Google's AI Overview now shows up above the ten blue links on most informational searches. ChatGPT Search, Perplexity, and Claude are pulling in a real chunk of commercial research too. Some late 2025 studies put the number of high-intent queries routing through an AI surface at close to 28%. That number is only going up.
This matters for how we build sites, not just how we write blog posts.
AI engines read your markup, not your design
When an AI engine answers a question, it's not rendering your page in a browser and admiring the parallax scroll. It's pulling structured content from your HTML. Headings, semantic tags, schema markup, clean paragraph structure. If your content is buried under a stack of nested divs, wrapped in inline styles, and rendered by a page builder that outputs the same generic markup for every block on every site, the AI engine has more work to do to figure out what your page is actually about.
We've made this point before in Thinking Beyond Page Builders, and it applies directly here. A page built in Elementor isn't hand-coded semantic HTML. It's a stack of div-in-div-in-div output from a drag and drop builder, styled with inline CSS and shortcodes. That's fine for a human scrolling through it. It's a mess for a crawler or an LLM trying to extract a clear answer to cite.
Clean code was already a ranking factor
Google has cared about clean, fast, well-structured pages for years. Site speed and Core Web Vitals are direct ranking factors, and a one second delay quietly kills conversion rate, as we broke down in What a Slow Website Actually Costs Your Business. Most Denver business sites load in 4 to 6 seconds against a 2.5 second threshold Google considers acceptable, and we've written about why that happens in Why Your Denver Business Website Is Slow.
What's changed is the stakes. It used to be that a slow, messy site would rank lower and lose some traffic. Now it also risks getting skipped entirely when an AI engine is scanning for a clean, citable source. If your content is technically correct but buried in bad markup, you're invisible to a system that doesn't click around, it just reads.
What we build to handle this
Our primary stack is Astro paired with Payload CMS. Astro ships minimal JavaScript and renders clean, semantic HTML by default. That's a good starting position for both traditional SEO and whatever AI engines end up prioritizing. Payload gives clients a real content model instead of a pile of shortcodes, which means the content structure stays consistent and easy to parse, page after page. We compared this stack directly against the alternative in Astro vs WordPress: Which One Is Right for Your Business?.
For WordPress projects, we build with Timber and Twig instead of a page builder, and we use Advanced Custom Fields so clients can edit content without touching a builder's bloated block library. The output is clean HTML with a real template structure behind it, the reasoning for which we laid out in Timber/Twig vs Elementor: Why WordPress Page Builders Are Losing Ground. Combined with our performance targets, under 2 second load times and 95+ Lighthouse scores, that gives both search engines and AI engines a fast, well-structured page to work with instead of a mess to untangle.
This is part of a longer game
None of this replaces good content or real expertise on the page. Structure gets you found and cited, it doesn't substitute for having something worth citing. We made this point in Why SEO Is A Long-Term Investment: a solid strategy starts with technical fundamentals, and every piece of content built on top of that becomes a long-term asset. A technically clean site doesn't guarantee AI Overview citations or top rankings. It just removes the technical barriers standing between your content and the systems trying to read it.
If your current site is running on a page builder and you're wondering whether it's holding you back in ways beyond just page speed, that's a conversation worth having before your next redesign, not after a competitor starts showing up in AI search results and you don't.
Want to see what a clean rebuild looks like for your site? Check out our work or get in touch and we'll walk through it.