When AI answers a question
your blog already covers,
it should cite you.
Right now it probably does not. A typical AI answer cites only a handful of sources, and your WordPress site is missing the signals that get you on that shortlist. No llms.txt, no Markdown for agents, no author identity, no idea which AI bots are reading you. RankReady fixes that side of it, alongside the SEO plugin you already run.
Free, forever · No credit card · Coexists with Rank Math, Yoast and AIOSEO
You rank fine on Google.
AI still skips you.
Traditional SEO plugins optimise for blue links, a web that is shrinking. AI assistants check four different things before they cite a source. Most WordPress installs miss all four.
There is no AI index of your site
Google reads your sitemap.xml. ChatGPT reads nothing. Without an llms.txt file, AI crawlers cannot tell what your site covers, so they go cite someone who has one.
Your content is not shaped like an answer
Google AI Overviews and Perplexity lift answers from clearly structured content. Clean headings, Speakable and Article markup, and a Markdown copy of the page hand them a passage they can quote. A wall of prose is harder to pull from.
Your authors look anonymous
E-E-A-T is what Google's Search Quality Rater Guidelines use to weigh a source. With empty Person schema, no bio, credentials or topics, there is nothing for a model to weigh.
You cannot see any of it happening
Which AI bots came by? Which posts did they fetch mid-answer? Without a log you are guessing. RankReady puts every bot hit and citation in a real table.
Three things happen
before AI quotes you.
None of it is mysterious. Once you see the sequence, you can see exactly where your site drops out.
The bot finds you
It reads your llms.txt to see what your site covers, pulls the Markdown version of the post it cares about, and checks Content Signals for what it is allowed to do.
The bot decides you are worth quoting
Article and Speakable schema point at the sentences worth lifting. A Markdown copy of the page removes the guesswork. E-E-A-T author schema tells it whether the writer is someone to trust.
The bot cites you
Someone asks ChatGPT, Perplexity or Google AI a question in your niche. The bot composes an answer from the sources it scored highest, and your URL lands in the citation list.
Everything you need to be
discovered, read and cited.
The AI layer your SEO plugin does not add: discovery files, schema shaped like an answer, one-click generation, and a log of which bots actually read you.
Show up where the bots are actually looking.
The discovery layer. If a crawler cannot find or read your content, nothing else matters.
llms.txt & llms-full.txt
The llmstxt.org standard at /llms.txt, an AI-native index of your best content. RankReady generates both files and keeps them current as you publish.
Markdown endpoints
Every post served as clean Markdown at /post.md with YAML frontmatter. Agents parse it cleanly, with no theme HTML, navigation or scripts in the way. Content negotiation via Accept: text/markdown too.
WebMCP manifest New
A Model Context Protocol manifest at /.well-known/mcp.json lists what agents can do on your site. Claude Desktop and Cursor users add you as an MCP server.
Open Knowledge Format New
OKF output, so agents that speak the emerging open-knowledge spec can consume your site directly, not only the ones that read llms.txt.
29 AI crawler controls
Allow or block GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Bytespider and 24 more, individually. Auto-synced to a real robots.txt, even if a host plugin intercepts it.
Content Signals
The ai-train, search and ai-input directives let you say "index me, do not train on me" in a way bots already understand, per contentsignals.org.
Give the bots the shape of an answer.
Schema is how AI understands what a post actually is. RankReady picks the right one per post. You write normally, the plugin handles the markup.
Article & Speakable schema
Every post gets Article JSON-LD with Speakable sentences flagged separately, the part voice assistants and AI read aloud. Running Rank Math or Yoast? RankReady merges into their graph instead of duplicating.
FAQPage schema
Structured question and answer pairs give AI a clean, ready-to-quote passage. Generate a FAQ on any post and the JSON-LD wires itself up.
E-E-A-T author box
Photo, bio, headline, topics, credentials, year started. Drop the Gutenberg block or Elementor widget and Person schema goes out with it, so bots know who wrote the post and what they know.
Brand terms & identity New
One source of truth for your site name, summary, about text and the terms your brand owns, reused across schema and llms.txt so AI describes you consistently everywhere.
Multilingual llms.txt
Auto-detects WPML, Polylang, TranslatePress, Weglot and GTranslate, and emits hreflang Link headers so crawlers discover every translated copy alongside the canonical.
Generate the bits AI actually quotes from.
Bring your own API key. RankReady writes FAQ blocks and summaries wrapped in the right schema, with no monthly cap on either.
AI summaries Unlimited
One click writes a "Key Takeaways" block at the top of any post, wrapped in Speakable schema so AI knows exactly which sentences to quote.
FAQ generator + DataForSEO Unlimited
RankReady asks DataForSEO for the real "People Also Ask" questions ranking for your keyword, has your LLM answer them, and attaches FAQPage schema.
Use any of four LLMs
OpenAI, Anthropic Claude, Google Gemini or DeepSeek. Paste one key in Settings and you are done, switch any time. Your key never leaves your server.
Native block & Elementor widget
Three blocks ship in the box: AI Summary, FAQ and Author Box. Drop them anywhere, pick position, label and whether they are open by default.
Regenerate inside the editor
Updated a post? There is a regenerate button right in the meta box. No bulk job, no separate page. You pay only your own usage, typically $0.001 to $0.01 a post.
See which AI engines are reading you.
Every analytics view is free, server-side, and stays on your own site. Without this data you are guessing whether any of it works. With it, you just look.
Training-bot log
Which AI crawlers indexed which pages: GPTBot, ClaudeBot, Google-Extended, Bytespider, CCBot and more training-intent bots, timestamped and sorted.
Citation-bot candidates
Which pages were fetched mid-answer by ChatGPT-User, OAI-SearchBot, PerplexityBot, Claude-Web and DuckAssistBot. Each hit is a live AI answer that retrieved your page.
Intent classification New
Every bot hit is tagged by why it came: training, search indexing, or a live citation fetch. The logs tell you intent, not just traffic.
Real AI referrals
Humans clicking through from chatgpt.com, perplexity.ai, claude.ai, gemini.google.com and copilot.microsoft.com, tracked 100% server-side via the Referer header.
Content freshness scanner
Buckets every post into Fresh, Going stale and Stale. Tick the stale ones and bulk-refresh dateModified, a clean recency signal without touching content.
Standards-compliant down to the header.
The AI-readable endpoints are cheap to serve, correct at the edge, and overridable from code. Built for people who read the source.
RFC 9110/9111 cache headers
Split max-age against s-maxage so browsers and edges cache the AI routes correctly, not by accident.
ETag + If-None-Match to 304
Revalidation on /llms.txt and /mcp.json saves 60% to 90% bandwidth on repeat crawls.
CORS on AI-readable endpoints
Agents fetching cross-origin are not blocked by a missing header. The AI routes answer them cleanly.
Cloudflare APO admin notice
Detects APO and surfaces the exact Cache Rule snippet to paste, so content-negotiated Markdown works without a cache buster.
llms.txt content filters
Override the generated file with rankready_llms_txt_content, or force it on in edge cases with rankready_force_llms_txt.
WordPress.org native updates
Ships and updates through the official repo. No license servers, no custom update endpoints.
On the roadmap.
The features we are building next. Marked coming soon in the plugin today.
The public AI-readiness tools
grade you. RankReady passes.
IsItAgentReady and the AcceptMarkdown recipe are the community benchmarks for an AI-ready site. RankReady is built to pass everything they check for, automatically, from a plugin install.
Check if your site is agent-ready or not.
Is It Agent Ready?
- /llms.txt present and validThe content index AI crawlers check first
- Markdown endpoints active/post.md served on every URL
- AI crawler access configuredGPTBot, ClaudeBot and PerplexityBot permitted
- Structured data detectedFAQPage, Article and Speakable schema present
RankReady handles every item for you. Install, run the setup wizard, re-test. Your score moves from red to green without touching a server.
Test your siteAccept Markdown recipe
- Per-post Markdown endpointsEvery URL available at /post.md
- Structure preservedHeadings, lists, tables and code blocks intact
- Correct Content-Type headertext/markdown, so agents recognise it
- Works with every editorGutenberg, Elementor, Bricks and Classic
RankReady ships the recipe out of the box. One toggle in Settings. No theme edits, no functions.php, no custom routes to maintain later.
Read the recipeAbout five minutes,
start to finish.
If you have ever installed a WordPress plugin, you already know how this goes.
Install from WordPress.org
Plugins, Add New, search RankReady, install, activate. No account, no credit card, no zip to download yourself.
Turn on the safe defaults
Tick the master toggles for llms.txt, Markdown, schema, crawler rules and insights, then Save. One conventional WordPress settings flow.
Paste a key, generate
In Settings pick OpenAI, Anthropic, Gemini or DeepSeek and paste the key. Open any post, hit Generate Summary. Seconds later your first AI-friendly post is live.
Every answer,
already written down.
Setup, each feature on its own page, and the exact fix for the errors people actually hit.
Getting Started
Install it, configure it, and confirm it is actually running.
- How to install RankReady on WordPress
- The RankReady setup wizard, step by step
- What RankReady does, and what it does not
Features
Every feature explained, one page each, with what it does and does not do.
- How to add llms.txt to WordPress
- What is llms-full.txt and when to use it
- llms.txt examples: real files, explained
Troubleshooting
The exact error, the real cause, and the fix that works.
- The .md version of a post returns 404 or serves HTML
- AI summary or FAQ generation fails with an error
- The E-E-A-T author box does not appear
Reference
Endpoints, settings, hooks and crawler names, in full.
- Every RankReady endpoint, referenced
- RankReady hooks and filters for developers
- Every RankReady setting explained
The honest answers,
before you have to ask.
Q. Will RankReady conflict with Rank Math, Yoast or AIOSEO?
No. It is designed to work alongside Rank Math, Yoast, AIOSEO, SEOPress, The SEO Framework and Slim SEO. Before injecting schema it checks whether another schema plugin is active, then skips its own output or merges into the existing graph via documented filters. Verifiable in Google's Rich Results Test, with no duplicate Article, Person or FAQPage nodes.
Q. How does RankReady actually work?
Three layers. First, discovery files: /llms.txt, /llms-full.txt, /.well-known/mcp.json and per-post Markdown, which crawlers read to find your content. Second, structured markup (Article, Speakable, FAQPage, ItemList) so an assistant can tell what each passage on the page actually is. Third, controls and analytics over which bots see you and which already do.
Q. Do I need an AI provider API key?
Only for AI Summaries and the FAQ Generator. llms.txt, Markdown endpoints, crawler controls, Article schema, Author Box, AI referral tracking, the freshness scanner and the WebMCP manifest all work with no key at all. You can make your content AI-readable without ever pasting a key in.
Q. Are there usage limits or monthly caps?
No caps. Manual AI Summary and FAQ generation are unlimited. You pay only your own LLM usage, typically $0.001 to $0.01 per generation. Every other feature is completely free with no limits.
Q. Will this slow down my site?
No. All AI generation runs in the WordPress admin, never on page load. Schema and discovery headers add a few hundred bytes. /llms.txt and robots.txt are cached via a 10-minute transient with stale-while-revalidate. Page Speed Insights and Core Web Vitals are unaffected.
Q. What data leaves my site?
Your content, keys, crawler logs and author profiles all stay in your own wp_options and wp_postmeta tables. The only outbound calls are to the LLM providers you connected yourself, plus DataForSEO if you use the FAQ question-finder.
Q. What is the .well-known/mcp.json manifest?
Model Context Protocol is an open standard for letting AI agents discover and call your site's structured content. RankReady publishes a manifest at /.well-known/mcp.json listing what an agent can do: read posts, list authors, fetch FAQs, query categories. Claude Desktop and Cursor users add your site as an MCP server by pointing at this file.
Q. Will it work with my page builder?
Yes: Gutenberg, Elementor, Bricks, Oxygen, Divi, Breakdance and Beaver Builder. RankReady hooks into template_redirect at priority 1 so builder routes do not block the AI endpoints. Posts and Pages are covered today, custom post types are on the way.