WordPress is a good starting point for answer engine optimization: it serves content as HTML that AI crawlers can read. Most WordPress sites that are invisible to ChatGPT or Perplexity are held back by a security plugin, a CDN rule or a page builder, not by WordPress itself. This guide walks through the setup, in order of impact.
Step 1: Check AI crawler access
Open yoursite.com/robots.txt. WordPress generates a virtual file, and SEO plugins let you edit it. Make sure these aren't disallowed:
- OAI-SearchBot and ChatGPT-User (ChatGPT search and user-requested fetches)
- PerplexityBot and Perplexity-User
- Claude-SearchBot and Claude-User
- Googlebot and Bingbot (Google AI features and Copilot)
Blocking training crawlers such as GPTBot is a separate decision. See AI crawlers and robots.txt and blocking AI training crawlers.
Step 2: Check security plugins and your CDN
Security plugins (such as Wordfence) and CDN bot protection (such as Cloudflare's bot settings) can block AI crawlers even when robots.txt allows them. Test:
curl -s -o /dev/null -w "%{http_code}\n" -A "OAI-SearchBot" https://yoursite.com/
A 403 or a challenge page means the bot is blocked. Allow verified AI search crawlers in your firewall or CDN settings. See CDN bot protection and AI crawlers.
Step 3: Configure your SEO plugin's schema
Yoast SEO and Rank Math both output structured data. Complete:
- Site representation: Organization (or Person) with name, logo and social profiles. This drives your Organization schema and
sameAslinks. - Article schema for posts, with author pages filled in.
- Breadcrumbs enabled.
- FAQ and HowTo blocks where they fit the page.
Avoid running two schema plugins that output conflicting Organization data. See schema markup for AEO and Organization schema.
Step 4: Fix rendering issues from page builders
Most page builders render HTML on the server, but check for:
- Text inside sliders, tabs or accordions that only loads on click
- Content injected by JavaScript widgets
- Headings styled as text instead of real heading tags
View the page source (not the inspector) and search for your key sentences. If they're missing, AI crawlers likely miss them too. See JavaScript rendering and AI crawlers.
Step 5: Speed up for real-time fetchers
User-initiated AI fetches happen while the user waits. Use page caching, compress images, limit heavy plugins and check Core Web Vitals. See page speed for AI fetchers.
Step 6: Sitemaps, Bing and IndexNow
- Submit your SEO plugin's XML sitemap in Google Search Console and Bing Webmaster Tools.
- Enable IndexNow (available in several SEO plugins and CDNs) so Bing and other participating engines hear about updates quickly.
Bing's index matters for Copilot and other assistants. See Bing Webmaster Tools and IndexNow and XML sitemaps for AI search.
Step 7: Write in answer-first templates
Use the block editor to make structure easy:
- Heading blocks phrased as questions
- Paragraph with the direct answer first
- Table block for comparisons and prices
- List blocks for steps
- FAQ block at the end of key pages
Consider a reusable block pattern for "key takeaways" at the top of posts. See answer-first writing and content chunking for AI search.
Step 8: Optional extras
- llms.txt: easy to add with a plugin or upload; unconfirmed impact. See the llms.txt guide.
- Author pages with bios and expertise.
- Visible updated dates on posts you genuinely update.
WordPress AEO checklist
| Check | Where |
|---|---|
| AI search crawlers allowed | robots.txt (SEO plugin) |
| No firewall or CDN blocks | Security plugin, CDN dashboard |
| Organization schema complete | SEO plugin settings |
| Key content in page source | View source |
| Sitemap in Google and Bing | Search Console, Bing Webmaster Tools |
| IndexNow enabled | SEO plugin or CDN |
| Answer-first structure | Block editor templates |
Common WordPress problems we see
- "Discourage search engines" left on in Settings → Reading after a launch, adding noindex across the site.
- Security plugins blocking unknown bots by default, including AI search crawlers.
- Maintenance or coming-soon plugins returning 503 to bots long after launch.
- Duplicate schema from a theme and an SEO plugin both outputting Organization data.
- Tag and archive pages indexed with thin content while important pages lack internal links.
Each is quick to fix and often explains why a WordPress site is missing from AI answers.
The bottom line
WordPress already gives AI crawlers clean HTML. Unblock the bots, complete your SEO plugin's schema, keep content visible in the source, and write answer-first. Then measure with a technical AEO audit checklist.
