On this page · 10 sections
- What Google launched on 8 October 2026
- Who qualifies: the six eligibility tests
- How it differs from the Indexing API and normal crawling
- The markup Google expects on your pages
- The engineering behind a pipeline
- How to apply, step by step
- Should you apply? A quick decision guide
- India-specific considerations
- How eCorpIT can help
- References
Summary. On 8 October 2026 Google Search Central published a page for the UGC Fresh Data Program, filed under its Early Adopters Program, and as of 16 November 2026 the page has not changed since that date. Approved platforms get a dedicated ingestion pipeline to send fresh user-generated posts and their interaction signals to Google, separate from both the Indexing API and normal crawling. Eligibility rests on six tests: the site must mainly host UGC on stable public URLs tied to public creator profiles, carry high volume and a significant user base, handle OAuth 2.0 and strictly validated JSON-LD, mark pages up with SocialMediaPosting or DiscussionForumPosting including interactionStatistic, moderate actively with user reporting, and send posts within minutes with engagement counter updates within 72 hours. Google promises a reply within 6 to 8 weeks and does not promise Search visibility. By contrast, the Indexing API stays limited to JobPosting and livestream pages, with a default of 200 publish requests a day that is meant for setup and testing, and no charge. Our verdict: only large forums, community apps and social platforms should apply, and only after their on-page markup already passes Google's forum guidelines.
About this article. This is for product owners, engineering leads and SEO teams at forums, community platforms, review and Q&A sites and social apps in the US, UK, EU and India. We checked every requirement, date and limit on 16 November 2026 against Google Search Central's programme page and documentation change log, Google's structured data, Indexing API and OAuth 2.0 documentation, and the schema.org type definitions. Google shares the technical integration documents only with accepted platforms, so we describe the public requirements and do not guess at the private API. This is general technical guidance, not legal advice, and no vendor paid for inclusion. Researched with AI assistance and checked against the primary sources listed in the references.
What Google launched on 8 October 2026
Google's documentation change log lists the new page under 8 October 2026 and says its purpose is to explain the programme and help prospective applicants judge their eligibility. In the Search Central navigation the page sits in the Early Adopters Program group, next to package tracking, the only other programme listed there. Search Engine Roundtable reported the page the same day and described it as a way for large UGC sites to push content to Search faster.
The programme page itself makes four points:
- Its purpose is to help platforms show fresh, high-quality, authentic UGC across Search features.
- Approved platforms send content and interaction signals through a dedicated ingestion pipeline.
- The pipeline is built only for trending UGC and is independent of the Indexing API and of ordinary crawling of web content.
- Taking part does not guarantee that any content appears in Search.
Two dates are useful for planning. A platform that applied on launch day, 8 October, should hear back between 19 November and 3 December 2026 if Google keeps to its 6 to 8 week window (8 October plus 42 and 56 days). A platform that applies today, 16 November, should expect an answer between 28 December 2026 and 11 January 2027, so the holiday period sits inside the wait.
Why the Early Adopters label matters
Early Adopters programmes at Google are selective and can close. The package tracking page in the same group now says the programme is no longer taking new partners, a change the log dates to 14 July 2026. The same log shows earlier early adopter programmes for mini-apps and, in February 2021, for 3D and AR results being removed once Google stopped accepting submissions. Treat the UGC Fresh Data Program as an open window, not a permanent product, and apply while it is open if you qualify.
Who qualifies: the six eligibility tests
Google says participation is limited because of the technical demands and the nature of the integration, and lists six criteria a platform must meet. We have restated them as tests you can run against your own platform. The programme page is the source for every row below.
| Test | What Google requires | How to check your platform |
|---|---|---|
| Content focus | Mainly UGC, social posts or forum threads, each on its own page with a stable URL, not on profile or feed pages | Count what share of indexable pages are single posts or threads with permanent URLs |
| Volume and audience | A high volume of UGC and a significant user base | Google gives no numeric threshold, so prepare daily post counts and active user figures |
| Accessibility | Public pages that Googlebot and users can reach, no login wall or paywall, and every post tied to a creator with a public profile | Fetch post and profile URLs while logged out and confirm both return the full content |
| Technical readiness | Secure OAuth 2.0 API authentication, strictly validated JSON-LD payloads and valid on-page schema.org markup such as SocialMediaPosting or DiscussionForumPosting with interactionStatistic | Run your templates through the Rich Results Test and a JSON schema validator in CI |
| Health and moderation | No illegal content, active moderation and a way for users to report content | Document your moderation queue, reporting button and response times |
| Freshness | Posts sent as fresh as possible, ideally within minutes, and engagement counter updates within 72 hours of creation | Measure the delay from post creation to an outbound event in your pipeline |
What counts as UGC
Google defines UGC for this programme as digital material hosted and distributed by a platform or aggregator but created entirely by independent users, not by the platform. Google's forum markup guidance draws the same line: it tells sites not to use DiscussionForumPosting for content written mainly by the publisher or its agents. A brand blog with a comment section does not qualify. A support community where customers start most threads might.
No numbers on volume
The volume test is the vaguest. Google asks for a high volume of UGC and a significant user base and publishes no figure for either. We found no official threshold, and we do not repeat the unofficial ones circulating in trade blogs. Put real numbers in your application: posts a day, unique creators a month, monthly active users and the share of traffic arriving from Search.
Gated content is out
Login-only or paywalled UGC is ineligible. That rules out private groups, member-only forums and apps that show a post only after sign-in. If part of your platform is public and part is gated, only the public part is a candidate. Do not try to mark private posts as accessible: Google's general structured data guidelines forbid marking up content that readers cannot see on the page. Publishers with real paywalls have separate paywalled content markup, but that markup does not make gated UGC eligible for this programme.
How it differs from the Indexing API and normal crawling
Many teams will ask whether they can use the Indexing API instead. For UGC, the answer is no. The Indexing API only accepts pages carrying JobPosting or a BroadcastEvent inside a VideoObject, and every submission goes through spam checks, with access revoked for abuse such as using several accounts to raise quota. Its default quota is 200 publish requests a day per project, 180 metadata reads a minute and 380 requests a minute across all endpoints, and it costs nothing to use. Google has said since September 2024 that this default quota is for initial setup and testing, with further use needing approval, and it updated the quota page on 16 October 2026 to remove an old request form.
| Channel | Who can use it | What it carries |
|---|---|---|
| Organic crawling | Any public site | Whatever Googlebot finds and chooses to crawl, on Google's schedule |
| Sitemaps | Any site owner | Lists of URLs and last modified dates as hints for crawling |
| Indexing API | Verified owners of job posting or livestream pages | URL updated and URL deleted notifications, 200 publish requests a day by default |
| UGC Fresh Data Program | Approved UGC platforms only, after application | Fresh posts plus interaction signals through a dedicated pipeline, with JSON-LD payloads over OAuth 2.0 |
The sources for this comparison are Google's programme page and the Indexing API quickstart and quota pages. The key difference is what is sent. The Indexing API only tells Google that a URL changed and leaves the fetch to Google. The programme, by Google's description, carries the content and its interaction signals directly, which is why Google asks for strictly validated payloads and tight timing.
The markup Google expects on your pages
Google says the platform must already use, or be ready to add, valid schema.org markup across its URLs, and names SocialMediaPosting and DiscussionForumPosting with interactionStatistic as examples. Both types already have Google documentation, so you can get this layer right before you apply.
Choosing the type
On schema.org, SocialMediaPosting is a subtype of Article, and DiscussionForumPosting is a subtype of SocialMediaPosting. Google's forum guidance applies the same requirements to both; most forums will find DiscussionForumPosting the better fit, while sites that behave more like a general social network can use SocialMediaPosting. If your community follows a question and answer pattern, Google points you to Q&A markup instead.
Required and recommended properties
For a post, Google requires author with author.name, datePublished in ISO 8601, and at least one of text, image or video. Recommended properties include author.url pointing to the creator's profile, comment, commentCount, dateModified, headline (not recommended for a SocialMediaPosting), interactionStatistic, isPartOf for a subforum, sharedContent and url. The digitalSourceType property lets you flag posts written by an AI model or a reply bot, and Google assumes content is human-made when it is missing.
For interactionStatistic, Google reads InteractionCounter values with these interaction types: LikeAction, DislikeAction, ViewAction, CommentAction or ReplyAction, and ShareAction. On schema.org, an InteractionCounter carries the interactionType and a userInteractionCount integer. Those counters are the engagement signals the programme wants refreshed within 72 hours.
Creator profiles
Every post in the programme must be attributable to a creator with a public profile. Google's profile page markup covers this: a ProfilePage needs a mainEntity that is a Person or Organization, and that entity needs a name, or an alternateName such as a handle when no name is available. Google lists a user profile on a forum or social site as a valid use. Link each post's author.url to that profile URL, as the forum guidance recommends.
A minimal post example
The example below follows Google's required and recommended properties for a forum post. Values are illustrative.
{
"@context": "https://schema.org",
"@type": "DiscussionForumPosting",
"url": "https://community.example.com/t/12345",
"headline": "Best way to batch-upload invoices?",
"text": "We upload about 400 invoices a month and the importer times out...",
"datePublished": "2026-11-16T09:12:00+05:30",
"author": {
"@type": "Person",
"name": "Asha R",
"url": "https://community.example.com/u/asha-r"
},
"isPartOf": "https://community.example.com/c/billing",
"commentCount": 3,
"interactionStatistic": [
{
"@type": "InteractionCounter",
"interactionType": "https://schema.org/LikeAction",
"userInteractionCount": 14
},
{
"@type": "InteractionCounter",
"interactionType": "https://schema.org/ViewAction",
"userInteractionCount": 1290
}
]
}
Keep markup and page in step. Google's general guidelines require that marked-up content be visible to readers, and state that correct markup still does not guarantee a feature appears. Expect the same discipline for anything sent through a push pipeline: counters in the payload should match counters on the page.
The engineering behind a pipeline
Google will hand over the integration documents only after acceptance, so the private API is unknown. The public requirements still tell you what to build in advance.
OAuth 2.0 service-to-service authentication
Google's OAuth 2.0 documentation says server-to-server calls use a service account, which belongs to the application rather than a user, so no OAuth client ID or user consent is needed. The server signs a JSON Web Token, swaps it for an access token, and creates a new signed token when the old access token expires. Google strongly recommends its client libraries over hand-built token code because creating and signing tokens yourself is complex and risky. Store the service account key in a secrets manager, rotate it, and give the pipeline its own identity separate from analytics or ads accounts.
Strictly validated JSON-LD payloads
Strict validation means a payload that fails schema checks should never leave your system. In practice:
- Generate the JSON-LD for a post from one serialiser used by both the page template and the outbound pipeline, so the two cannot drift.
- Validate each payload in CI and at runtime against the required properties: author name, ISO 8601 publish time and content.
- Reject or quarantine posts that fail, and alert on the rejection rate.
- Log every payload with a hash so you can prove what you sent if Google questions a record.
Timing: minutes for posts, 72 hours for counters
Google wants new posts sent ideally within minutes and engagement counter updates within 72 hours of creation. An event-driven design fits: a post-created event goes to a queue, a worker builds and validates the payload, and a sender delivers it with retries and back-off. Counter updates can batch on a schedule, for example hourly for the first day and then less often, as long as each post gets fresh counts inside its first 72 hours. Measure the gap from creation to delivery as a percentile, not an average, and include it in your application.
Moderation that removes bad posts upstream
Active moderation with user reporting is a hard requirement, and illegal content is disqualifying. Google's guidance on user-generated spam, updated on 26 October 2026, recommends a clear abuse policy shown at sign-up, letting trusted users report spam, spotting spam accounts from sign-up patterns, manual approval for suspicious activity, and keeping pages from new users without reputation out of the index with noindex or robots.txt. Wire your moderation decisions into the pipeline: a post that is removed or held should never be sent, and a post removed after sending should trigger whatever deletion signal Google provides once you are onboarded.
How to apply, step by step
Google takes expressions of interest through an application form linked from the programme page, and says applying does not guarantee a place.
- Check all six tests against your platform, and stop if you fail the gated content or UGC focus tests, since no amount of engineering fixes those.
- Ship valid DiscussionForumPosting or SocialMediaPosting markup with interactionStatistic on every post template, plus ProfilePage markup on creator profiles.
- Confirm the markup with the Rich Results Test and fix any warnings on the templates, not page by page.
- Write up your moderation policy, reporting flow and response times.
- Gather numbers: daily post volume, active creators, monthly users and your measured post-to-publish delay.
- Submit the form linked from the programme page.
- Plan for a reply in 6 to 8 weeks; if accepted, Google sends the technical documents and onboarding steps.
What happens after acceptance
Google only says that selected platforms receive detailed integration documentation and onboarding instructions. Budget for a build phase after acceptance rather than assuming a plug-in. If you have already built the event pipeline, validator and OAuth service account, most of the remaining work should be mapping to Google's payload format.
Should you apply? A quick decision guide
| Platform type | Likely fit | Why |
|---|---|---|
| Large public forum or community site | Strong | Matches the content focus, has profiles and usually has moderation in place |
| Social app with public post URLs | Strong if posts have stable public pages | Feed-only content does not count, single post pages do |
| Product support community | Possible | Qualifies only if users, not staff, write most threads and volume is high |
| Review or Q&A site | Possible | Q&A sites should use Q&A markup on pages, and Google has not said whether it accepts them |
| Member-only or paid community | No | Gated content is ineligible |
| Company blog with comments | No | Content is mainly publisher-written |
The fit ratings are our judgement based on Google's eligibility criteria and markup guidance. If you sit in the possible rows, fix the markup and moderation first: those improvements help Google's existing forum features even if the application is refused.
For a wider view of which schema types Google actually uses, see our structured data guide. If you are weighing Google's other creator features, our Search Profiles analysis covers who qualifies there.
India-specific considerations
Indian community platforms, edtech forums, regional-language social apps and fintech help communities can apply on the same terms; the programme page sets no country limit. Two local points matter. First, sending creator names and profile links to Google is processing of personal data, so map it in your records and privacy notice before 13 May 2027, when most operative duties under India's DPDP Rules start; our DPDP Rules checklist lists the dates. Second, for regional-language communities, the JSON-LD text must match the visible post in the same language, because Google's guidelines require marked-up content to be visible on the page.
How eCorpIT can help
eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our application development services team can add forum and profile markup to your templates, build the event pipeline, validator and OAuth service account, and prepare the numbers for your application. Talk to us at /contact-us/.
Last updated: 16 November 2026.