Claude's Watermarks Just Broke SEO — Transcript
Full transcript
- 0:00Anthropic just started watermarking
- 0:01every single word that Claude writes,
- 0:03invisible, embedded in the text itself,
- 0:05and it rides along when you paste it
- 0:07onto your website. So, if you've been
- 0:08publishing AI content, there's now a
- 0:10permanent mark on it saying where it
- 0:12came from. It's on everything, every
- 0:15single model launched since August 2nd
- 0:17across the API, Claude Code, Cowork, all
- 0:19of it, worldwide. It survives copy and
- 0:22paste. It survives editing. And
- 0:24Anthropic says a detector is coming.
- 0:26Plus, they're working on retrofitting
- 0:28the older models. So, follow that chain
- 0:30out. That mark is on your pages.
- 0:33Anthropic is going to ship the detector,
- 0:35and now Google knows exactly which pages
- 0:38on the internet were written by AI down
- 0:40to the exact paragraph. That's the fear,
- 0:43not the watermark itself, but what a
- 0:46search engine does once it can sort the
- 0:48entire index into human and machine.
- 0:52Now, if that flips into a demotion,
- 0:54every AI published page you got turns
- 0:56into a liability overnight. And there's
- 0:58no real way to walk this back at scale.
- 1:02That's the version currently circulating
- 1:03right now, and every link in it sounds
- 1:05reasonable. But none of this makes sense
- 1:08until you understand what the watermark
- 1:11actually is. Because almost everyone
- 1:13reporting on it got this part wrong. The
- 1:16watermark is not metadata. There's no
- 1:18hidden file attached to your text.
- 1:19There's no invisible characters buried
- 1:22in it. The watermark is the word choices
- 1:24themselves. When Claude writes, it's
- 1:26choosing each word from a set of
- 1:28options. The watermark nudges those
- 1:30choices in a pattern. Every individual
- 1:32word looks completely normal. But across
- 1:35a few hundred words, the pattern of
- 1:36choices adds up to a signature. This is
- 1:39why it survives copy and paste. You're
- 1:41still of course copying the words, and
- 1:43the words are the watermark. It's also
- 1:46why heavy rewriting kills it, but light
- 1:48paraphrasing usually won't. You have to
- 1:50change enough of the word choices so
- 1:52that the pattern falls apart. Now, we
- 1:54have to hold onto to because this
- 1:56matters for something later. There's one
- 1:58more thing that most people are getting
- 2:00wrong here. A detected mark does not
- 2:02prove that Claude wrote it, okay? This
- 2:05is Anthropic's own language in their own
- 2:08documents. If you wrote an entire
- 2:10article yourself by hand, you paste it
- 2:12in, and you ask Claude to clean up the
- 2:14grammar, the output will still likely
- 2:16carry that mark. It's the same if you
- 2:19ask it to translate or summarize. All it
- 2:22tells you then is that the text passed
- 2:23through Claude at some point, which is a
- 2:26much narrower claim than a lot of people
- 2:28are making. So, that's what the mark is.
- 2:31It's real, it's durable,
- 2:34and it's a lot dumber than most of the
- 2:35coverage suggests. But, the version
- 2:37circulating right now breaks in three
- 2:39separate places. I'm going to show you.
- 2:41First,
- 2:42Anthropic ships a detector, and it gets
- 2:45into Google's hands. So, okay, this one
- 2:48clearly plausible. Anthropic has said it
- 2:50intends to publish the details and allow
- 2:52third parties to check it. So, I'm
- 2:55obviously not going to stand here and
- 2:56tell you that detection is impossible.
- 2:58It is likely coming. This makes the
- 3:00second link the important one because
- 3:02the whole chain assumes that once Google
- 3:05can detect AI content, Google will do
- 3:08something about it. And honestly, that
- 3:10assumption has never been tested with
- 3:13text. Text watermarking is like 10 days
- 3:17old. Nobody has data on it. Nobody can
- 3:20have data on it. But, it has been tested
- 3:22somewhere else for 3 years in public,
- 3:25and almost one in this industry has
- 3:28really bothered to look. So, before I
- 3:30show that to you, I want you to look at
- 3:32what Google has actually said about
- 3:34AI-generated content because their
- 3:36documented position is not silence. They
- 3:39wrote it down. Their guidance says
- 3:41appropriate use of AI or automation is
- 3:44not against their guidelines, and that
- 3:47however content is produced, you should
- 3:49be aiming for original, high-quality,
- 3:52people-first work. This is Google's own
- 3:55blog post from 2023 and it's still up.
- 3:57Now, I'm not going to sit here and tell
- 4:00you that you should trust Google's
- 4:01public statements. Google has spent
- 4:03years telling this industry that clicks
- 4:06were too noisy to use in ranking. Then,
- 4:09their VP of Search testified under oath
- 4:11that Navboost is one of their important
- 4:13signals and later a former engineer
- 4:16testified that Google was told
- 4:18internally not to admit this publicly
- 4:20because SEOs would exploit it. This is
- 4:23the same story with the helpful content
- 4:25update. Google said it would reward
- 4:27people-first content. Then, Danny
- 4:29Sullivan sat in a room with publishers
- 4:32it had crushed and told them there was
- 4:34nothing wrong with their content.
- 4:35Google's systems just weren't surfacing
- 4:37it. Those people paid their own way to
- 4:40that meeting. Okay, so a Google blog
- 4:42post proves basically nothing on its
- 4:44own. What I want is behavior, years of
- 4:47it, with the detection already working.
- 4:49This brings me back to what's been
- 4:51running in public since 2023, images.
- 4:54Google has a watermarking system called
- 4:57SynthID. It's how Google marks the
- 4:59images, the video, and audio its models
- 5:02produce. And it's been live since 2023.
- 5:05It shows up inside Google Search, in
- 5:07Lens, in Circle to Search, where it'll
- 5:10tell you whether a picture was
- 5:12AI-generated. Now, every major lab does
- 5:15some version of this. It's been the
- 5:17industry standard for years. So, if
- 5:20Google were ever going to rank against
- 5:22AI content, images are where this would
- 5:25have happened first. The mark exists,
- 5:28the detection works, it's been sitting
- 5:30there for over 3 years. Now, let me show
- 5:33this to you. This is a page that my Core
- 5:3530 agent designed for local SEO built.
- 5:38And here's an image that was
- 5:40AI-generated, start to finish. It's a
- 5:42good image. Google Gemini generated it.
- 5:45You'd scroll right past this if you
- 5:46visited this website and never really
- 5:48think twice. I mean, maybe it looks a
- 5:50little weird that he's taking a wrench
- 5:51to this part of the water heater, but
- 5:54it's not a super weird image. Now, let
- 5:56me show you what this looks like on a
- 5:58free detector. This is just one random
- 6:00detector I found and it says 99% AI
- 6:04generated. This is off the pixels alone
- 6:06in like 2 seconds. There's no login,
- 6:08there's no key, there's no special
- 6:10access. Anybody can run this detection
- 6:12including Google and honestly Google can
- 6:15do it better because Google's own model
- 6:17made the image and Google's own
- 6:19watermarks are in its output. So, this
- 6:22is not a close call. Every layer of
- 6:25detection that exists catches it. Now,
- 6:27here's what happened to these pages. Let
- 6:29me show you some rank maps. This is from
- 6:31people running that very same Core 30
- 6:33agent before and after. AI written
- 6:35content, AI generated images published
- 6:38to their sites. Here's Here's this one,
- 6:40May 27th to June 16th. So, this is
- 6:43roughly 3 weeks of a before and after
- 6:46all based on content written by the Core
- 6:4830 agent. Here's another one. Uh this
- 6:51May 2nd to June 25th. So, this is almost
- 6:532 months. Uh I can show another page
- 6:56here.
- 6:57Uh we have This is July 16th to July
- 7:0025th. So, this is 9 days, right? Insane
- 7:03progress for 9 days. We can show another
- 7:05one here. This is the before, June 29th.
- 7:08Here's the after, July 24th. A little
- 7:11bit less than a month. Absolutely crazy
- 7:14results that people are getting with the
- 7:15Core 30 agent. And remember, this is
- 7:17with AI generated images, AI generated
- 7:19text, 3 years of working free public
- 7:22detection and it has never once been
- 7:24what decides whether a page ranks.
- 7:27That's the second link gone. Google
- 7:29having the capability and Google using
- 7:31it against you have never been the same
- 7:33thing and these are the receipts to
- 7:36prove it. Which leaves the third link.
- 7:38And this is the one that's going to cost
- 7:40you money if you get it wrong. Because
- 7:42somebody is going to tell you that you
- 7:45need to strip the watermark out anyway
- 7:47just to be safe. Now,
- 7:50these methods exist. There's published
- 7:52research on this. Documented academic
- 7:54papers. You can run text through a
- 7:56paraphraser. You can translate it into
- 7:57another language and back. You can do
- 7:59character level attacks that swap
- 8:01letters for look-alikes from other
- 8:03alphabets. And there's newer work on
- 8:05more targeted removal. Some of it
- 8:07actually needs access to the model's
- 8:09internals, which obviously you're never
- 8:11going to get through a hosted API, but
- 8:13most of it doesn't. Most of it you can
- 8:15just run this afternoon on content if
- 8:17you wanted to. But they all cost
- 8:19something. Remember how the watermark
- 8:22works, that the signal lives in the word
- 8:24choices themselves. That's why
- 8:26paraphrases and round trip translation
- 8:28defeat it. But keep in mind, you can't
- 8:30use Claude or OpenAI or Gemini to do the
- 8:33paraphrasing or to do the round trip
- 8:35translation. This has to be done by
- 8:37hand. OpenAI, Gemini are signing on to
- 8:41their own watermarks. This is part of a
- 8:43European Union law. So, we're not
- 8:46deleting a tag. We're not turning every
- 8:48word on the page. Doing this, especially
- 8:51by hand, the writing will flatten,
- 8:53errors will creep in that no one
- 8:54proofreads for, and you've ended up
- 8:56rewriting a page that was working. And
- 8:59the character swaps are the easiest but
- 9:01the worst of the bunch because of how
- 9:04this works under the hood. Remember that
- 9:06Google doesn't match keywords, it
- 9:07resolves entities. It reads the city
- 9:10Molden and connects it to everything we
- 9:12know about that city. It reads your
- 9:14business name and connects it to your
- 9:15Google Business Profile. But none of it
- 9:17happens visually. Of course, Google's
- 9:20algorithm doesn't have eyes. Text gets
- 9:22broken into tokens before anything looks
- 9:24at it. And if you've replaced the Latin
- 9:27symbol A with a Cyrillic character that
- 9:29looks identical, it's a still a
- 9:31completely different character
- 9:33underneath. So, a swapped word, it's not
- 9:35a misspelling that something can work
- 9:37out from context. It doesn't resolve to
- 9:40anything at all. Do that to a service
- 9:42name, a category, a city, the business
- 9:44name, and the page stops making the
- 9:46connection it was built to make. On top
- 9:48of that, mixed script text is trivially
- 9:51detectable, and Google has run this as a
- 9:53spam signal for years. You'd be breaking
- 9:56the entities on your page. You'd be
- 9:58handing Google something it flags on
- 10:00site. You'd be degrading real pages to
- 10:02hide from a consequence that doesn't
- 10:05exist. Okay, so look, things change. If
- 10:07there's ever evidence that Providence
- 10:08affects ranking, I'll talk about it, and
- 10:11I'll say so plainly. I have enough
- 10:12clients under management that are
- 10:14ranking with AI-written content and
- 10:16AI-generated images that we would see it
- 10:19immediately at my agency. But right now,
- 10:21the evidence runs the other way, and
- 10:23it's been running that way for 3 years.
- 10:26If you want to see the system that
- 10:27produced these rank maps, I put together
- 10:29a full walk-through of how the Court 38
- 10:31Agent works, what it writes, and what
- 10:33the pages look like. You can check out
- 10:35that video here.
About this transcript
This page contains the full transcript of Claude's Watermarks Just Broke SEO by Caleb Ulku, generated from the public captions YouTube serves with the video. The transcript has 1,878 words across 280 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.