Home/Insights/Google opened a fast lane for forum posts. Who qualifies for the UGC Fresh Data Program, and what should everyone else use?

Google opened a fast lane for forum posts. Who qualifies for the UGC Fresh Data Program, and what should everyone else use?

Google's UGC Fresh Data Program speeds intake for big UGC platforms, not rankings. How it compares with crawling, sitemaps and the Indexing API.

BY Esh, FOUNDER, ETHOS ENGINEPUBLISHED OCTOBER 16, 20267 MIN READ
KEY TAKEAWAYS
  1. The UGC Fresh Data Program is an intake lane for large UGC platforms. Google promises speed of processing, not visibility.
  2. Google now has four documented ways in. Each one fits a different kind of site, and none of them guarantees indexing.
  3. Ahrefs found the top 10 domains hold 84.87% of Discussions and forums links. Faster intake does not change who wins those slots.
  4. Sites that do not qualify should fix accurate lastmod dates, feeds, forum markup and moderation, then measure time to first impression.

On 8 October 2026 Google published a page for something it calls the UGC Fresh Data Program. Approved platforms can now send new posts and engagement counts to Google through their own pipeline, instead of waiting for Googlebot. Eight days later, on 16 October, Google rewrote the quota page for its other push route, the Indexing API. Both changes raise the same question for anyone who runs a forum, a community or a content site. Which way into Google fits you, and what does each one actually promise?

What did Google open on 8 October?

An intake lane, by application. Google describes a dedicated pipeline for trending user-generated content that runs apart from the Indexing API and from ordinary crawling. A platform that is accepted pushes content and interaction signals. Google says the aim is to get fresh first-hand content processed and updated quickly in Search.

Three limits sit on the same page. The lane covers trending UGC only. Content must still live on public pages that Googlebot and users can reach. And Google says plainly that taking part does not guarantee that anything will appear in Search. Technical documentation is shared only after acceptance, and Google expects to reply to applications within six to eight weeks.

Who qualifies, and what is still unknown?

Google lists six criteria. Read together, they describe a large, well-run social or forum platform.

  1. Content focus. The site mainly hosts UGC, social posts or forum threads, on dedicated pages with stable URLs. Profile and feed pages do not count.
  2. Scale. High UGC volume and a significant user base. No number is given.
  3. Access. Public pages only. Gated content is out, and every post must link to a creator with a public profile.
  4. Engineering. OAuth 2.0 authentication and strictly validated JSON-LD, using SocialMediaPosting or DiscussionForumPosting with interactionStatistic.
  5. Moderation. No illegal content, active moderation and a way for users to report posts.
  6. Speed. Posts sent ideally within minutes of creation, and engagement counter updates within 72 hours.

Search Engine Journal looked at the form behind the page. It counts seven required fields, including monthly active users, 10 sample URLs and a Search Console owner's email. The form treats a submission as an expression of interest only. As of 15 October, SEJ found no named participant.

What Google has not said matters as much. There is no volume threshold, no word on how interaction signals are used, and no mention of AI Overviews or AI Mode. One small tension is worth knowing about. Google's forum markup page recommends Microdata or RDFa to avoid duplicating long text, while the program asks for validated JSON-LD. Both formats are supported, but an applicant must be able to produce the JSON-LD version.

Is it a ranking advantage?

The coverage splits here. Barry Schwartz at Search Engine Roundtable read the program as an API that sites like Reddit can use to push content in faster. DesignRush went further. It argued that a complaint trending on an approved platform could reach Google within minutes while a brand's reply on its own site waits for a crawl.

Google's own text supports a narrower reading. It promises processing speed, limits the scope to trending UGC, and disclaims any guarantee of appearance. No participant and no measured effect have been published. So the defensible claim is about intake speed. Nothing public shows a ranking gain, and the reputation scenario is plausible but untested.

There is a precedent. In February 2024 Google announced access to Reddit's Data API, which it said provides structured, current content. That deal also covered training. The new program reads like the same pipe offered by application to any platform that qualifies, and its page does not mention training.

Four routes into Google, compared

Google now documents four ways for content to reach it. They are not ranked options. Each one fits a different kind of site.

RouteWho can use itWhat you sendWhat Google says about speedWhat it promises
Crawling with sitemaps and feedsAny siteSitemap with accurate lastmod, RSS or Atom via WebSubA sitemap is a hintNothing; discovery only
URL Inspection recrawl requestOwners and full users of a Search Console propertyA few URLs, under a quota"a few days to a few weeks" for crawlingNo guarantee of inclusion
Indexing APIPages with JobPosting, or BroadcastEvent in a VideoObjectURL_UPDATED and URL_DELETED notices, 200 a day by defaultNot statedSpam checks on every submission
UGC Fresh Data ProgramApproved large UGC platformsPosts plus interaction signals, within minutesNot statedNo guarantee of appearance

The Indexing API row changed today. The English quota page, updated on 16 October, lists the defaults: 200 publish requests a day per project, 180 metadata reads a minute, 380 requests a minute across all endpoints. It no longer links a form to ask for more, and it no longer says quota can rise or fall with document quality. The Japanese version, last updated on 17 July, still carries both lines. Google's changelog says only that an outdated form was removed.

This follows a run of complaints. In September SEJ reported job site operators whose approval requests had gone unanswered for months. Alexander Chukovski said he had seen at least 50 applications since October 2025 with none approved, while noting he had no inside knowledge. Google has not explained how extra quota is granted now.

How fast is ordinary crawling?

The sources disagree, but less than it first looks. Google's recrawl page says crawling can take a few days to a few weeks. At Search Central Live in Barcelona on 2 October, Gary Illyes reportedly put typical discovery of a new URL at about 20 hours, with the slowest cases taking weeks or never.

These are different measures. One is a range for a requested recrawl. The other is a typical value for discovery, reported second-hand from an attendee's recap with no method or sample. Both agree on the shape: most pages arrive quickly, and a slow tail may never arrive. The same applies to claims that Indexing API pings are crawled within minutes. Cavuno, which makes that claim, notes that no controlled comparison has been published. We found none either.

Speed does not change who wins the forum slots

Ahrefs published a study of 145 million US Google results in August 2026. The Discussions and forums feature appeared on 11.7% of them. Reddit appeared in 87.8% of US results with the feature, and 83.9% worldwide. Worldwide, Reddit, Facebook and Quora together held 76.75% of the feature's links, and the top 10 domains held 84.87%. The top 1,000 domains averaged 21 years and 8 months old. Backlinks pointing at individual threads showed no correlation with ranking.

That is the market a new pipeline enters. It may help a large platform's new thread appear sooner on a fresh query. It does not change which domains Google trusts for first-hand discussion, and quality still decides the slow tail. Reddit's own machine-translated pages fell in Google after the May 2026 core update and June 2026 spam update, as Glenn Gabe documented. If you are reading a recent drop, our guide to the September 2026 spam update covers the signatures.

What should a site that does not qualify do?

Make ordinary crawling fast and honest. Here is a hypothetical case to show the reasoning.

Hypothetical: a software company runs a public product community. It gets about 900 new threads a month, roughly 30 a day, from 15,000 monthly active members. Posts and profiles are public. Google publishes no threshold, but this is unlikely to count as high volume next to the domains Ahrefs lists. The Indexing API is closed to it, because forum pages carry no JobPosting markup. Its routes are a sitemap with accurate lastmod dates, a feed sent through WebSub, and forum markup on each thread.

Google's sitemap page says lastmod is used only when it is consistently and verifiably accurate, so the date should change when a thread gains a reply, not on every page load. Our piece on what counts as an update applies the same rule to articles. The forum markup page lists the fields that matter: author, datePublished, the post text, interactionStatistic, and digitalSourceType for bot or model replies. Moderation does double duty. Google's 2021 advice on UGC spam, as SEJ reported it, includes holding new members' posts for review and noindexing untrusted areas such as profiles. Its spam policies name spammy forum posts as user-generated spam, so thin profiles and unmoderated threads cost more than slow intake does.

A seven-step method

  1. Classify the site. Mostly UGC, mostly jobs or livestreams, or neither. That alone rules routes in or out.
  2. Measure intake now. Record the gap between post time and first Search Console impression for 20 recent pages.
  3. Fix lastmod. Tie it to real changes such as new replies or edits, never to the build time.
  4. Add a feed. Publish RSS or Atom for new threads and notify through WebSub.
  5. Mark up threads. Use DiscussionForumPosting or SocialMediaPosting, with interactionStatistic and digitalSourceType where bots post.
  6. Clean the public surface. Hold new members' first posts, noindex thin profiles, and remove spam before adding speed.
  7. Apply only if you fit. A large platform that meets all six criteria can submit the form, then compare intake times against step 2 once onboarded.

The same discipline helps outside Google too. Forum threads feed AI answers, and we looked at how one engine's Reddit citations fell this summer. If you want to know how your community pages show up across search and AI, join the waitlist.

Questions

What is Google's UGC Fresh Data Program?

It is an application-based pipeline that lets approved platforms send user-generated posts and interaction signals straight to Google. Google says it is separate from the Indexing API and from normal crawling, covers trending UGC only, and does not guarantee that any content will appear in Search.

Can a small forum or a brand community apply?

Anyone can submit the form, but Google asks for high UGC volume and a significant user base without giving numbers, plus OAuth 2.0, strictly validated JSON-LD and active moderation. A mid-sized community is unlikely to be the target. It can still use markup, sitemaps and feeds.

Does joining the program improve rankings?

Google makes no such claim. Its page promises faster processing, not placement, and no participant or measured effect has been published. Rankings in the Discussions and forums feature are concentrated in a few old domains, and speed alone does not change that.

Can I use the Indexing API for forum or blog pages instead?

No. Google limits the Indexing API to pages with JobPosting, or BroadcastEvent embedded in a VideoObject. Its quota page, updated on 16 October 2026, lists a default of 200 publish requests a day and no longer links a form for more.

Sources

  1. Google Search Central, About the UGC Fresh Data Program developers.google.com
  2. Google Search Central, Latest Google Search documentation updates developers.google.com
  3. Google Search Central, Indexing API quota and pricing information developers.google.com
  4. Google Search Central, Indexing API quota page, Japanese version last updated 17 July 2026 developers.google.com
  5. Google Search Central, Indexing API overview developers.google.com
  6. Google Search Central, Ask Google to recrawl your URLs developers.google.com
  7. Google Search Central, Build and submit a sitemap developers.google.com
  8. Google Search Central, Discussion forum (DiscussionForumPosting) structured data developers.google.com
  9. Google Search Central, Spam policies for Google web search developers.google.com
  10. Google, An expanded partnership with Reddit blog.google
  11. Ahrefs, Analysis: Reddit Appears in 83.9% of Google's Discussions and Forums Results ahrefs.com
  12. Search Engine Journal, Google Takes Applications For A UGC Pipeline Separate From Crawling searchenginejournal.com
  13. Search Engine Journal, Google Indexing API approval and job sites searchenginejournal.com
  14. Search Engine Roundtable, Google Reveals The UGC Fresh Data Program seroundtable.com
  15. Search Engine Land, Google Search disclosed its UGC Fresh Data Program searchengineland.com
  16. PPC Land, Google says new pages take about 20 hours to be found, some never are ppc.land
  17. DesignRush, Google Ends Spam Update, Opens UGC news.designrush.com
  18. Cavuno, Google Indexing API for job postings cavuno.com
  19. Search Engine Journal, Google's advice on preventing UGC spam and manual actions searchenginejournal.com
  20. GSQi, Reddit's AI Translations Finally Drop Heavily In Google And AI Search gsqi.com
E
Esh

Founder, Ethos Engine. Builds the Digital Authority Score and runs the placement marketplace. esh@ethosengine.io

NEXT STEP

See where your brand stands.

Your Digital Authority Score, who AI recommends for your target questions, and the placements that close each gap. Your first report is free.

Get your free report →
MOREINSIGHTS