The Hidden Mistake Killing Your AI Search Traffic

Every website I build still has to work the old way: title tags, meta descriptions, backlinks, page authority, all the fundamentals that get a site ranking on Google. That part hasn’t gone anywhere. What’s changed is that ranking well on Google is no longer the only test a website has to pass. More and more of my own clients’ traffic is starting somewhere else entirely, inside ChatGPT, Perplexity, or Google’s own AI Overviews, and those engines don’t read a page the same way a classic search crawler does.

A site built purely for Google and a site built to also work for AI search aren’t the same thing. The gap between them is structural, and it shows up on every page, not just one.

What “built for Google” actually means

A Google-first page is optimised to win a spot in a list of blue links. That means keyword placement, internal linking, page authority, and enough backlinks to be trusted. It’s built to be clicked, then read by a human. None of that is wrong, it’s still the foundation every site needs. It’s just not the whole job anymore.

What “built for AI search” adds on top

An AI engine isn’t trying to send someone to your page, it’s trying to lift an answer out of it and hand that answer straight to the person asking. To do that, it needs the content structured so a machine can extract it cleanly: real questions answered in plain language, content attributed to a named person rather than left anonymous, and schema markup in the code that tells the engine exactly what it’s looking at, an FAQ, a set of steps, a local business, an article, before it ever reads a word of the visible text.

A real example from my own site

Every service page on weightmandigital.com carries FAQPage schema, real question-and-answer pairs marked up in the code. When I checked it through Google’s Rich Results Test, it came back fully valid, no errors. But it doesn’t show up as a rich result in Google search. Google restricted that visual FAQ snippet to government and health sites back in August 2023, so for a business like mine, that accordion-style result in search just isn’t available anymore, however correctly it’s built.

I kept the schema in anyway. Google might not reward it with a visual snippet, but AI engines still read that exact same structured data to pull a direct answer. The thing Google stopped showing is the same thing AI search is quietly relying on. Building it “for Google” and building it “for AI” turned out to be the same piece of code, just judged by two different audiences.

Close-up of a hand typing with a subtle mechanical seam at the wrist, symbolising AI quietly working alongside human input
The machine-readable layer sits quietly behind everything now, whether you notice it or not.

Why the Google-first fundamentals still matter

None of this is a case for abandoning traditional SEO. Domain authority, backlinks, and a technically sound site are still what get a page trusted enough to be crawled and cited in the first place. AI engines aren’t magic, they still favour sites that already carry real authority. Building for AI search is an addition to the fundamentals, not a replacement for them.

What a dual-purpose site looks like day to day

In practice this means every page I build carries proper schema markup from the start (I build a schema field into every site I make, rather than bolting it on afterwards), headings that ask the actual question a customer would type, and content that’s attributed to a real person, not left as anonymous copy. None of it changes how the page reads to a human visitor. It just means there’s something underneath for a machine to find as well.

Frequently Asked Questions

Do I need two separate websites, one for Google and one for AI search?

No. You need one website built to do both jobs. The technical groundwork, structured data, clear headings, direct answers, works for AI engines without taking anything away from how Google crawls and ranks the same page.

If Google no longer shows my FAQ schema as a rich result, is it still worth adding?

Yes. Google restricted FAQ rich results to government and health sites in August 2023, so most businesses won’t see the visual snippet in search anymore. But AI engines like ChatGPT, Perplexity and Google’s own AI Overviews still read that same structured data to pull direct answers. The visual reward from Google disappeared. The AI-readable substance underneath didn’t.

Does building for AI search mean I can stop doing traditional SEO?

No, if anything it makes traditional SEO more important, not less. Domain authority and backlinks are still what get a site trusted enough to be crawled, cited and pulled from in the first place. AI-readiness sits on top of that foundation, it doesn’t replace it.

How do I know if my current website is AI-search ready?

Check whether your pages have structured data (schema markup) in the source code, whether your headings ask and answer real questions in plain language, and whether content is attributed to a named person rather than left anonymous. If none of that’s there, an AI engine has nothing to extract, however well the page ranks in a normal Google search.

Not sure if your site is built for AI search, or just for Google?

I’ll check your structured data, your schema markup, and how your content actually reads to an AI engine, no jargon, just a straight answer on where you stand.

Get My Free Review

author avatar
Neil Weightman

Privacy Preference Center