Website builder guide
Short answer
Core WordPress ships with almost nothing for AI search or Google visibility: no schema markup, no llms.txt, no AI citation tracking, just a barebones sitemap and a basic virtual robots.txt. Everything that actually matters, structured data, AI crawler management, llms.txt generation, meta tags, gets added through a plugin, and the plugin ecosystem has genuinely kept pace with 2026’s shift toward AI search, with several tools now generating llms.txt files and scoring AI readiness out of the box. The trade-off for that flexibility is real: you’re choosing, installing, and maintaining that stack yourself, and a badly chosen plugin combination can create more problems than it solves.
Every other platform in this series makes a set of decisions for you. Shopify decides your Product schema. Wix decides your default meta tag structure. WordPress decides nothing. It’s a publishing framework, not a finished product, and what you get out of it depends entirely on what you put into it.
That’s a strength and a liability depending on what you’re trying to do. This page covers what WordPress genuinely leaves to you, which plugins have actually caught up with AI-era search, and where the platform’s total flexibility becomes a real maintenance responsibility rather than a convenience.
The trade you’re making
Full control, assembled by you
Unlike Durable or Canva Sites, which hide almost all technical decisions from you, WordPress exposes every one of them. There’s no vendor deciding what your robots.txt looks like or which schema types you’re allowed to use. That also means there’s no vendor doing it for you.
What core WordPress actually includes on its own is thin: an automatically generated XML sitemap at yourdomain.com/wp-sitemap.xml since WordPress 5.5, and a basic virtual robots.txt that most sites never look at. No schema. No llms.txt. No AI crawler management. No meta description field on a default post without a plugin adding one. If you installed WordPress and never touched a plugin, an AI tool trying to extract structured facts about your business would find very little to work with.
This is the opposite starting point from a platform like Shopify, and it’s exactly why WordPress needs a different kind of guide than the rest of this series. The question isn’t “what does WordPress do for me,” it’s “what do I need to add, and which tool actually does it well.”
What to add
The plugin layer that actually matters in 2026
The WordPress SEO plugin landscape has shifted meaningfully. It used to be about meta tags and sitemaps. Now the better plugins handle a genuinely different job: making your content legible to AI crawlers, not just Google’s.
You choose one
llms.txt generation
Several major plugins, including Yoast, Rank Math, and SEOPress, now generate an llms.txt file that tells AI crawlers what your site covers and where your key content lives, the AI-era equivalent of a sitemap built for language models rather than search bots.
You choose one
Named AI crawler control
Some plugins let you allow or block specific AI crawlers, GPTBot, ClaudeBot, PerplexityBot, individually, without touching raw robots.txt syntax. This matters if you want your content readable by some AI tools but not others, for licensing or competitive reasons.
You choose one
Schema markup, deep and specific
Where Shopify or Wix give you a handful of automatic schema presets, a WordPress plugin can generate 15 or more schema types, Article, FAQ, Product, Review, LocalBusiness, HowTo, and stack several on a single page. This is more schema depth than any closed platform in this series offers.
A newer addition
AI visibility scoring
Some plugins now score how “AI-ready” a given page is, similar in spirit to the AI Visibility tool built into Wix’s dashboard, but as an add-on rather than a native feature.
You do not need all four of these in separate plugins. Most established SEO plugins now bundle schema, llms.txt, and crawler management into one tool. The mistake to avoid is running two full SEO plugins side by side, which reliably creates duplicate schema, conflicting robots.txt rules, or both fighting over the same meta fields.
The real cost
Where “you can do anything” turns into “you have to maintain everything”
The flip side of total flexibility is that WordPress makes zero decisions to protect you from a bad one. These are the places that consistently trip people up.
| Where flexibility becomes a burden | Fixable? | Who it hits hardest |
|---|---|---|
| Running two SEO plugins at once | Yes, deactivate one | Anyone who’s switched plugins without fully removing the old one |
| No structured data at all until you install something | Yes, pick one plugin and configure it | New sites in their first weeks |
| Page speed depends entirely on your hosting and theme choice | Yes, but requires research | Sites on cheap shared hosting or heavy themes |
| Security and updates are your responsibility | Yes, ongoing maintenance | Sites without a maintenance routine |
| Content quality signals (author bios, dates) aren’t automatic | Yes, manual setup | Sites with anonymous or unattributed content |
1. Two SEO plugins running together is the single most common self-inflicted problem
Avoidable entirely
It happens more often than you’d expect: someone installs Rank Math to try it, doesn’t fully deactivate Yoast, and now has two plugins independently generating sitemaps, writing conflicting robots.txt rules, and inserting duplicate schema on the same pages. Neither Google nor an AI crawler handles that gracefully. Duplicate or conflicting structured data is often worse than having none at all, since it signals an unreliable source rather than a clear one.
Pick one main SEO plugin. If you’re testing a replacement, fully deactivate and delete the old one first, and most major plugins now include a one-click migration tool specifically to make that switch clean.
2. A brand-new WordPress site has nothing for AI tools to work with
Fixable in an afternoon
Because core WordPress adds no schema and no llms.txt on its own, a freshly installed site is genuinely invisible to the structural signals AI tools rely on, even if the content itself is good. This isn’t a bug, it’s just what an unconfigured publishing framework looks like. The fix is simply: pick a plugin, run its setup wizard, and don’t skip the schema and llms.txt steps because they seem optional. They’re the parts that matter most for how AI tools read your site.
Free tool
Not sure if your plugin setup is actually working?
Run a free audit and get exact, platform-specific fixes for AI and Google search visibility. No account needed.
3. Speed is a hosting decision, not a WordPress feature
Fixable, requires research upfront
Unlike Wix or Shopify, where hosting and page speed are handled entirely by the platform, WordPress’s performance is a direct function of your hosting provider, your theme, and how many plugins you’re running. Cheap shared hosting and a bloated theme will produce a genuinely slow site regardless of how well you’ve configured your SEO plugin, and page speed affects both Google ranking and how efficiently AI crawlers can process your pages.
This is worth researching before you build, not after. A managed WordPress host with good caching built in, and a lightweight, well-coded theme, solves most of this before you’ve written a line of content.
4. E-E-A-T signals don’t appear unless you add them deliberately
Fixable manually
AI tools weigh trust signals heavily when deciding what to cite: visible author bios, real publish and update dates, and a clear connection between your content and an actual person or organization. A default WordPress theme often buries or omits these entirely.
Add a real author bio to your posts, keep your published and last-updated dates visible, and use Person and Organization schema (most SEO plugins can generate this) to make the connection explicit rather than implied. This is one of the more overlooked levers for content that AI tools are willing to cite.
Fit check
Who should actually build on WordPress
Good fit
You want maximum control and own your infrastructure
Content-heavy sites, publishers, and anyone who wants full portability with no platform lock-in, and who’s willing to choose and maintain a plugin stack rather than accept defaults.
Action checklist
Setting up WordPress for AI and Google visibility from zero
If you’re starting fresh or auditing an existing site, work through this in order.
- Confirm you’re on one SEO plugin, not two. Check your plugins list. If you see more than one full SEO suite, deactivate and remove all but one before doing anything else.
- Run your chosen plugin’s setup wizard fully. Don’t skip the schema and llms.txt configuration steps, even if they’re marked optional.
- Generate your llms.txt file and check it’s actually live. Visit yourdomain.com/llms.txt after generating it to confirm it’s populated correctly.
- Add schema to your key page types. Article for blog posts, FAQPage for any Q&A content, LocalBusiness or Organization if relevant, Product if you’re selling anything.
- Add real author bios and visible dates to your content. This is one of the clearest trust signals both Google and AI tools weigh.
- Connect Google Search Console and submit your sitemap. Your plugin-generated sitemap is almost always more complete than core WordPress’s default.
- Check your hosting and theme for speed, not just features. Run your homepage through PageSpeed Insights. If it’s slow, the fix is usually hosting or theme, not another plugin.
- Review your AI crawler settings deliberately. Decide which AI bots you want reading your content, rather than leaving the default wide open or accidentally blocking all of them.
Key takeaways
- Core WordPress gives you almost nothing for AI search or Google visibility on its own. Everything meaningful, schema, llms.txt, AI crawler control, comes from a plugin you choose.
- The plugin ecosystem has genuinely caught up with AI-era search, with several major tools now generating llms.txt files and offering deeper schema coverage than any closed platform in this series.
- Running two SEO plugins at once is the most common self-inflicted problem on WordPress, reliably producing conflicting sitemaps, robots.txt rules, and duplicate schema.
- Page speed on WordPress is a hosting and theme decision, not a platform feature, unlike Wix or Shopify where it’s handled for you.
- E-E-A-T signals like author bios and visible dates don’t appear automatically and need deliberate setup, but they’re one of the clearer levers for AI tools deciding what to cite.
Check your setup actually worked, with INDEXED.
Because WordPress depends entirely on what you configure, it’s the platform in this series where “I installed the plugin” and “it’s actually working correctly” are most likely to be two different things.
INDEXED. is a free audit tool that checks whether your schema, meta tags, and AI visibility signals are actually live and correctly configured, not just installed. Paste your URL and get a plain-language report on indexing status, page titles, AI visibility signals, and mobile performance, with specific next steps rather than a wall of technical flags. It works well alongside the Google visibility fundamentals and tools covered elsewhere on this site.
Free tool
See what’s actually stopping your WordPress site from getting found
Run a free audit and get exact, platform-specific fixes for AI and Google search visibility. No account needed.
Common questions about WordPress, AI search, and Google
Barely. Core WordPress includes a basic automatic sitemap and a virtual robots.txt file, and nothing else: no schema, no llms.txt, no AI crawler management. Everything meaningful comes from a plugin, which is a deliberate design choice rather than an oversight. WordPress is a framework, not a finished tool.
There isn’t a single correct answer, but Yoast, Rank Math, AIOSEO, and SEOPress have all added llms.txt generation and AI crawler management as of 2026. Rank Math’s free tier is unusually generous with schema types, SEOPress offers flat pricing across unlimited sites, and Yoast leans toward guided setup for less technical users. Pick one, not several.
It’s a file, similar in spirit to robots.txt, that tells AI crawlers what your site covers and where your most important content lives. It’s not required for basic indexing, but it’s a genuinely useful, low-effort way to guide how AI tools understand your site’s structure, and most major SEO plugins now generate it automatically.
Almost always one of three things: cheap shared hosting without proper caching, a heavy or poorly coded theme, or too many plugins doing overlapping work. Unlike a closed platform, WordPress won’t warn you when these add up. Check your hosting plan and theme first before assuming a plugin is the problem.
No, don’t. Running two full SEO plugins reliably produces duplicate sitemaps, conflicting robots.txt rules, and duplicate schema markup on the same pages, which confuses both Google and AI crawlers rather than helping them. Pick one main plugin and add narrow, single-purpose tools alongside it if you need something specific it doesn’t cover.
They solve it differently. Webflow gives you more native, no-code control over technical fundamentals like robots.txt and canonical tags, but still needs custom code for schema. WordPress gives you deeper, more flexible schema options through plugins, at the cost of needing to choose and maintain that plugin stack yourself. Neither has an automation advantage over the other for AI citation specifically; both require deliberate setup.
Not on its own, but more thoroughly than almost any other platform once you add a plugin. A single plugin can generate 15 or more schema types and stack multiple types on one page, which is deeper coverage than the automatic presets on closed platforms like Shopify or Wix.