YouTube2Text

The Problem with AI Websites — Transcript

by Caleb Ulku · 1,268 words · 187 segments · language en · Watch on YouTube

Full transcript

  1. 0:00You spent 10 minutes with AI and got a
  2. 0:01beautiful website, clean design, nice
  3. 0:03photos, looks perfect on your phone. 3
  4. 0:05weeks later, you're still invisible on
  5. 0:07Google. Now, everyone starts blaming the
  6. 0:09same thing. AI content doesn't rank.
  7. 0:11That's not it. AI content ranks fine.
  8. 0:14The real problem is nobody told the AI
  9. 0:16what Google actually needs to crawl your
  10. 0:18site, to understand it, and to trust it.
  11. 0:21There are four things missing from
  12. 0:22almost every AI-built website, and the
  13. 0:24first one means Google might not even
  14. 0:27have read your site yet. Most AI website
  15. 0:29builders don't actually build websites.
  16. 0:31They build JavaScript applications,
  17. 0:32which means when Google shows up, the
  18. 0:34page is basically blank, a shell of code
  19. 0:37and a note that says the content is
  20. 0:39still loading. Google has to come back
  21. 0:41later, run all that JavaScript, and
  22. 0:43wait. That delays your indexing, and on
  23. 0:45some pages Google will just give up.
  24. 0:47Now, here's the part that I haven't seen
  25. 0:49very many people talking about. Google's
  26. 0:50bot will at least try to look at
  27. 0:53JavaScript. The AI crawlers won't.
  28. 0:55ChatGPTs, Claudes, Perplexities, they
  29. 0:58read the raw code, and that's it. To an
  30. 1:00AI agent, that beautiful JavaScript site
  31. 1:03is basically invisible. Everyone's
  32. 1:05racing to show up in AI search with a
  33. 1:07website that the AI systems can't even
  34. 1:08read. The fix is old-school, statically
  35. 1:11generated HTML, plain pages fully built
  36. 1:14before anyone requests them. Google
  37. 1:16reads them instantly. AI crawlers read
  38. 1:18them instantly. It's how sites were
  39. 1:20built 20 years ago, and it's quietly
  40. 1:23becoming the correct way to build them
  41. 1:24again. Now, even the site that Google
  42. 1:26can read can still be a complete mess.
  43. 1:29That's problem number two, your sitemap.
  44. 1:31That's the list of pages on your website
  45. 1:33that you hand to Google. Most AI
  46. 1:34builders create it once and then never
  47. 1:36update it. So, you add a page and Google
  48. 1:39never gets the memo. It should
  49. 1:40regenerate every single time your site
  50. 1:42changes. robots.txt, this is the file
  51. 1:45that tells crawlers what they're allowed
  52. 1:47to look at. I've seen AI builders ship
  53. 1:49sites where it's accidentally blocking
  54. 1:50half of the website or not existing at
  55. 1:52all. The owner's wondering why nothing
  56. 1:54ranks, and their own site is turning
  57. 1:56Google away at the door. While you're in
  58. 1:57there, go ahead and add llms.txt. It's a
  59. 2:00plain summary of your site for AI
  60. 2:01systems. And let me be straight with
  61. 2:03you, it is completely unproven. No AI
  62. 2:05company has confirmed they use it, but
  63. 2:07it takes like 30 seconds and it costs
  64. 2:09nothing. Cheap insurance. Anyone selling
  65. 2:11llms.text as a ranking secret is selling
  66. 2:15you snake oil. Okay, now the sneaky one.
  67. 2:17Your homepage can live at four different
  68. 2:19addresses. With www, without www, with a
  69. 2:23trailing slash, and without a trailing
  70. 2:25slash. To Google, that's four separate
  71. 2:27pages and your ranking power gets split
  72. 2:29across the copies. A canonical tag is
  73. 2:32designed to fix that. One line of code
  74. 2:34that says, "This here is the original
  75. 2:36version." Most AI builders skip it. And
  76. 2:38when you delete a page, your site should
  77. 2:40tell Google it's gone. A lot of AI built
  78. 2:42sites say everything's fine. So dead
  79. 2:45pages pile up in the index. Ghosts and
  80. 2:47clones. Google's picture of your site
  81. 2:49gets blurrier and blurrier. Fix all of
  82. 2:52that and Google still might not know
  83. 2:54what your business actually does. This
  84. 2:56is problem number three. A human lands
  85. 2:58on your site and gets it instantly. Van,
  86. 3:01phone number, 24/7 emergency plumber.
  87. 3:03Done. They know what you are. Google is
  88. 3:05a machine parsing code, guessing.
  89. 3:08Plumber? Supply store? Blog about
  90. 3:09plumbing? Schema's how you stop the
  91. 3:11guessing. Schema's code behind your
  92. 3:13pages that no visitor ever sees. It
  93. 3:15exists for machines and it states the
  94. 3:18facts in a format that they cannot
  95. 3:20misread. Exact name, address, phone
  96. 3:23numbers, hours, services, facts labeled.
  97. 3:25The types matter. Local business, what
  98. 3:28you are and where. Organization, who's
  99. 3:31behind it. Service schema on your
  100. 3:32service pages. Breadcrumb, so machines
  101. 3:34see how your pages connect. If you ask
  102. 3:37an AI to build you a website, you have
  103. 3:39to check the code after. Almost none of
  104. 3:42this is going to be there. You ask for a
  105. 3:44website and schema's not something you
  106. 3:45can see, so you don't know that it was
  107. 3:47missed. Now, the honest version, because
  108. 3:49schema does get hyped in both
  109. 3:50directions. It's not actually a ranking
  110. 3:52factor. Google said that over and over
  111. 3:54again and no one has proof that schema
  112. 3:56gets you cited by Chat GPT. What's
  113. 3:58actually confirmed is Google uses it to
  114. 4:00understand pages. Microsoft says the
  115. 4:02same thing for its AI. So, that's the
  116. 4:05real case. It's a clarity signal.
  117. 4:07Without it, machines piece your business
  118. 4:09together from marketing copy. Sometimes
  119. 4:11they get it wrong. This is cheap to add.
  120. 4:13It's dumb to skip and anyone selling it
  121. 4:15as an AI ranking hack is lying to you.
  122. 4:18Okay, so that's how machines read a
  123. 4:19page. Problem four is what the AI wrote
  124. 4:23on them. AI builders write pages for
  125. 4:25humans, not for search. Title tags and
  126. 4:28H1s, the page's label in the search
  127. 4:30results and the headline at the top,
  128. 4:32they need to match what people actually
  129. 4:34type into Google. An AI builder writes
  130. 4:36solutions for your home comfort needs.
  131. 4:38Sounds nice. Matches nothing that anyone
  132. 4:40will ever type into Google or an AI for
  133. 4:43that matter. The first paragraph should
  134. 4:45let a visitor finish their goal
  135. 4:46immediately. What you do, where you do
  136. 4:49it, how to hire you. First thing on the
  137. 4:51page. Google watches how people behave.
  138. 4:54When visitors instantly find what they
  139. 4:56came for, that tells Google the page
  140. 4:58delivers. AI builders open with mission
  141. 5:01statements, uh company histories. I can
  142. 5:04guarantee to you that no one is typing
  143. 5:07plumber near me into Google because
  144. 5:08they're looking for history lessons on
  145. 5:11local plumbing businesses. Okay, and
  146. 5:13your pages should link in clean branches
  147. 5:15like a family tree so Google sees how
  148. 5:16everything relates. AI builders link
  149. 5:18everything to everything through the nav
  150. 5:20menu that creates a pile, not a topical
  151. 5:23hierarchy tree. So, that's what happens
  152. 5:25when you say build me a website, a site
  153. 5:27that Google can't read and index full of
  154. 5:29ghosts, no schema, pages with nothing
  155. 5:31for a search engine to match. Now, you
  156. 5:33can fix all of that by hand. People in
  157. 5:35my community do it every day, but the AI
  158. 5:37didn't fail because AI can't build
  159. 5:39websites. It failed because nobody gave
  160. 5:41it the right instructions. So, I'm in
  161. 5:43the process of building a website
  162. 5:44generator where the machine won't skip
  163. 5:46this stuff. Statically generated HTML,
  164. 5:49so Google and the AI crawlers actually
  165. 5:50see it. Full schema on every page, title
  166. 5:53tags and first paragraphs built for
  167. 5:54search intent, not for slogans. A site
  168. 5:57map that we generate itself, clean
  169. 5:59canonicals, correct error codes, links
  170. 6:01built as a tree, even the LMS text. None
  171. 6:04of it's optional, because build me a
  172. 6:06website gets you a very pretty site that
  173. 6:08won't rank. The instructions are
  174. 6:11everything. We made them permanent. Now,
  175. 6:13whether you want to wait for that
  176. 6:13generator or fix your site by hand,
  177. 6:16starting today, you can join my school
  178. 6:17group to grab the full technical
  179. 6:19checklist of everything I walked
  180. 6:21through, every item from this video,
  181. 6:23what to check, how to fix it. It's
  182. 6:24inside my AI SEO mastery community. Over
  183. 6:273,000 people are in there, too. Now, if
  184. 6:29you want to go deeper on writing pages
  185. 6:31that match search intent, check out this
  186. 6:33video right here. I'll see you in the
  187. 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.