VISIBILITY
Visibility – Lightweight SEO, AEO and GEO for Search and AI compatibility with REEID Translate
Visibility – Lightweight SEO, AEO and GEO for Search and AI compatibility with REEID Translate is being evaluated from available plugin evidence. SEO metadata generation: outputs meta title/description, canonical URLs, Open Graph tags, and Twitter Cards with per-post and per-term overrides. No specific visitor-facing translation surface is currently confirmed.
Visit Visibility – Lightweight SEO, AEO and GEO for Search and AI ↗
AWAITING VERIFICATION
What the available evidence establishes for Visibility – Lightweight SEO, AEO and GEO for Search and AI.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Visibility – Lightweight SEO, AEO and GEO for Search and AI is documented in the SEO category with 8 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Visibility – Lightweight SEO, AEO and GEO for Search and AI compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
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.
CONTENT BOUNDARY
Visibility – Lightweight SEO, AEO and GEO for Search and AI capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
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.
What does Visibility – Lightweight SEO, AEO and GEO for Search and AI do according to the available plugin evidence?
Visibility – Lightweight SEO, AEO and GEO for Search and AI has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Visibility – Lightweight SEO, AEO and GEO for Search and AI?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Visibility – Lightweight SEO, AEO and GEO for Search and AI?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Visibility – Lightweight SEO, AEO and GEO for Search and AI in a multilingual WordPress workflow.
REEID documents Visibility – Lightweight SEO, AEO and GEO for Search and AI functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.