Google Just Told Platforms How to Hide Their Share Links From Search

2026-10-27 — stakeholder management consulting

Google updated its spam guidance on October 26th. The change is modest in appearance but lands a genuine problem in your lap if you run a platform where users generate content meant for sharing, not searching.

The new section is called "Only index content meant for Search." It tells platforms hosting shared pages, generated outputs, or interactive tools—things like ChatGPT share links, Claude conversations, no-code apps—to use noindex tags or robots.txt blocks by default to keep that content out of Google's index.

Reasonable enough on the face of it.

Except robots.txt doesn't actually work the way most people think it does. That's where this gets messy. A page disallowed in robots.txt can still be indexed if linked to from other sites. Google won't crawl it, but the URL itself can appear in search results. No description, mind you—just the URL and maybe the anchor text from whatever external page links to it. But it's there.

This creates an uncomfortable situation. You tell Googlebot to go away from your share pages via robots.txt. But if someone else links to those pages externally—which happens constantly with shareable content—Google can still index the URLs themselves.

The guidance wants you to use noindex instead, actually. Or both—noindex via a meta tag or HTTP header, alongside robots.txt for belt-and-suspenders protection. Here's the thing though: noindex only works if Googlebot actually sees it. The noindex rule only works when robots.txt isn't blocking the page, because otherwise the crawler will never see the noindex rule. So you need the right combination.

That's not the whole picture.

Google also expanded what the guidance covers. It used to focus mainly on hosting platforms and comment sections. Now it explicitly includes "tools that let users publish shared pages, generated content, or web apps." DuckDuckGo's share links for its AI assistant, Google's own Opal no-code builder, the Playground game creator Google launched last month—these all fall into the new category. Actually, that raises something interesting: some of Google's own products now live in the exact space it's telling platforms to police.

The update also adds monitoring requirements. Platforms should verify their domain in Search Console, watch for unexpected spikes in indexed pages or impressions, and set alerts for things like new users generating large numbers of indexable URLs all at once. It's asking platforms to catch abuse earlier, not just respond after the fact.

There's a practical tension here that the guidance doesn't quite resolve. If you block user content with robots.txt to prevent crawling, but external linking inevitably brings those URLs into Google's index anyway, you're relying on noindex to actually work—which requires Googlebot to reach those pages despite the robots.txt block. Most platforms probably aren't handling this combination correctly right now.

The question for anyone running a platform where users generate shareable content: are you blocking indexing at all today, and if so, how?

Source: "To help platforms keep user-created pages that aren't meant for Search out of the index and detect spam earlier." — Google Search Documentation Updates