The Problem with AI Websites — Transcript
Full transcript
- 0:00You spent 10 minutes with AI and got a
- 0:01beautiful website, clean design, nice
- 0:03photos, looks perfect on your phone. 3
- 0:05weeks later, you're still invisible on
- 0:07Google. Now, everyone starts blaming the
- 0:09same thing. AI content doesn't rank.
- 0:11That's not it. AI content ranks fine.
- 0:14The real problem is nobody told the AI
- 0:16what Google actually needs to crawl your
- 0:18site, to understand it, and to trust it.
- 0:21There are four things missing from
- 0:22almost every AI-built website, and the
- 0:24first one means Google might not even
- 0:27have read your site yet. Most AI website
- 0:29builders don't actually build websites.
- 0:31They build JavaScript applications,
- 0:32which means when Google shows up, the
- 0:34page is basically blank, a shell of code
- 0:37and a note that says the content is
- 0:39still loading. Google has to come back
- 0:41later, run all that JavaScript, and
- 0:43wait. That delays your indexing, and on
- 0:45some pages Google will just give up.
- 0:47Now, here's the part that I haven't seen
- 0:49very many people talking about. Google's
- 0:50bot will at least try to look at
- 0:53JavaScript. The AI crawlers won't.
- 0:55ChatGPTs, Claudes, Perplexities, they
- 0:58read the raw code, and that's it. To an
- 1:00AI agent, that beautiful JavaScript site
- 1:03is basically invisible. Everyone's
- 1:05racing to show up in AI search with a
- 1:07website that the AI systems can't even
- 1:08read. The fix is old-school, statically
- 1:11generated HTML, plain pages fully built
- 1:14before anyone requests them. Google
- 1:16reads them instantly. AI crawlers read
- 1:18them instantly. It's how sites were
- 1:20built 20 years ago, and it's quietly
- 1:23becoming the correct way to build them
- 1:24again. Now, even the site that Google
- 1:26can read can still be a complete mess.
- 1:29That's problem number two, your sitemap.
- 1:31That's the list of pages on your website
- 1:33that you hand to Google. Most AI
- 1:34builders create it once and then never
- 1:36update it. So, you add a page and Google
- 1:39never gets the memo. It should
- 1:40regenerate every single time your site
- 1:42changes. robots.txt, this is the file
- 1:45that tells crawlers what they're allowed
- 1:47to look at. I've seen AI builders ship
- 1:49sites where it's accidentally blocking
- 1:50half of the website or not existing at
- 1:52all. The owner's wondering why nothing
- 1:54ranks, and their own site is turning
- 1:56Google away at the door. While you're in
- 1:57there, go ahead and add llms.txt. It's a
- 2:00plain summary of your site for AI
- 2:01systems. And let me be straight with
- 2:03you, it is completely unproven. No AI
- 2:05company has confirmed they use it, but
- 2:07it takes like 30 seconds and it costs
- 2:09nothing. Cheap insurance. Anyone selling
- 2:11llms.text as a ranking secret is selling
- 2:15you snake oil. Okay, now the sneaky one.
- 2:17Your homepage can live at four different
- 2:19addresses. With www, without www, with a
- 2:23trailing slash, and without a trailing
- 2:25slash. To Google, that's four separate
- 2:27pages and your ranking power gets split
- 2:29across the copies. A canonical tag is
- 2:32designed to fix that. One line of code
- 2:34that says, "This here is the original
- 2:36version." Most AI builders skip it. And
- 2:38when you delete a page, your site should
- 2:40tell Google it's gone. A lot of AI built
- 2:42sites say everything's fine. So dead
- 2:45pages pile up in the index. Ghosts and
- 2:47clones. Google's picture of your site
- 2:49gets blurrier and blurrier. Fix all of
- 2:52that and Google still might not know
- 2:54what your business actually does. This
- 2:56is problem number three. A human lands
- 2:58on your site and gets it instantly. Van,
- 3:01phone number, 24/7 emergency plumber.
- 3:03Done. They know what you are. Google is
- 3:05a machine parsing code, guessing.
- 3:08Plumber? Supply store? Blog about
- 3:09plumbing? Schema's how you stop the
- 3:11guessing. Schema's code behind your
- 3:13pages that no visitor ever sees. It
- 3:15exists for machines and it states the
- 3:18facts in a format that they cannot
- 3:20misread. Exact name, address, phone
- 3:23numbers, hours, services, facts labeled.
- 3:25The types matter. Local business, what
- 3:28you are and where. Organization, who's
- 3:31behind it. Service schema on your
- 3:32service pages. Breadcrumb, so machines
- 3:34see how your pages connect. If you ask
- 3:37an AI to build you a website, you have
- 3:39to check the code after. Almost none of
- 3:42this is going to be there. You ask for a
- 3:44website and schema's not something you
- 3:45can see, so you don't know that it was
- 3:47missed. Now, the honest version, because
- 3:49schema does get hyped in both
- 3:50directions. It's not actually a ranking
- 3:52factor. Google said that over and over
- 3:54again and no one has proof that schema
- 3:56gets you cited by Chat GPT. What's
- 3:58actually confirmed is Google uses it to
- 4:00understand pages. Microsoft says the
- 4:02same thing for its AI. So, that's the
- 4:05real case. It's a clarity signal.
- 4:07Without it, machines piece your business
- 4:09together from marketing copy. Sometimes
- 4:11they get it wrong. This is cheap to add.
- 4:13It's dumb to skip and anyone selling it
- 4:15as an AI ranking hack is lying to you.
- 4:18Okay, so that's how machines read a
- 4:19page. Problem four is what the AI wrote
- 4:23on them. AI builders write pages for
- 4:25humans, not for search. Title tags and
- 4:28H1s, the page's label in the search
- 4:30results and the headline at the top,
- 4:32they need to match what people actually
- 4:34type into Google. An AI builder writes
- 4:36solutions for your home comfort needs.
- 4:38Sounds nice. Matches nothing that anyone
- 4:40will ever type into Google or an AI for
- 4:43that matter. The first paragraph should
- 4:45let a visitor finish their goal
- 4:46immediately. What you do, where you do
- 4:49it, how to hire you. First thing on the
- 4:51page. Google watches how people behave.
- 4:54When visitors instantly find what they
- 4:56came for, that tells Google the page
- 4:58delivers. AI builders open with mission
- 5:01statements, uh company histories. I can
- 5:04guarantee to you that no one is typing
- 5:07plumber near me into Google because
- 5:08they're looking for history lessons on
- 5:11local plumbing businesses. Okay, and
- 5:13your pages should link in clean branches
- 5:15like a family tree so Google sees how
- 5:16everything relates. AI builders link
- 5:18everything to everything through the nav
- 5:20menu that creates a pile, not a topical
- 5:23hierarchy tree. So, that's what happens
- 5:25when you say build me a website, a site
- 5:27that Google can't read and index full of
- 5:29ghosts, no schema, pages with nothing
- 5:31for a search engine to match. Now, you
- 5:33can fix all of that by hand. People in
- 5:35my community do it every day, but the AI
- 5:37didn't fail because AI can't build
- 5:39websites. It failed because nobody gave
- 5:41it the right instructions. So, I'm in
- 5:43the process of building a website
- 5:44generator where the machine won't skip
- 5:46this stuff. Statically generated HTML,
- 5:49so Google and the AI crawlers actually
- 5:50see it. Full schema on every page, title
- 5:53tags and first paragraphs built for
- 5:54search intent, not for slogans. A site
- 5:57map that we generate itself, clean
- 5:59canonicals, correct error codes, links
- 6:01built as a tree, even the LMS text. None
- 6:04of it's optional, because build me a
- 6:06website gets you a very pretty site that
- 6:08won't rank. The instructions are
- 6:11everything. We made them permanent. Now,
- 6:13whether you want to wait for that
- 6:13generator or fix your site by hand,
- 6:16starting today, you can join my school
- 6:17group to grab the full technical
- 6:19checklist of everything I walked
- 6:21through, every item from this video,
- 6:23what to check, how to fix it. It's
- 6:24inside my AI SEO mastery community. Over
- 6:273,000 people are in there, too. Now, if
- 6:29you want to go deeper on writing pages
- 6:31that match search intent, check out this
- 6:33video right here. I'll see you in the
- 6:35next one.
About this transcript
This page contains the full transcript of The Problem with AI Websites by Caleb Ulku, generated from the public captions YouTube serves with the video. The transcript has 1,268 words across 187 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.
What you can do with it
Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to translate the transcript into 100+ languages.
Free YouTube transcript tool
YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, translation to 100+ languages, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.