Google Adds Indexing Advice for Link-Sharing Pages to Its Spam Guidelines

Google has updated its spam guidelines with advice on indexing pages used for link sharing, collaboration, and online tools. If a page should not be found through search, Google recommends noindex.

· 4 min read · 4 comments

On October 26, Google updated its spam guidelines with a section on pages used for link sharing, collaboration, and tools. As Search Engine Journal reports, if those pages are intended only for people who have the link, Google advises using noindex by default or blocking crawling through robots.txt. Blocking crawling alone, however, does not guarantee that a URL will stay out of search results.

Which pages does the update cover?

The main question is whether a page should be discoverable through a search engine or serve only as a direct-access page. Google suggests asking this about pages users share, generated results, and interactive tools. If public search is not part of a page’s purpose, the guidelines advise using noindex in a robots meta tag or an X-Robots-Tag HTTP header. The other suggested option is to block crawling by default in robots.txt.

The description of spam risks now specifically mentions tools that let users publish shared pages, generated content, and web apps. Where the guidelines previously referred to creating websites at scale, they now also mention individual pages. That is an important distinction for a platform: many URLs can be created within a single service without launching new websites.

The earlier advice remains: posts by new users can be kept out of the index with noindex until those users build a reputation on the platform. That advice was already present in the December 10, 2025 version. The new section suggests considering not just whether the author is trusted, but also the purpose of the published material.

Why robots.txt is no substitute for noindex

The measures Google suggests serve different purposes. Robots.txt restricts crawling, but a blocked page’s URL can still appear in results if other sites link to it. Google will not be able to read the page’s content; the results may show the URL and possibly anchor text instead of a description.

For noindex to work, Googlebot needs to be able to access it. If the page is also blocked in robots.txt, Googlebot will see neither the meta tag nor the rule in the HTTP header. Using both restrictions together therefore does not provide double protection against a URL appearing in search results.

The article gives the example of Claude’s link-sharing pages: on July 27, the author found a Disallow rule for the path to those pages and a value of none in the X-Robots-Tag. According to Google’s documentation, none is equivalent to noindex and nofollow. But the author could not establish what Google saw when it first discovered the links. The example does not change the central limitation: if you block crawling, you cannot count on the crawler reading noindex.

What site owners should check

Start by grouping URLs according to their purpose. A product page that people search for by bicycle model and a page containing a result shared with a specific person do not necessarily need the same settings. The test is not whether someone can copy the link, but whether the page needs to be found through search.

If a URL should not appear in search results, check that it has noindex and that Googlebot can access the rule. For URLs indexed despite a robots.txt block, Search Console has an “Indexed, though blocked by robots.txt” status. Google’s help documentation recommends removing the block and using noindex in that case.

The updated guidelines advise verifying your site or subdomain in Search Console to receive notifications about manual actions and security issues. They also suggest regularly checking indexing and search performance reports for unexpected increases in indexed pages, impressions, or queries unrelated to the platform’s purpose. Separately, Google recommends watching for spikes in the publication of publicly accessible pages and checking whether a small group of users is creating a significant share of indexable URLs.

My view: draw the line before publishing

I would not keep everything that can be shared by link out of search. Buyers still search for specific parts by bicycle model, so the relevant pages need to be discoverable. A URL created solely to share a result or use a tool, on the other hand, may have no need to appear in search results. The catch is trying to handle both cases with a single robots.txt directive: Google’s explanation makes clear why that block cannot guarantee that a URL stays out of the index.

When updating a site or migrating a catalogue, I would agree on a list of page types in advance: which should remain discoverable through search, where noindex is needed, and how to check the outcome in Search Console. I want a price with a clearly defined scope of work, not a promise to “hide the unnecessary pages” without a list of URLs. Otherwise, you could lose useful landing pages while leaving links intended only for sharing in search results.

Sources

Where the news comes from. The text is a retelling in the author’s own words; the facts come from the source, the opinion is the author’s.

  1. Google Adds Indexing Advice For Shareable Pages To Spam Guide via @sejournal, @MattGSouthern www.searchenginejournal.com

About the author

Daan van der Meer

Bicycle accessories shop owner

I sell bicycle accessories online and manage the catalog myself. I’m currently figuring out how to update the site without losing niche landing pages and order history.

All posts by the author

Leave a comment

Not published. We’ll send a link to confirm your comment.

No links or ads. Your first comment is published after review. By sending a comment you agree to the privacy notice.

  1. In my shop, we have shared pages for things like order updates and product comparisons that are useful to customers who have the link, but should not be entry points from Google. We treat that as a publishing decision: if a page has no value to someone arriving from search, we add a noindex directive before launch and check that it is not blocked by robots.txt, since Google needs to crawl the page to see the directive. That small check is much cheaper than untangling unexpected URLs later.

    1. The robots.txt check is easy to miss—Google has to crawl the page to see noindex, so checking both before launch makes sense.

    2. @bas.vanloon That pre-launch check is the kind of tiny ritual that saves a team from later discovering its “private by link” order page has become Google’s newest front door. And yes, robots.txt can keep Google from reading noindex—an impressively efficient way to hide the sign that says “don’t list this.”

      1. @beatriz_ines The distinction I would add is between discoverability and access control: noindex can keep a URL out of search, but it does not make an order-update page private. If the link itself grants access to sensitive details, the page still needs appropriate authorization and expiry controls; indexing directives only address the search result.