DIGISTARTER BASIC SEO
DIGISTARTER Basic SEO translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what DIGISTARTER Basic SEO does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Site-wide title pattern configuration via Settings → General (separator and site-name order) applied across multiple page types, with a front-page exception described in the plugin documentation.
- Per-page meta description support for posts/pages (editor sidebar, Quick Edit, list-screen column, and front page setting), where leaving the field empty results in no meta description tag being written.
- Open Graph and Twitter card tag generation per page using the page title, meta description, and featured image; pages without a featured image omit `og:image`, and pages without a description omit `og:description`.
- Sitemap endpoint at `/sitemap.xml` that lists every published post and page with last-modified dates, generated fresh from the database on each request (not written to a file).
- Sitemap behavior includes direct handling of the `/sitemap.xml` request with its own HTTP status and `robots.txt` updates to point to it, intended to avoid issues described with WordPress’s `/wp-sitemap.xml` redirect/404 behavior.
- Deliberate scope limitation: no per-page title override, no robots controls, no character counters/snippet preview, no custom dashboard/menu, and no templates with placeholders (per the provided readme).
Distinctive features
Site-wide title pattern configuration via Settings → General (separator and site-name order) applied across multiple page types, with a front-page exception described in the plugin documentation. Per-page meta description support for posts/pages (editor sidebar, Quick Edit, list-screen column, and front page setting), where leaving the field empty results in no meta description tag being written. Open Graph and Twitter card tag generation per page using the page title, meta description, and featured image; pages without a featured image omit `og:image`, and pages without a description omit `og:description`. Sitemap endpoint at `/sitemap.xml` that lists every published post and page with last-modified dates, generated fresh from the database on each request (not written to a file). Sitemap behavior includes direct handling of the `/sitemap.xml` request with its own HTTP status and `robots.txt` updates to point to it, intended to avoid issues described with WordPress’s `/wp-sitemap.xml` redirect/404 behavior. Deliberate scope limitation: no per-page title override, no robots controls, no character counters/snippet preview, no custom dashboard/menu, and no templates with placeholders (per the provided readme).
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what DIGISTARTER Basic SEO does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
DIGISTARTER Basic SEO and REEID Translate FAQ.
Does the current evidence establish translation scope for DIGISTARTER Basic SEO?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.