Why your CMS determines your AI score
The problem with template bloat
I am going to say something that will not make me popular with part of the internet: most CMS platforms produce terrible HTML.
There. I said it.
AI models read HTML. That sounds simple, until you open the source code of an average WordPress site with Elementor and a handful of plugins. Then you see a tangle of `
At Kobalt I regularly open the source code of client websites. Sometimes I genuinely need to take a breath. The content is excellent. The HTML the CMS produces from it? A disaster. And if I struggle with it after twenty years of web development, do not expect an AI crawler to understand the structure.
Your CMS is not neutral. It determines how clean your HTML is, how consistent your heading structure, how easily you can implement Schema.org and how fast your pages load. These are all factors that directly influence your AI score.
WordPress: powerful but messy without discipline
Let me start with the elephant in the room. WordPress powers 43% of the web. That is impressive and also a little terrifying.
The freedom of WordPress is its strength and its weakness. Anyone can install a plugin, add a page builder and generate markup that no system understands. I have seen WordPress sites with 47 active plugins. Forty-seven. That makes me go quiet for a moment.
- Gutenberg generates reasonably clean HTML, provided you do not stack too many plugins on top of it.
- Elementor, Divi and WPBakery are performance and markup disasters. Mountains of inline CSS, nested divs, shortcodes. They do not make me happy.
- Yoast and Rank Math make Schema.org accessible, but the output is generic and sometimes redundant.
- Themes vary enormously. A premium theme from a reputable developer is worlds apart from a free theme of unknown origin.
- Caching plugins are a necessity, not a luxury. Without cache, WordPress is almost always too slow for AI bots.
My conclusion on WordPress: it can work fine. But you need discipline. Use the block editor, no page builders. Choose a lightweight theme. Install only necessary plugins. Validate your HTML output regularly. That sounds like a checklist, but it is more of a way of life.
Headless CMS: the promise and the pitfall
Contentful, Sanity, Strapi: the developer community loves them. Content in a structured API, frontend entirely in your own hands. Clean HTML, fast builds, full control.
In theory, perfect for AI readability. In practice I see two pitfalls that teams keep falling into.
- Next.js and other React frameworks render client-side by default. No SSR or static generation configured? Then AI crawlers get an empty HTML shell. You are worse off than with WordPress. Let that sink in.
- The freedom of headless means Schema.org, Open Graph tags and robots.txt all need to be built manually. Teams without strong SEO knowledge regularly forget this. And then you have a beautiful frontend that is an empty box for AI models.
Laravel and custom solutions: the top of the spectrum
I am biased, I will admit that. At Kobalt we build a lot on Laravel. But there are substantive reasons that go beyond "this is what we know best."
A Laravel application with Blade templates generates server-rendered HTML by default. No JavaScript framework accidentally placing your content behind a hydration wall. You write the HTML you want, and that is what crawlers see. You implement Schema.org exactly as you want it. No plugin "handling it for you" in a way you do not fully understand.
The disadvantage is obvious: custom development costs more. For a marketing site of a small company that is not always justifiable. But for organizations where AI visibility seriously matters in the funnel? Then the investment in clean, manageable code is absolutely worth it.
Do not jump straight to custom development if WordPress suffices. But do know what you are giving up: development speed in exchange for HTML that requires discipline to keep clean. And that discipline is lacking in most teams, if I am being honest.
The best CMS choice is the one where your team can maintain the discipline to produce clean HTML. A perfectly configured WordPress site beats a sloppily built Laravel project. Always. Want to know how clean your HTML is? Take the free AEO scan.
Frequently asked questions
Do I need to switch CMS to improve my AI score?
Probably not. Most improvements are possible within your current CMS. Clean up HTML output, remove unnecessary plugins, implement Schema.org correctly. A CMS switch is a major investment you only justify when you have structural problems you cannot solve. And that is rarely the case.
Which CMS scores best on AI readability?
There is no universal answer, and I mean that. A well-configured WordPress site with minimal plugins scores better than a sloppily built headless app. The team behind the site is at least as important as the platform itself.
How do I check whether my CMS generates clean HTML?
Right-click, "View page source." Look at the ratio of content to markup. If you see ten lines of divs, spans and class names for every sentence of text, there is work to be done. Also use the W3C Markup Validator. It is old-fashioned but it works.
How does your website score on AI readiness?
Get your AEO score within 30 seconds and discover what you can improve.
RELATED ARTICLES
Why after 20 years of web development I still put performance first
From 56k modems to AI crawlers. The technology changes. The lesson does not. After twenty years of building, optimizing, and yes, making mistakes too, my conclusion is always the same: start with speed. The rest follows.
HTTP/2 and HTTP/3: faster protocols for AI crawlers
HTTP/1.1 is over 25 years old. And your server is probably still running it. Learn what HTTP/2 and HTTP/3 concretely do for AI crawlers, why multiplexing is a game changer, and how to enable it today.
Semantic HTML: the language humans, machines and AI understand
Seven layers of div nesting for a simple paragraph. I am not exaggerating. Semantic HTML is the difference between a website AI models understand and an impenetrable mess of div elements. And it takes you an afternoon to fix.