VISIBILITY
Visibility – Lightweight SEO, AEO and GEO for Search and AI translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Visibility – Lightweight SEO, AEO and GEO for Search and AI does, but does not yet establish specific visitor-facing content values that REEID should translate.
Visit Visibility – Lightweight SEO, AEO and GEO for Search and AI ↗
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
- SEO metadata generation: outputs meta title/description, canonical URLs, Open Graph tags, and Twitter Cards with per-post and per-term overrides.
- Structured data (schema) emission: generates JSON-LD schema including Article-family nodes (selectable type per content type), BreadcrumbList, Person (with author expertise fields), FAQPage derived from Details/Accordion blocks, and Site Identity (Organization/WebSite) on the home page.
- Robots and indexing controls: provides robots directives (noindex/nofollow) with bulk or per-item controls by post type and taxonomy, including rules for search, 404, date/paginated/attachment/author archives and RSS feeds.
- Sitemap handling: customizes WordPress’s native XML sitemap at `/wp-sitemap.xml` by excluding selected post types/taxonomies/users/posts/terms, controlling lastmod dates and URL limits, and ensuring noindexed content is excluded; includes repair behavior for the native sitemap returning 404 when there are no published Posts entries.
- Redirect management: includes a lightweight redirect manager supporting HTTP status codes 301/302/307/410, with CSV import/export and suggested redirects when posts are deleted; also supports taking over WordPress slug-change redirects.
- AI discovery outputs and robots.txt endpoint control: provides AI discovery files/controls including `llms.txt`/`llms-full.txt` and a robots.txt editor; serves `/robots.txt` itself (virtual endpoint) when no physical file exists and merges its directives into an existing physical robots.txt in BEGIN/END blocks.
- External service behavior for author images: when Open Graph module is active and no other image source exists, performs a cached (24-hour TTL) Gravatar lookup via an HTTP HEAD request using an MD5 hash of the lowercased/trimmed author email (original email not sent) to determine whether an author avatar exists for use in `og:image` and Person schema image fields.
- Storage and integration surface: stores settings in a single autoloaded WordPress option and per-post/per-term/per-author overrides in native WordPress meta; exposes compatibility via documented frontend robots-resolution methods and settings accessors, plus filters for schema graph/meta description/OG image/FAQ pairs.
Distinctive features
SEO metadata generation: outputs meta title/description, canonical URLs, Open Graph tags, and Twitter Cards with per-post and per-term overrides. Structured data (schema) emission: generates JSON-LD schema including Article-family nodes (selectable type per content type), BreadcrumbList, Person (with author expertise fields), FAQPage derived from Details/Accordion blocks, and Site Identity (Organization/WebSite) on the home page. Robots and indexing controls: provides robots directives (noindex/nofollow) with bulk or per-item controls by post type and taxonomy, including rules for search, 404, date/paginated/attachment/author archives and RSS feeds. Sitemap handling: customizes WordPress’s native XML sitemap at `/wp-sitemap.xml` by excluding selected post types/taxonomies/users/posts/terms, controlling lastmod dates and URL limits, and ensuring noindexed content is excluded; includes repair behavior for the native sitemap returning 404 when there are no published Posts entries. Redirect management: includes a lightweight redirect manager supporting HTTP status codes 301/302/307/410, with CSV import/export and suggested redirects when posts are deleted; also supports taking over WordPress slug-change redirects. AI discovery outputs and robots.txt endpoint control: provides AI discovery files/controls including `llms.txt`/`llms-full.txt` and a robots.txt editor; serves `/robots.txt` itself (virtual endpoint) when no physical file exists and merges its directives into an existing physical robots.txt in BEGIN/END blocks. External service behavior for author images: when Open Graph module is active and no other image source exists, performs a cached (24-hour TTL) Gravatar lookup via an HTTP HEAD request using an MD5 hash of the lowercased/trimmed author email (original email not sent) to determine whether an author avatar exists for use in `og:image` and Person schema image fields. Storage and integration surface: stores settings in a single autoloaded WordPress option and per-post/per-term/per-author overrides in native WordPress meta; exposes compatibility via documented frontend robots-resolution methods and settings accessors, plus filters for schema graph/meta description/OG image/FAQ pairs.
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 Visibility – Lightweight SEO, AEO and GEO for Search and AI 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
Visibility – Lightweight SEO, AEO and GEO for Search and AI and REEID Translate FAQ.
Does the current evidence establish translation scope for Visibility – Lightweight SEO, AEO and GEO for Search and AI?
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.