FOOTPRINTSEO Training Center
(239) 457-1867
New
  • Module 098
  • 2026-10-27
  • "REX (Matt Diamante / Get-Found school)"
  • "Content Policy / Technical SEO / UGC"

Module 98: The Link-Shared Noindex Rule — UGC, Shared Pages & Google's Updated Spam Line

What changed

On October 26, 2026, Google updated its spam guidance — and a four-report cluster documented it the same day: Search Engine Roundtable ("Google Warns Tools On User-Generated Spam Guidance & More"), Search Engine Journal ("Google Updates Spam Guide For Shared Pages, Generated Content & Apps"), Search Engine Land ("Google Search says you should block indexing of link-shared content"), and PPC Land ("Google tells platforms to noindex link-shared pages by default"). Google also updated its "how to block Google Search" documentation at the same time.

The substance of the update (all four reports + Google's own spam policies documentation):

  • Link-shared content should default to noindex. Pages that exist mainly to host content someone else shared — collab pages, share-to-view pages, tool-output pages — should not be indexed by default.
  • User-generated pages are a platform responsibility. Forum threads, review feeds, comment archives, and community posts that platforms index freely are now called out in Google's spam guidance: if the page is mostly user-generated and unmoderated, the guidance says platforms should keep it out of the index until it earns its place.
  • Generated content is explicitly covered. The updated spam guide addresses auto-generated and mass-produced content alongside shared pages and apps — the trio Google now treats as one quality risk.
  • It's guidance with teeth, not a suggestion. Google warned tools and platforms directly. Indexing thin user-generated or link-shared pages at scale is now positioned as a policy-level quality risk — the kind of surface that gets sitewide quality signals dragged down, not just the individual page.
REX framing: Google finally said the quiet part out loud — "if the users wrote it and you didn't stand behind it, keep it out of the index."

Why it works

This isn't Google being mean to user-generated content. It's Google telling you where its quality systems now look.

  • Thin UGC pages are spam magnets. Open indexation of unmoderated user content attracts parasite spam, link drops, and AI-slop pages. Every indexed spam page on your domain is a page Google can hold against your site's quality score.
  • Link-shared pages are duplicated content surfaces. A page whose only job is hosting shared material adds no unique value — it duplicates the source and dilutes crawl budget.
  • Index bloat distorts your real performance. When 60% of your indexed pages are thin UGC or generated pages, Google's perception of your site is built on your worst content, not your best. Pruning what doesn't earn its index slot is the same doctrine as Module 94 (content pruning) — this is its UGC-specific extension.
  • Crawl budget goes to what matters. Blocking thin shared pages frees crawlers to find, render, and refresh the pages that actually rank and convert — the Module 96 fix-order principle applied to UGC.
  • It protects you from the next update. Every core update, sites with large thin-U footprints get hit hardest. A proactive noindex rule is insurance against the volatility cycle we've watched run Oct 24–27.

How to run it

Local service businesses (AC repair, roofing, security)

  • Inventory your indexable UGC-ish pages. Run site: searches in Google for your domain plus these patterns: review pages, testimonial pages, comment sections, city/service generated pages, event pages, quote-shared pages. Log everything that comes back.
  • Grade each page type. Three buckets: (a) editorial-backed — UGC plus real written content, reviews with owner responses, FAQ pages you maintain; (b) thin feed — raw review widgets, bare comment threads, auto-generated city pages with boilerplate; (c) shared/collab — pages that exist to host shared docs, shared checklists, or partner material.
  • Apply the rule. Bucket (a) stays indexed. Bucket (b): add editorial substance (owner responses, local specifics, unique photos) or noindex. Bucket (c): noindex by default — full stop.
  • Implement the noindex. Add <meta name="robots" content="noindex,follow"> to the page template — or the HTTP header equivalent. Do not also block in robots.txt: blocking crawling means Google never sees the noindex and can still show the URL in results.
  • Keep reviews on GBP-first. Your Google Business Profile is the right indexed surface for review content — your website's raw review-feed pages usually aren't.
  • Re-check in Search Console. After two weeks, use the Pages report to confirm the noindexed pages drop out of "Indexed" and the editorial pages keep their impressions.

Insurance / YMYL sites (Medicare, ACA, MASA)

  • Audit agent and sub-brand pages first. Shared agent subpages, co-branded resource pages, and state-collab pages are the classic link-shared surfaces on brokerage sites. Each one must carry unique, reviewable, compliance-safe content — or get noindexed.
  • Handle comment and Q&A sections conservatively. On YMYL pages, unmoderated user comments are both a spam risk and a compliance risk (unlicensed advice in the wild). Either moderate daily, or noindex the comment archive pages while keeping the main article indexed.
  • Check tool-generated pages. Quote calculators, plan-comparison printouts, and shared results pages should not be indexable — noindex the templates.
  • Document the decisions. Keep a short register: page type, decision (index / noindex), date, reason. This is your audit trail if quality questions come up later — and the paper trail a compliance reviewer will want.
  • Never noindex the money pages. The rule is about UGC, shared, and generated surfaces — not your Medicare guide pages, ACA explainers, or contact pages.

Real example

acrepairdaily.com — a local AC-repair site with seasonal maintenance guides and a "cities we serve" section.

The site had 40 auto-generated city pages — each one the same 200 words of boilerplate with the city name swapped — plus a testimonials page that was a raw JavaScript review widget rendering hundreds of uncategorized quotes. Google had indexed all of it.

Applying the rule:

  • The city pages for markets with real content (photos, local pricing notes, named techs) were upgraded with editorial substance and kept indexed.
  • The 25 remaining boilerplate city pages got noindex,follow.
  • The raw testimonial widget page got noindexed; the curated "What homeowners say" page with 10 named, dated reviews and owner responses stayed indexed.
  • Two shared "maintenance checklist" collab pages built for partner vendors got noindexed — the partners link to the main guide instead.

Result pattern within a crawl cycle: total indexed pages dropped ~40%, impressions on the remaining pages rose as crawl budget concentrated, and the site's worst-quality surface stopped feeding the index. That's the fix-order doctrine from Module 96 — crawlability before cosmetics — applied to the UGC layer.

Checklist

  • [ ] Run site: searches for review, testimonial, comment, city, event, and shared pages on the domain
  • [ ] Sort every UGC-ish page type into: editorial-backed / thin feed / shared-collab
  • [ ] Upgrade thin pages with real editorial substance where the page earns it
  • [ ] Noindex thin feed and shared-collab pages with robots meta noindex,follow
  • [ ] Confirm robots.txt does NOT block crawling of pages carrying noindex
  • [ ] Noindex tool-generated templates (quote printouts, calculators, shared results)
  • [ ] On YMYL: moderate or noindex comment archives; never noindex money pages
  • [ ] Keep a decision register (page, decision, date, reason) for the audit trail
  • [ ] Re-check Search Console Pages report after two weeks

Quiz

Q1: A platform hosts hundreds of forum threads. What does Google's updated guidance say should be the default indexation state for those pages?

A) Index everything to maximize long-tail traffic
B) Noindex by default — unmoderated user-generated pages should stay out of the index until they earn their place
C) Block crawling in robots.txt instead

Answer: B. The updated guidance tells platforms to noindex link-shared and user-generated pages by default. (And note why C is wrong: robots.txt blocking prevents Google from seeing the noindex meta — it hides the crawl but not the indexation.)

Q2: You want to noindex your raw review-widget page. What's the correct implementation pairing?

A) Add the noindex meta tag AND block the URL in robots.txt
B) Add the noindex meta tag (or HTTP header) and leave the URL crawlable
C) Redirect the page to the homepage

Answer: B. Google must be able to crawl the page to read the noindex directive. Pairing noindex with a robots.txt block is the classic mistake — Google sees the URL but never the instruction.

Q3: Which page type should stay indexed under the new guidance?

A) An auto-generated city page with 200 words of boilerplate and a swapped city name
B) A raw JavaScript review feed with hundreds of uncategorized quotes
C) A curated testimonials page with named, dated reviews and owner responses
D) A shared vendor-collab page hosting partner documents

Answer: C. Editorial-backed pages — real curation, owner responses, unique substance — are exactly what earns an index slot. A and B are thin/generated surfaces; D is link-shared content.

Try this today

Pick the managed site with the biggest listing/review surface (this week's queue: acrepairdaily.com's city pages and testimonial widget). Run the site: inventory, grade the page types, and put noindex,follow on the first thin-feed template today. One template change usually reclassifies dozens of pages at once — that's the cheapest quality cleanup in SEO.

Sources