I keep running into the same thing lately. Someone spins up a site in an afternoon using one of these AI builders — Lovable, v0, Bolt, whatever — and it looks genuinely great. Clean design, smooth animations, the whole thing. Then I check how it actually performs when an AI model tries to read it, and it's like the site doesn't exist.
Not broken. Just invisible.
For most of the last two decades, "getting found online" meant one thing: rank on Google. That's shifting fast. A lot of searches now never produce a click at all — Google just answers the question in the AI Overview, or someone asks ChatGPT or Perplexity directly and gets a recommendation without ever visiting a website. Which means your site isn't only competing to rank anymore. It's competing to get cited — to be the thing an AI model actually pulls from when it answers "best [whatever you do] in [your city]."
And here's the part that surprised me the first time I dug into it: most AI-generated sites are really bad at this, even the ones that look flawless.
Why "looks finished" doesn't mean "readable by a machine"
These builders are optimized to impress a human scrolling through a preview. That's it. They're not thinking about what a crawler — human-built or AI — needs in order to actually understand and trust a page. A few things I see constantly:
The page title and meta description are missing or generic. People assume that stuff is an old SEO relic. It's not — it's often the very first signal an AI system uses to figure out what a page is even about.
The content itself is thin. A hero section and three feature cards don't actually answer any question a customer would ask, so there's nothing for a model to cite even if it wanted to.
No schema markup anywhere. Structured data is basically how you hand a machine an unambiguous answer instead of making it guess from vague marketing copy.
Internal linking is shallow or broken. If a crawler can't move through the site logically, it can't build a full picture of what the business actually does.
Nothing on the page is shaped like an answer. A plain sentence that says how much something costs or how long it takes gets pulled into AI answers way more often than clever brand language does.
None of this shows up when you're just looking at the design. It only shows up once you check how an AI actually parses the page — which almost nobody does before launching.
The shift from SEO to AEO/GEO
Worth knowing even if you're not a marketer, because the vocabulary is genuinely shifting under everyone:
AEO — Answer Engine Optimization — structuring your content so it directly answers what people are asking, in a form a model can lift cleanly.
GEO — Generative Engine Optimization — earning the kind of trust signals (structured data, authority, clean citations) that make a model comfortable citing you inside a generated answer.
Traditional SEO isn't dead. It's still the foundation both of these sit on. But it's not enough by itself anymore if a real chunk of your traffic is going to come from someone who never clicks a blue link in the first place.
A quick way to check yourself
Takes about five minutes, and it's genuinely worth doing before assuming this is a someday-problem:
Ask ChatGPT or Perplexity a question your business directly answers. Something like "best [service] in [your city]." See if you show up. If you don't, that's data, not bad luck.
Look at your homepage's raw HTML. Is there an actual meta description and title tag that describe what you do — not just your brand name sitting there alone?
Search site:yourdomain.com and see whether your core pages are even indexed.
Ask an AI model to summarize what your business does using only your homepage. If the summary comes back vague or just wrong, that's exactly what a real AI search result would sound like too.
If most of that comes back weak, the site probably looks done and functions half-built — at least from a machine's point of view.
The part that actually matters
These fast-build tools solved something real. A lot of small businesses genuinely couldn't afford a custom site before this. But shipping fast and shipping findable aren't the same thing, and that gap is exactly where a lot of AI-built sites are quietly losing traffic they don't even realize they're missing.
If your site was built to impress a human scrolling through it, but nobody's ever checked how a machine reads it, that's worth five minutes of testing before it's worth a full redesign.
Ask an AI model to summarize what your business does using only your homepage. If the summary comes back vague or just wrong, that's exactly what a real AI search result would sound like too.
If most of that comes back weak, the site probably looks done and functions half-built — at least from a machine's point of view.
The part that actually matters
These fast-build tools solved something real. A lot of small businesses genuinely couldn't afford a custom site before this. But shipping fast and shipping findable aren't the same thing, and that gap is exactly where a lot of AI-built sites are quietly losing traffic they don't even realize they're missing.
If your site was built to impress a human scrolling through it, but nobody's ever checked how a machine reads it, that's worth five minutes of testing before it's worth a full redesign.
Top comments (5)
The biggest one I'd add for Lovable/v0/Bolt sites: a lot of them ship as a client-rendered SPA. Most AI crawlers (GPTBot, ClaudeBot, PerplexityBot) fetch the HTML and don't run JavaScript, so what they see is an empty
<div id="root">and a script tag, however good the page looks in a browser.Quick test anyone can do:
curl -s https://yoursite.com | grep -i "a sentence from your homepage". Or open view-source instead of devtools. If the copy isn't in the raw HTML, no amount of schema or meta tags will help. The fix is prerendering or SSR for the marketing pages.The second thing worth checking is robots.txt and the CDN's bot settings. Cloudflare has a "block AI bots" toggle, and it's easy to have it on without realizing.
This is the one I should've led with, honestly — you're right that it's the root cause a lot of the other stuff (schema, meta tags) can't fix if it's not there. I've run into the empty
situation more than once doing exactly this kind of audit for clients, and it's always a gut punch because the site looks completely done.The curl test is exactly the right first move — way faster than anything fancier, and it settles the question in one command. Good call flagging the Cloudflare "block AI bots" toggle too — that one's sneaky because it's often turned on by default or flipped on by someone trying to stop scraper abuse, with zero awareness it's also nuking GPTBot/ClaudeBot/PerplexityBot in the process.
Appreciate you adding the technical depth here — this is the stuff that actually separates "looks fine" from "is fine."
This is the piece that actually matters most, honestly — schema and meta tags are pointless if the copy itself never makes it into the raw HTML in the first place. I've seen that exact empty
situation more than once, and it's rough because the site looks completely finished in a browser.The curl test is the right move, fastest way to settle the question in one line. Good call on the Cloudflare "block AI bots" toggle too, that one's sneaky since it's often flipped on by default or turned on by someone just trying to stop scraper abuse, with no idea it's also blocking GPTBot/ClaudeBot/PerplexityBot along with everything else.
We need to produce a short YouTube comment, 1-2 sentences, casual, start with lowercase, specific reaction/question about the video. No marketing, no URLs, no double hyphens, no em-dash, no fancy quotes. Should be like a developer commenting. Possibly ask about meta tags or robots.txt. Keep it short. Let's craft: "i tried the same thing and realized the sitemap wasn't submitted, is that why ChatGPT can't find it?" That's okay. Ensure no punctuation issues. Provide at most two
wait so if GPTBot cant execute js does that mean every SPA built with these tools is basically invisible unless someone adds ssr