NOINDEX SEO
noindex SEO compatibility with REEID Translate
noindex SEO compatibility with REEID Translate is being evaluated from available plugin evidence. Applies up to five independent robots directives—noindex, nofollow, noarchive, nosnippet, and noimageindex—to selected WordPress page contexts. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for noindex SEO.
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
noindex SEO is documented in the SEO category with 7 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 noindex SEO 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
- Applies up to five independent robots directives—noindex, nofollow, noarchive, nosnippet, and noimageindex—to selected WordPress page contexts.
- Supports three directive delivery methods: HTML meta tags (e.g., “), HTTP headers (via `X-Robots-Tag`), or both simultaneously.
- Provides global configuration to apply directives across 22 different page contexts (e.g., front page, home, pages, privacy policy, single/singular, category/tag/date archives, author pages, post type archives, pagination, search results, attachments, customize/preview modes, and 404 error pages).
- Supports granular per-content overrides via meta boxes for individual posts, pages, and custom post types, with precedence described as per-post override → per-post-type default → built-in context.
- Exposes two read-only REST API endpoints under `/wp-json/noindex-seo/v1/` for headless consumers: `GET /settings` (requires authenticated user with `manage_options`) and `GET /effective?post_id=…` (public only for published, non-password-protected posts; otherwise requires `edit_post`).
- Integrates with WordPress XML sitemaps (on WordPress 5.5+): URLs receiving a noindex directive are excluded from the core sitemap (`/wp-sitemap.xml`).
- Preserves plugin data on uninstall by default, with an optional setting to delete all plugin data on uninstall.
CONTENT BOUNDARY
noindex SEO 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
noindex SEO and REEID Translate FAQ.
What does noindex SEO do according to the available plugin evidence?
noindex SEO has 7 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 noindex SEO?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for noindex SEO?
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 noindex SEO in a multilingual WordPress workflow.
REEID documents noindex SEO 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.