{"id":632453,"date":"2026-10-16T13:42:15","date_gmt":"2026-10-16T13:42:15","guid":{"rendered":"https:\/\/www.newsbeep.com\/nz\/632453\/"},"modified":"2026-10-16T13:42:15","modified_gmt":"2026-10-16T13:42:15","slug":"google-takes-applications-for-a-ugc-pipeline-separate-from-crawling","status":"publish","type":"post","link":"https:\/\/www.newsbeep.com\/nz\/632453\/","title":{"rendered":"Google Takes Applications For A UGC Pipeline Separate From Crawling"},"content":{"rendered":"<p>For most websites, <a href=\"https:\/\/www.searchenginejournal.com\/website-crawling\/485275\/\" rel=\"nofollow noopener\" target=\"_blank\">crawling<\/a> is still how you get into Google Search. Googlebot finds a URL and retrieves the page; then, independently, Google\u2019s systems determine if they want to add this page to their index.<\/p>\n<p>On Oct. 8, Google added Search Central documentation describing how approved forums and social platforms can submit user-generated content directly to Google.<\/p>\n<p>The <a href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/ugc-fresh-data-program\" target=\"_blank\" rel=\"noopener nofollow\">UGC Fresh Data Program<\/a> allows approved platforms to submit content and interaction signals through a \u201cdedicated data ingestion pipeline\u201d that accepts data submission from those platforms. Google states that the pipeline is separate from both traditional crawlers and the Indexing API. According to Google, participation in the UGC Fresh Data Program does not ensure your content will be included in Google Search.<\/p>\n<p>Google has partnered with individual social platforms before, including Twitter in 2009 and Reddit in 2024. This time the criteria are posted and there\u2019s an <a href=\"https:\/\/docs.google.com\/forms\/d\/e\/1FAIpQLScCpW46_ZiFS7ormuphFnz0Fxt18Ott-z1I4jWq2C4bEjPQWQ\/viewform\" target=\"_blank\" rel=\"noopener nofollow\">application form<\/a>, so you can check most of Google\u2019s requirements against a platform\u2019s own pages before applying. The form asks how many monthly active users the platform has and when it launched.<\/p>\n<p>What Google Posted<\/p>\n<p>The <a href=\"https:\/\/developers.google.com\/search\/updates\" target=\"_blank\" rel=\"noopener nofollow\">Search Central documentation changelog<\/a> links to the page under the entry for Oct. 8: \u201cAdded documentation on the UGC Fresh Data Program.\u201d Google wrote that the page is meant to explain the program\u2019s purpose and help applicants \u201cunderstand the eligibility criteria and how to participate.\u201d<\/p>\n<p>The <a href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/ugc-fresh-data-program\" target=\"_blank\" rel=\"noopener nofollow\">program page<\/a> opens with this description:<\/p>\n<p>The UGC Fresh Data Program is an initiative designed to help platforms display fresh, high quality, and authentic user-generated content (UGC) across various features on Search.<\/p>\n<p>Google says sending content through the pipeline \u201chelps ensure that fresh content is processed and quickly updated in Search.\u201d The page gives no time frame for \u201cquickly.\u201d It also says the program \u201cdoesn\u2019t guarantee that content will appear in Search.\u201d<\/p>\n<p>The page limits the program to \u201ctrending UGC content.\u201d It describes the pipeline as \u201cindependent of the Google Indexing API and traditional organic crawling for general web content.\u201d<\/p>\n<p>Oct. 8 is when the page went up. Neither the page nor the changelog entry says when the pipeline started operating.<\/p>\n<p>Who Google Says Can Apply<\/p>\n<p>Google <a href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/ugc-fresh-data-program\" target=\"_blank\" rel=\"noopener nofollow\">lists six criteria<\/a>, using the labels below.<\/p>\n<p>Content focus. The platform must primarily host \u201cUGC, social postings, or forum discussions.\u201d Content should sit on dedicated pages with stable URLs, \u201cnot on profile or feed pages.\u201d<br \/>\nVolume and audience. \u201cA high volume of UGC content and a significant user base.\u201d<br \/>\nContent accessibility. Content must be on public pages that Googlebot and users can reach. Anything behind a login or paywall doesn\u2019t qualify, and all UGC must be tied to \u201ca creator with a public profile.\u201d<br \/>\nTechnical readiness. The platform must be able to implement \u201csecure OAuth 2.0 API authentication\u201d and build \u201cstrictly validated JSON-LD payloads.\u201d It must already use, or be prepared to implement, valid on-page schema.org markup. Google\u2019s example is SocialMediaPosting or DiscussionForumPosting with interactionStatistic sub-fields.<br \/>\nContent health and moderation. No illegal content, plus active moderation that includes a way for users to report posts.<br \/>\nContent freshness. Content must be \u201cas fresh as possible, ideally sent within minutes,\u201d and the platform must be able to submit \u201cregular updates of engagement counters (within 72 hours of creation).\u201d<\/p>\n<p>Submitting an application \u201cdoesn\u2019t guarantee participation,\u201d according to the page, and Google will share developer documents \u201conce accepted into the program.\u201d<\/p>\n<p>The <a href=\"https:\/\/docs.google.com\/forms\/d\/e\/1FAIpQLScCpW46_ZiFS7ormuphFnz0Fxt18Ott-z1I4jWq2C4bEjPQWQ\/viewform\" target=\"_blank\" rel=\"noopener nofollow\">form<\/a> has seven required fields: company name, service domain, 10 sample URLs with UGC, monthly active users, launch date, a Search Console owner\u2019s email and a contact email. It calls a submission \u201cmerely an expression of interest\u201d and says Google \u201chas no obligation to incorporate your content in our features.\u201d<\/p>\n<p>The form goes further than the page on where content could show up, saying submitted content \u201cis eligible to serve on Google Search and other surfaces, especially for time-sensitive or fresh content.\u201d It adds, \u201cwe never guarantee serving as that is determined entirely by ranking algorithms.\u201d<\/p>\n<p>How It Compares With Crawling And The Indexing API<\/p>\n<p>Any site can ask Google to crawl its pages, according to Google\u2019s <a href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/ask-google-to-recrawl\" target=\"_blank\" rel=\"noopener nofollow\">recrawl documentation<\/a>. Owners and full users of a Search Console property can request crawls of individual URLs in the URL Inspection tool, within a quota, and sitemaps cover larger sets of URLs. Google says crawling \u201ccan take anywhere from a few days to a few weeks,\u201d and that a request \u201cdoes not guarantee that inclusion in search results will happen instantly or even at all.\u201d<\/p>\n<p>The <a href=\"https:\/\/developers.google.com\/search\/apis\/indexing-api\/v3\/quickstart\" target=\"_blank\" rel=\"noopener nofollow\">Indexing API<\/a> is narrower. It covers pages with JobPosting, or BroadcastEvent embedded in a VideoObject, and lets their owners tell Google when a page is added, updated or removed. This \u201callows Google to schedule pages for a fresh crawl.\u201d There is a \u201cdefault 200 quota\u201d available for API onboarding and submission testing; however, the API \u201crequires additional approval for usage and resource provisioning.\u201d In <a href=\"https:\/\/www.searchenginejournal.com\/google-indexing-api-approval-job-sites\/590316\/\" rel=\"nofollow noopener\" target=\"_blank\">a September post<\/a> I noted several job boards had gone months without a reply to their approval requests.<\/p>\n<p>Recrawls, sitemaps, the Indexing API provide the URL for crawling. Platforms submit what Google calls \u201ccontent and interaction signals\u201d through the UGC program, but this does not replace public URLs. The criteria still require that the content be accessible via Googlebot.<\/p>\n<p>The Indexing API has a default quota for onboarding and testing, with additional approval required for further usage. The UGC program requires Google to approve applicants. Neither guarantees that submitted content will appear in Search. Of the three options being compared here, recrawl requests and sitemaps do not include a request for approval. The program\u2019s \u201cwithin minutes\u201d wording covers sending, not indexing.<\/p>\n<p>Google Has Partnered With Social Platforms Before<\/p>\n<p>On Dec. 7, 2009, Google <a href=\"https:\/\/googleblog.blogspot.com\/2009\/12\/relevance-meets-real-time-web.html\" rel=\"nofollow noopener\" target=\"_blank\">launched real-time search results<\/a> that showed \u201clive updates from people on popular sites like Twitter and FriendFeed.\u201d The post named Facebook, MySpace, FriendFeed, Jaiku and Identi.ca as new partners, along with Twitter, which Google said it had announced \u201ca few weeks ago.\u201d<\/p>\n<p>In July 2011, Google said \u201cthat agreement expired on July 2,\u201d as <a href=\"https:\/\/www.datamation.com\/trends\/google-realtime-goes-dark-after-twitter-agreement-expires\/\" target=\"_blank\" rel=\"noopener nofollow\">Datamation reported<\/a> at the time. In May 2015, Google <a href=\"https:\/\/blog.google\/products-and-platforms\/products\/search\/tweets-take-flight-in-google-app\/\" target=\"_blank\" rel=\"noopener nofollow\">said it was bringing Tweets<\/a> to Search on mobile, and it added desktop that August.<\/p>\n<p>In February 2024, Google stated that it \u201cnow has access\u201d to <a href=\"https:\/\/blog.google\/company-news\/inside-google\/company-announcements\/expanded-reddit-partnership\/\" target=\"_blank\" rel=\"noopener nofollow\">Reddit\u2019s Data API<\/a>. According to Google, this Data API delivers \u201creal-time, structured, unique content.\u201d Google noted that accessing the Data API would provide \u201cenhanced signals that will help us better understand Reddit content and display, train on, and otherwise use it.\u201d Furthermore, Google states that this partnership does not affect its use of publicly accessible (crawl-able) content from the Internet for indexing, training or displaying such content in Google products.<\/p>\n<p>Those partnerships mentioned above are the ones Google announced with named entities. However, those earlier posts did not provide sufficient technical information so as to allow comparison with the new pipeline. While the 2024 description notes \u201caccess to Reddit\u2019s Data API,\u201d the Oct. 8 posting describes approved platforms providing data through a Google ingestion pipeline. There was no reference to the Reddit partnership in the program page or the form.<\/p>\n<p>As noted previously, one of the uses listed in the 2024 post is training. However, neither the program posting nor the posted application form referenced \u201ctraining.\u201d<\/p>\n<p>There is a clear distinction between what has been published about the new program and the earlier partnerships. Google has made available to the general public both the eligibility criteria for participation in the new program and an online application. As previously discussed, Google provided identification of individual social platform partners through prior announcements.<\/p>\n<p>What Forum Markup Already Carries<\/p>\n<p>Google\u2019s support for the markup the program names predates it by almost three years. In November 2023, Google <a href=\"https:\/\/developers.google.com\/search\/blog\/2023\/11\/discussion-and-profile-markup\" target=\"_blank\" rel=\"noopener nofollow\">added discussion forum and profile page structured data<\/a>, which <a href=\"https:\/\/www.searchenginejournal.com\/google-highlights-forums-profiles-with-new-structured-data\/502301\/\" rel=\"nofollow noopener\" target=\"_blank\">I covered at the time<\/a>. Google said the markup works with features \u201cdesigned to show first-person perspectives from social media platforms, forums, and other communities,\u201d and that using it \u201cdoes not guarantee appearance.\u201d<\/p>\n<p>In June 2024, the <a href=\"https:\/\/developers.google.com\/search\/updates\" target=\"_blank\" rel=\"noopener nofollow\">changelog<\/a> confirmed that SocialMediaPosting markup is also supported, \u201cto more accurately reflect how the data ingestion for these features work.\u201d In March 2026, Google added forum and Q&amp;A properties \u201cfor providing more clarity on comment thread structure to Google ingestion systems.\u201d The update included labels for AI-generated and bot content, <a href=\"https:\/\/www.searchenginejournal.com\/google-adds-ai-bot-labels-to-forum-qa-structured-data\/570425\/\" rel=\"nofollow noopener\" target=\"_blank\">which I covered in March<\/a>.<\/p>\n<p>Google\u2019s current <a href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/structured-data\/discussion-forum\" target=\"_blank\" rel=\"noopener nofollow\">discussion forum markup page<\/a> lists five interaction types it supports in interactionStatistic: likes or upvotes, dislikes or downvotes, views, comments, and reshares. The program page names the same markup, with interactionStatistic, as its example of what applicants should have on their pages.<\/p>\n<p>Neither the forum documentation nor the program page says how Google uses those counts in ranking.<\/p>\n<p>Why This Matters<\/p>\n<p>Google documents point to a separate intake for trending posts from forums and social platforms, apart from the crawling it uses for general web content. Approved platforms send the posts and their interaction signals themselves, while recrawl requests, sitemaps and the Indexing API all hand Google a URL to crawl.<\/p>\n<p>Any platform that includes only feed items; requires login credentials for post views; or has user generated posts that cannot be linked back to a public profile does not qualify under the current specifications regardless of the size of their platform. The ten example URLs provided are intended to represent the format the platform plans to send to Google.<\/p>\n<p>Whether or not the platform chooses to apply, the technical SEO can focus on the markup. Valid on-page structured data is one of the requirements, and in 2023 Google <a href=\"https:\/\/developers.google.com\/search\/blog\/2023\/11\/discussion-and-profile-markup\" target=\"_blank\" rel=\"noopener nofollow\">provided Search Console reporting and Rich Results Test support<\/a> for both forum and profile markup. Those reports show errors, warnings, and valid items related to marked-up forum and profile pages.<\/p>\n<p>If a site\u2019s primary source of content is not user-generated content, then it fails the first qualification. However, these types of sites may still be competing against User Generated Content (Forum\/Social) on the same searches, but Google did not name any participants. If you find your searches yielding more forum results, currently, there is no way within either the program page or form to determine whether the program is responsible for those increased results.<\/p>\n<p>What Google Hasn\u2019t Said<\/p>\n<p>As of Oct. 15, none of the program page, form, or changelog entry (Oct. 8) names a participating platform. None of these items establish a numerical value for \u201ca significant user base\u201d despite this being one of the values requested via the Form to be reported as Monthly Active Users.<\/p>\n<p>The program page references \u201cvarious features on Search,\u201d while the form says \u201cGoogle Search and other surfaces.\u201d They don\u2019t identify a feature. The 72-hour counter window isn\u2019t explained either.<\/p>\n<p>The three listed documents also do not indicate how Google utilizes the interaction signals\/engagement counts provided by participants; nor do they specify if participants will receive any reporting.<\/p>\n<p>Looking Ahead<\/p>\n<p>Applications are open through the form linked from the <a href=\"https:\/\/developers.google.com\/search\/docs\/appearance\/ugc-fresh-data-program\" target=\"_blank\" rel=\"noopener nofollow\">program page<\/a>. Google says it will get back to applicants \u201cwithin 6-8 weeks with a response on the status of your application.\u201d Selected platforms then get \u201cdetailed technical integration documentation and onboarding instructions,\u201d with no stated schedule for that step.<\/p>\n<p>Google\u2019s Search Central changelog records the Oct. 8 addition. It\u2019s a place to watch for future changes to the documentation.<\/p>\n<p>More resources:<\/p>\n<p>Featured Image: Tetiana Yurchenko\/Shutterstock. Source: Google.<\/p>\n","protected":false},"excerpt":{"rendered":"For most websites, crawling is still how you get into Google Search. Googlebot finds a URL and retrieves&hellip;\n","protected":false},"author":2,"featured_media":632454,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[111,139,69,145],"class_list":["post-632453","post","type-post","status-publish","format-standard","has-post-thumbnail","category-technology","tag-new-zealand","tag-newzealand","tag-nz","tag-technology"],"_links":{"self":[{"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/posts\/632453","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/comments?post=632453"}],"version-history":[{"count":0,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/posts\/632453\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/media\/632454"}],"wp:attachment":[{"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/media?parent=632453"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/categories?post=632453"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/tags?post=632453"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}