STEDICA SEO
Stedica SEO translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Stedica 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
- Audits and scores SEO issues across site URLs (admin-side), including meta, schema, social, sitemaps, redirects, hreflang, and other gaps.
- Reads and writes SEO metadata fields for multiple existing SEO plugins (Yoast, Rank Math, SEOPress, AIOSEO) so audits can run without migrating or losing existing metadata.
- Generates/outputs core structured data (Organization, WebSite, WebPage, BreadcrumbList JSON-LD) and provides a schema editor to validate/edit JSON-LD @graph nodes.
- Manages canonical URLs and robots directives per post, including support for noindex/nofollow/noarchive/nosnippet and merging into WordPress robots output.
- Provides XML sitemap functionality (paginated, cached, image-aware) with robots.txt integration, plus an HTML sitemap via shortcode `[stedica_html_sitemap]` and a table-of-contents block/shortcode `[stedica_toc]` with stable heading anchors.
- Supports IndexNow submissions to Bing/Yandex/Seznam/Naver when enabled (off by default), sending only the URL of published/updated posts to `api.indexnow.org/indexnow`.
- Implements redirect management with unlimited rules (301/302/307/410) and a 404 log, including redirect importers in Premium.
- Exposes a REST API endpoint namespace `/wp-json/stedica-seo/v1/` for audits, issues, and per-page SEO fields.
Distinctive features
Audits and scores SEO issues across site URLs (admin-side), including meta, schema, social, sitemaps, redirects, hreflang, and other gaps. Reads and writes SEO metadata fields for multiple existing SEO plugins (Yoast, Rank Math, SEOPress, AIOSEO) so audits can run without migrating or losing existing metadata. Generates/outputs core structured data (Organization, WebSite, WebPage, BreadcrumbList JSON-LD) and provides a schema editor to validate/edit JSON-LD @graph nodes. Manages canonical URLs and robots directives per post, including support for noindex/nofollow/noarchive/nosnippet and merging into WordPress robots output. Provides XML sitemap functionality (paginated, cached, image-aware) with robots.txt integration, plus an HTML sitemap via shortcode `[stedica_html_sitemap]` and a table-of-contents block/shortcode `[stedica_toc]` with stable heading anchors. Supports IndexNow submissions to Bing/Yandex/Seznam/Naver when enabled (off by default), sending only the URL of published/updated posts to `api.indexnow.org/indexnow`. Implements redirect management with unlimited rules (301/302/307/410) and a 404 log, including redirect importers in Premium. Exposes a REST API endpoint namespace `/wp-json/stedica-seo/v1/` for audits, issues, and per-page SEO fields.
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 Stedica 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
Stedica SEO and REEID Translate FAQ.
Does the current evidence establish translation scope for Stedica 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.