MentionReady

MentionReady helps WordPress site owners turn SEO, AEO, GEO and AI-readiness work into reviewable, reversible operations. llms.txt is one managed resource inside the product; it is not the product’s primary purpose.

MentionReady 1.0.0 is built as an AI Search Operating System for WordPress. The Command Center turns multi-day optimization work into reviewable Missions: scan the site, prioritize opportunities by business goal, preview changes, apply only explicitly safe actions, verify state, and roll changes back without overwriting newer edits.

The Complete toolset includes custom SEO titles and descriptions, canonical and social metadata, 404 intelligence, 301/302/307/308/410 redirects with loop protection, internal-link/orphan analysis with contextual suggestions and reviewable one-click link insertion, image-alt audits, a Brand Truth Center that feeds MentionReady’s organization identity and llms site context, local-business readiness, content-decay detection, an enforced pre-publish quality gate, topic-authority scoring, SEO-plugin migration helpers, WooCommerce product-readiness checks, crawler monitoring, Search Console/IndexNow integrations, BYOK AI review drafts, AEO analysis, llms.txt/llms-full.txt, schema, agent capabilities, unified HTML/JSON/CSV reporting, approval queues, verified mission rollback, plus a built-in non-destructive System Check that verifies the live WordPress runtime, MentionReady database tables, REST wiring, shipped UI assets, scheduling readiness, SEO coexistence and optional connection state.

The product is built around one outcome: make the parts of your website that matter to AI crawlers and agents visible, reviewable, and maintainable — without inventing traffic, rankings, or external behavior.

MentionReady checks observable site signals, prepares website-specific drafts, keeps publication under administrator control, and monitors meaningful changes after setup. It separates saved configuration from live public state, so a draft is never reported as published and an unavailable observation is never converted into a pass.

Use MentionReady to review crawler access in robots.txt, publish llms.txt guidance, manage safe response headers and structured data, expose genuine read-only agent capabilities, inspect the live WordPress REST catalog, generate technical reports, monitor public resources, and receive notifications when something important changes.

What makes MentionReady different

MentionReady is not a single-purpose llms.txt generator. Its distinctive workflow is Detect → Prioritize → Preview → Apply → Verify → Roll back across technical SEO, AEO/GEO, content and AI-discovery signals.

• Goal-based Missions instead of settings-only tooling — site launch, AI-readiness, SEO cleanup, internal-link rescue, content refresh and image cleanup workflows coordinate multiple checks and actions.
• Verified rollback — Mission snapshots store exact before/after state and hashes; rollback skips fields that were changed again later instead of overwriting newer work.
• Safe-vs-review separation — technical actions explicitly classified as safe can be automated only after administrator opt-in; content and policy decisions remain review-first.
• Observable-only reporting — MentionReady records real local events and public resource state. It never invents crawler visits, rankings, AI citations or external mentions.
• Cross-layer command center — SEO metadata, redirects/404s, internal-link graph, pre-publish quality gate, Brand Truth, schema, robots/llms resources, crawler monitoring, Search Console/IndexNow and reports are coordinated from one workflow.
• WordPress-native AI path — on WordPress 7.0+ MentionReady prefers the Core WordPress AI Client and site-level provider connectors. Direct BYOK OpenAI/Anthropic/Gemini calls remain an optional compatibility fallback where no compatible Core connector is available.

Runtime Compatibility

MentionReady requires the PHP DOM extension (ext-dom). Multibyte string support is also required; hosts may provide native ext-mbstring, while the bundled symfony/polyfill-mbstring compatibility layer supplies the required operations when native mbstring is unavailable.

Privacy

MentionReady does not collect, transmit, or share site data by default. Core readiness checks, generated resources, and local monitoring run on your WordPress installation.

Local intelligence can store recognized crawler requests, 404 request paths, aggregate WordPress site-search phrases, readiness events, Mission snapshots, and report history in the site database. These records stay on the WordPress installation unless an administrator explicitly uses a connected external feature. MentionReady does not intentionally store visitor IP addresses in these local intelligence records.

No telemetry, usage analytics, advertising tracking, or unrelated “phone-home” traffic is sent to KODEA.

External services

MentionReady’s core scans, generated resources, local analytics and monitoring do not require an external service. The services below are optional and are contacted only when an administrator explicitly configures or invokes the related feature.
The WordPress.org 1.0.0 build does not include the MentionReady Agency Hub or any KODEA-hosted remote monitoring service, so it does not send site data to a KODEA service.

On WordPress 7.0+, MentionReady prefers the provider-agnostic WordPress AI Client when the site owner has configured a compatible provider in WordPress. In that mode, provider credentials are managed by WordPress/Core connector infrastructure rather than MentionReady. If no compatible Core connector is available, MentionReady can use the administrator’s directly configured BYOK provider as a compatibility fallback.

• OpenAI API (optional BYOK fallback) — used only when no compatible WordPress AI Client connector is available and an administrator explicitly selects OpenAI and saves an OpenAI API key. MentionReady sends the prompt, relevant site-content excerpts, conversation context needed for the requested feature, model/generation settings, and the administrator-provided API credential. Service: https://openai.com/api/ — Service terms: https://openai.com/policies/service-terms/ — Privacy: https://openai.com/policies/privacy-policy/
• Anthropic API (optional BYOK fallback) — used only when no compatible WordPress AI Client connector is available and an administrator explicitly selects Anthropic and saves an Anthropic API key. MentionReady sends the prompt, relevant site-content excerpts, conversation context needed for the requested feature, model/generation settings, and the administrator-provided API credential. Service: https://www.anthropic.com/api — Commercial terms: https://www.anthropic.com/legal/commercial-terms — Privacy: https://www.anthropic.com/legal/privacy
• Google Gemini API (optional BYOK fallback) — used only when no compatible WordPress AI Client connector is available and an administrator explicitly selects Google and saves a Gemini API key. MentionReady sends the prompt, relevant site-content excerpts, conversation context needed for the requested feature, model/generation settings, and the administrator-provided API credential. Service: https://ai.google.dev/ — Gemini API terms: https://ai.google.dev/gemini-api/terms — Google APIs Terms: https://developers.google.com/terms — Privacy: https://policies.google.com/privacy
• Google Search Console APIs — optional sitemap registration and URL Inspection features send the connected site’s URL, sitemap URL or inspected URL to Google and authenticate with the OAuth credential you connect. Service: https://developers.google.com/webmaster-tools — Google APIs Terms: https://developers.google.com/terms — Privacy: https://policies.google.com/privacy

• IndexNow — optional URL notifications send the site host, URLs being notified, and the site’s IndexNow key to participating IndexNow endpoints. MentionReady generates and stores a local key automatically when one is not already configured; an administrator can replace it with a custom key. Service: https://www.indexnow.org/ — Terms and privacy information: https://www.indexnow.org/terms

• Crawler documentation links are references only — URLs stored in MentionReady’s crawler catalog (for example OpenAI bot documentation, Anthropic crawler documentation, Google-Extended, Amazonbot, Perplexity, Applebot, Facebook, YouBot, Cohere and Diffbot documentation) are displayed as human-readable reference links. MentionReady does not request those documentation URLs and does not transmit site data to those crawler companies merely because their documentation link appears in the catalog.

Development

MentionReady ships its human-readable UI source in the src/ directory together with the build script used to produce dist/.

To verify the JavaScript source:

npm run check

To rebuild the distributed UI files:

npm run build

The PHP autoload mapping is documented in composer.json and uses the MentionReady\ PSR-4 namespace. The bundled Symfony mbstring polyfill is MIT-licensed and GPL-compatible; its license is included under vendor/symfony/polyfill-mbstring/LICENSE.

Source and Build

MentionReady ships human-readable source code inside the plugin. Admin and front-end sources live under src/; npm run build copies the reviewed source assets into dist/, and npm run check performs JavaScript syntax checks against the human-readable source. No remote JavaScript or CSS is required for the plugin interface.

The WordPress.org build does not contain a custom plugin updater or license-validation service. Plugin updates are delivered through WordPress.org.