Google tells platforms to noindex shared pages by default

Google has updated its help page on preventing user-generated spam to cover “tools that let users publish shared pages, generated content, or web apps.” A new section, “Only index content meant for Search,” tells platforms to apply noindex or block crawling by default for pages made for direct sharing, collaboration or utility. The change was logged on October 26, 2026, as reported by Search Engine Roundtable, Search Engine Journal and PPC Land.

What did Google change in its user-generated spam guidance?

Google widened the guide beyond comment forms and hosting services to any tool where users publish shared pages, generated content or web apps. According to PPC Land, the warning now also refers to spammers creating many “pages or sites,” not just sites.

The new section asks operators to consider whether content is meant for search or only for people with the link. Google’s changelog says the aim is to help platforms “keep user-created pages that aren’t meant for Search out of the index and detect spam earlier.” The monitoring list also gained Search Console verification, regular checks of the Page Indexing and Search performance reports, and platform-level alerts for spikes in new public pages or a few users producing many indexable URLs.

Should AI tools and shared pages be noindex by default?

For anything created for sharing rather than discovery, Google’s answer is yes: exclusion is the starting position. The guide does not say how a user could later opt a page into search, and it sets no thresholds for what counts as a suspicious spike.

Google named no products and did not mention AI. SEO consultants Lily Ray and Marie Haynes, per Search Engine Roundtable, wondered on X whether AI and app-building tools are the target and whether new manual actions are coming. That is speculation. Google has not said enforcement will follow, and the page is a set of recommendations, not a policy change.

Still, it signals what Google sees at scale: indexable, low-value pages hosted on trusted domains. Marketing teams that publish microsites, hosted forms, calculators or AI-generated reports on third-party platforms should expect those pages to stay out of Google if platforms adopt this default.

How to set up noindex for shared pages without robots.txt conflicts

Make sure Googlebot can read the noindex, because a robots.txt block stops it from ever seeing the rule. Search Engine Journal and PPC Land both point out that a URL blocked in robots.txt can still be indexed if other sites link to it, typically without a description. Share links are made to be pasted elsewhere, so that risk is real.

• Audit share, export and generated-output URLs: do they return a noindex via robots meta tag or X-Robots-Tag header?
• Check that those same paths are not disallowed in robots.txt. If they are, remove the block and rely on noindex.
• Look for “Indexed, though blocked by robots.txt” in the Page Indexing report, which Search Engine Journal flags as a likely place for share URLs to show up.
• If you run a platform, verify each site or subdomain in Search Console so manual action and security emails reach you.
• Build internal alerts for spikes in newly published public pages and for a small group of accounts generating most indexable URLs.
• Keep noindex on posts from new users until they build a reputation, which the guide already recommended.

If you only use these platforms, ask the vendor what their default indexing behavior is and whether you can publish a page publicly on purpose.

Sources

• Search Engine Roundtable: Google Updates User-Generated Spam Guidance To Specify Tools & More
• Search Engine Journal: Google Adds Indexing Advice For Shareable Pages To Spam Guide
• PPC Land: Google tells platforms to noindex link-shared pages by default