If you run a forum, you already know the problem.

Someone writes a genuinely good answer. It sits there. Google never picks it up, or picks it up weeks later when the thread has gone quiet and the person has moved on. You watch a subreddit get indexed in an hour and wonder what they do differently.

The answer is in Google's documentation, and it has been since 8 October 2026.

There are two pipelines

Most of what is written about indexing assumes one queue. You publish, Google crawls, Google indexes, eventually. Everything in one line, first in first out.

Google's documentation describes something else:

"The UGC Fresh Data Program is a specialized pipeline designed exclusively for trending UGC content. It's independent of the Google Indexing API and traditional organic crawling for general web content."

Two pipelines. One is the organic crawling everything goes through. The other is a dedicated data feed where approved platforms push content and interaction signals directly, and Google processes it immediately instead of waiting to discover it.

That is not a leak. It is a public page, and it explains the gap between a thread that appears within the hour and a thread that appears in three weeks. Same internet, different lane.

What it is for, and who it is for

The programme exists because of a specific kind of content: discussions. A forum answer about a broken driver is worth reading today and worth nothing in a month. Organic crawling is too slow for content whose whole value is that it is current.

So Google built a fast lane for it, and hands it to platforms rather than sites.

"The platform must primarily host UGC, social postings, or forum discussions."

If that is not your site, this is not your programme. If it is, the rest of this is the checklist.

The six requirements

Each one is quoted from Google. Each one is a thing you either have or do not.

1. Content on dedicated, stable URLs

"The UGC content should be hosted on dedicated pages with stable URLs, not on profile or feed pages."

Every thread needs its own permanent address. Not a page that shows the twenty most recent posts. Not a user profile where the content changes every time they post again.

This is the requirement most forums get wrong, and usually for a reason that made sense at the time. Infinite scroll, a feed-style homepage, threads that live under /user/name rather than /thread/slug. Convenient for readers, and it leaves Google with nothing stable to index.

2. Every post attributable to a real profile

"all UGC must be attributable to a creator with a public profile."

Every piece of content needs an author, and that author needs a page that is public. Not a display name with no page behind it, and not anonymous posting.

This is the same requirement Google makes everywhere else. It appears in the helpful content guidance, in the Discover content policies, and in the Article structured data documentation. Five separate documents, one demand: say who wrote it, and give that person a page.

I met the same requirement on this site, and it took a separate change to satisfy it rather than a setting.

3. No login walls

"Content must be on public web pages accessible to Googlebot and users; gated content (requiring a login or paywall to view) is ineligible."

A members-only board, a logged-in-only thread, a "register to read the rest" prompt, and the content is out. Both of this programme, and often of indexing entirely.

For a forum this is the hard one, because member-only sections are usually the point of joining. The same rule is why robots.txt does not hide a page and neither does a login, in the sense that matters: either way Google cannot see it.

4. Volume, and a real user base

"A high volume of UGC content and a significant user base."

There is no number. Google does not give one, and I looked. A forum with forty posts and three members is not getting into a programme built for platforms with continuous discussion.

5. Machine-readable structured data

"the platform must already utilize (or be prepared to implement) valid on-page schema.org structured data markup across its URLs."

Specifically named: SocialMediaPosting or DiscussionForumPosting, with interactionStatistic sub-fields.

That means Google wants to be told, in a machine format, that this is a forum post, who wrote it, when, and how much interaction it has. Not inferred from the layout. Declared.

6. Active moderation, with a reporting mechanism

"The platform must not publish illegal content and must maintain active content moderation, including a user reporting mechanism."

A moderation policy, moderators who use it, and a way for users to report things. Google is asking for evidence that the platform is tended, not just hosted.

The two requirements that only apply to platforms

Worth separating these, because they are the ones that make it a platform programme rather than a content programme.

Freshness within minutes.

"Content submitted must be as fresh as possible, ideally sent within minutes."

Engagement, within 72 hours.

"you must be able to submit regular updates of engagement counters (within 72 hours of creation)"

Google wants the replies, the votes, the reaction count, and it wants them within three days. That is a statement about what makes content worth surfacing: not just that it exists, but that people are engaging with it while it is current.

The registration, and the honest part

Participation is limited, the technical bar is real, and the documentation says so plainly:

"Due to the technical requirements and the nature of the integration, participation is limited to platforms that meet specific content quality and volume guidelines."

It requires OAuth 2.0 authentication and strictly validated JSON-LD payloads. That is engineering work, not a settings page.

And the last line of the page, which is the one I would read twice:

"This program doesn't guarantee that content will appear in Search."

Google built a bespoke pipeline with OAuth, validated payloads and moderation requirements, and will not promise the content gets indexed. If the fastest, most direct route into Google's index comes with that sentence attached, then waiting three weeks for a thread to appear is not a fault in your forum. It is the system working as documented.

What to do with this if you are not eligible

Most forums will not qualify, and the six rules are still worth reading, because five of them are the same things Google asks of any site.

dedicated stable URLs          a thread is a page, not a timestamp in a feed
attribution to a profile       authorship, again, in the fifth document
no login walls                 gated content is invisible, everywhere
structured data                declare what it is, do not rely on layout
active moderation              a tended site, not merely a hosted one

None of that is about the fast lane. All of it is about being indexable at all.

The programme is a shortcut for platforms that already meet the rules. The rules are the part that applies to everyone.

Which is the same conclusion Google's own definition of content quality leads to, from a different direction. The fast lane is a shortcut. There is no shortcut to being worth indexing.

Sources

  • Google Search documentation, UGC Fresh Data Program
  • Google Search documentation changelog, 8 October 2026
  • Google Search documentation, Discussion forum structured data