NEXEZ AGENT-READY
Nexez Agent-Ready compatibility with REEID Translate
Nexez Agent-Ready compatibility with REEID Translate is being evaluated from available plugin evidence. Server-side injection of Nexez listing structured data: adds JSON-LD (schema.org offers) into every page’s “ and constructs a manifest “ based on the configured Nexez listing slug. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Nexez Agent-Ready.
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
Nexez Agent-Ready 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 Nexez Agent-Ready 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
- Server-side injection of Nexez listing structured data: adds JSON-LD (schema.org offers) into every page’s “ and constructs a manifest “ based on the configured Nexez listing slug.
- Agent-discovery artifact path routing via 301 redirects: redirects requests on the WordPress domain for `/.well-known/agent.json`, `/agent.json`, `/llms.txt`, `/openapi.json`, and `/mcp.json` (when enabled) to the live Nexez listing’s corresponding artifact paths.
- Local serving of Nexez file ownership proof: serves `/.well-known/nexez-verify.txt` on the WordPress site to support Nexez site ownership verification without DNS changes.
- External data fetch with caching: after an administrator saves the listing slug, the plugin performs a server-side GET to `https://nexez.app//embed.json` when the local cache is empty or expired (one-hour cache); failed requests are cached for five minutes and saving settings clears the cache.
- Output construction and validation: validates the public JSON response from Nexez, encodes the JSON-LD locally, and constructs the manifest link locally; it does not print remote HTML into the site.
- Network/privacy behavior: Nexez requests originate from the WordPress server (not visitor browsers); the plugin does not send WordPress page content, administrator/visitor details, cookies, form values, or analytics data; it necessarily exposes the server IP and sends a User-Agent of the form `Nexez-Agent-Ready/; WordPress`.
- Admin-controlled enable/disable: saving the listing slug connects the site to Nexez and enables the Nexez-dependent behavior; clearing the slug disables it.
CONTENT BOUNDARY
Nexez Agent-Ready 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
Nexez Agent-Ready and REEID Translate FAQ.
What does Nexez Agent-Ready do according to the available plugin evidence?
Nexez Agent-Ready 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 Nexez Agent-Ready?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Nexez Agent-Ready?
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 Nexez Agent-Ready in a multilingual WordPress workflow.
REEID documents Nexez Agent-Ready 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.