AGENTIMUS
Agentimus – AI SEO, llms.txt & MCP for AI Agents translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Agentimus – AI SEO, llms.txt & MCP for AI Agents 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
- Generates AI-agent readable discovery outputs including llms.txt and llms-full.txt, plus a discovery document (forward-looking) and agent-card/MCP-related well-known endpoints (generated by the plugin).
- Provides machine-readable content delivery for AI/crawlers via Markdown delivery by appending .md to page URLs and/or using an Accept: text/markdown mode.
- Emits structured data (JSON-LD) for WebSite/Person/Organization, BlogPosting, and BreadcrumbList, while deferring to common SEO plugins to avoid duplicate schema.
- Serves an XML sitemap at /wp-sitemap.xml when no SEO plugin is installed, and advertises it in robots.txt and llms.txt; when an SEO plugin is present, it links to the SEO plugin’s sitemap instead.
- Publishes search/SEO-related metadata for per-page SEO titles, Open Graph/social share cards, canonical links, and meta descriptions, with switches under Settings → Discovery → Search basics; it also detects and “stands aside” on overlapping surfaces when certain SEO plugins are active.
- Implements a change feed endpoint (/agentimus-changes.json with ?since=) listing added/updated/removed pages for incremental re-checking by assistants.
- Runs an opt-in Model Context Protocol (MCP) server at /wp-json/agentimus/v1/mcp with permission-checked read-only tools by default, and optional write tools behind additional switches; write actions run as the signed-in WordPress user and are recorded under More → Agent Access.
- Supports AI crawler/bot policy signaling and hard blocking via robots.txt and additional mechanisms: it can add a Content-Signal line to robots.txt for AI training opt-out, publish a tdmrep.json opt-out file, and enforce scanner/crawler hard blocks that return 403 to denied user-agents.
Distinctive features
Generates AI-agent readable discovery outputs including llms.txt and llms-full.txt, plus a discovery document (forward-looking) and agent-card/MCP-related well-known endpoints (generated by the plugin). Provides machine-readable content delivery for AI/crawlers via Markdown delivery by appending .md to page URLs and/or using an Accept: text/markdown mode. Emits structured data (JSON-LD) for WebSite/Person/Organization, BlogPosting, and BreadcrumbList, while deferring to common SEO plugins to avoid duplicate schema. Serves an XML sitemap at /wp-sitemap.xml when no SEO plugin is installed, and advertises it in robots.txt and llms.txt; when an SEO plugin is present, it links to the SEO plugin’s sitemap instead. Publishes search/SEO-related metadata for per-page SEO titles, Open Graph/social share cards, canonical links, and meta descriptions, with switches under Settings → Discovery → Search basics; it also detects and “stands aside” on overlapping surfaces when certain SEO plugins are active. Implements a change feed endpoint (/agentimus-changes.json with ?since=) listing added/updated/removed pages for incremental re-checking by assistants. Runs an opt-in Model Context Protocol (MCP) server at /wp-json/agentimus/v1/mcp with permission-checked read-only tools by default, and optional write tools behind additional switches; write actions run as the signed-in WordPress user and are recorded under More → Agent Access. Supports AI crawler/bot policy signaling and hard blocking via robots.txt and additional mechanisms: it can add a Content-Signal line to robots.txt for AI training opt-out, publish a tdmrep.json opt-out file, and enforce scanner/crawler hard blocks that return 403 to denied user-agents.
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 Agentimus – AI SEO, llms.txt & MCP for AI Agents 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
Agentimus – AI SEO, llms.txt & MCP for AI Agents and REEID Translate FAQ.
Does the current evidence establish translation scope for Agentimus – AI SEO, llms.txt & MCP for AI Agents?
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.