Quick answer: A WordPress site is AI ready when search visibility is switched on, robots.txt and any security or CDN layer let AI crawlers in, an SEO plugin outputs clean structured data, and posts answer questions directly. WordPress gives you full control, which also means one plugin setting can quietly block every AI crawler.
The audit scores 15 signals out of 100: whether OAI-SearchBot, PerplexityBot, Claude-SearchBot, Bingbot and eight other AI agents may crawl the page, whether it is indexable, llms.txt and sitemap presence, structured data, content depth, answer capsules, and metadata. Nothing is stored.
How WordPress handles AI crawlers by default
If there is no physical robots.txt file in the site root, WordPress serves a virtual one that allows crawling and lists the core sitemap. SEO plugins such as Yoast SEO and Rank Math let you edit that file from the dashboard, and a physical robots.txt file uploaded to the root overrides the virtual one.
WordPress has created a core sitemap at /wp-sitemap.xml since version 5.5. SEO plugins usually replace it with their own, for example /sitemap_index.xml, and add the location to robots.txt.
WordPress AI SEO checklist
Work through these in order. The first three decide whether AI engines can read your site at all; the rest decide whether they choose to cite it.
- Turn off "Discourage search engines"Go to Settings, then Reading, and make sure the option that discourages search engines from indexing the site is unchecked. It is often left on after a staging copy goes live, and it adds noindex to every page.
- Check robots.txt from the plugin you useIn Yoast SEO use the file editor under Tools. In Rank Math use the robots.txt editor in its general settings. If a physical robots.txt exists in the root, edit that file instead, since it overrides both. Remove any Disallow rules aimed at OAI-SearchBot, PerplexityBot, Claude-SearchBot or Bingbot.
- Check security plugins and your CDNFirewall and security plugins, host-level bot protection, and CDN features that block AI bots can refuse crawlers that robots.txt allows. If the audit says the page could not be fetched, review those layers first.
- Verify structured dataYoast SEO and Rank Math output a structured data graph with WebSite, Organization and Article or WebPage types. Run the audit on a post to confirm, and avoid running two SEO plugins at once, which duplicates schema.
- Use FAQ blocks on key postsBoth Yoast SEO and Rank Math include FAQ blocks for the block editor that output FAQPage structured data. Add three to five real questions with direct answers to your most important posts.
- Write answer-first sectionsStart each H2 section with a one or two sentence answer before the detail. Themes and page builders do not matter much here; the text does.
- Add llms.txt if you want itUpload a plain text llms.txt to the site root with your host's file manager or SFTP. Some SEO plugins can generate one for you. It is optional, so do it after the fixes above.
Common WordPress problems the audit finds
- "Discourage search engines from indexing this site" left on after launch
- A security plugin or host firewall challenging AI crawlers that robots.txt allows
- Two SEO plugins active at once, producing duplicate or conflicting schema
- Category and tag archives indexed with no unique text, diluting the site
- Posts that bury the answer under long introductions
After you fix the basics
Access and markup make a WordPress site eligible for AI answers; they do not guarantee citations. Engines choose sources that answer the question directly and that other sites refer to. Re-run the audit after each change, check whether ChatGPT can reach your pages, and make sure your site is verified and indexed in Bing, since several AI assistants rely on the Bing index.
WordPress AI SEO FAQ
Audit every important WordPress page
Run the audit on your homepage, a top product or service page, and your most visited article. Each page type fails for different reasons.
Back to the audit