On this page
Forum SEO runs on the same mechanics as the rest of SEO, with its own list of ways to fail. Threads still rank in 2026, and Google still ships a search feature built to surface them. What has changed is the margin for error. A thread page competes against a Reddit thread on the same question, an AI Overview that answers it without a click, and the board's own duplicate URLs.
Discussions and forums, and the markup behind it
Google announced support for discussion forum and profile page structured data on 27 November 2023, in a Search Central post by Thomas Han. DiscussionForumPosting is described in the current documentation as markup "designed for any forum-style site where people collectively share first-hand perspectives". It feeds the Discussions and forums feature in Search. The announcement was careful about what that buys you: "Forums with this markup are considered for having their content appear in the Perspective and 'Discussions and forums' features. However, the use of the markup does not guarantee appearance."
| Property | Status | What it does |
|---|---|---|
author, author.name | Required | Identifies who wrote the post |
datePublished | Required | When the post went up |
text, image or video | Required (at least one) | The content itself |
comment | Recommended | Carries the replies, nested to match the board's threading or flattened under the original post if the board is linear |
commentCount | Recommended | Covers replies the page doesn't show |
interactionStatistic | Recommended | Carries upvotes |
author.url | Recommended | Points at a profile marked up with ProfilePage |
creativeWorkStatus (Deleted) | Recommended | Flags posts removed but kept for threading context |
digitalSourceType | Recommended | Flags machine-generated content |
Google assumes content is human-generated when digitalSourceType is absent, so a board publishing bot replies without marking them makes an implicit claim.
For multi-page threads, Google asks that later pages include the original post with the main page URL, so page 14 is still recognisably part of the same thread. If the board is question-and-answer shaped, use Q&A markup instead, and never both on one page.
The 2024 Reddit deal and forum visibility
In February 2024, Reuters reported that Google was paying Reddit roughly 60 million dollars a year to license its content for AI model training, in the same week Reddit filed for its IPO. Search Engine Land covered the deal on 22 February 2024 and tied it to something SEOs had already noticed: the consultant Glenn Gabe, citing Semrush data, put Reddit URLs ranking in Google at about 22 million in May 2023 and 41.1 million in February 2024.
The two facts are not the same fact, and Google says so. In a report published by The Verge on 4 August 2026 about promotional posting aimed at AI search systems, Google's Jennifer Kutz said Reddit "gets no special preference" in its ranking systems and that its AI features do not target any specific platform. Her framing of forums is worth taking seriously: they carry both high-quality and low-quality content, and Google's systems are built to tell the difference.
What the deal changed is the weather. By July 2026 the Wall Street Journal reported that Reddit was weighing whether to cut off Google's access for AI training, with the stock falling around 9 percent on the news, as covered by eMarketer on 24 July 2026. The driver is referral traffic: Digital Content Next puts the drop in publisher referrals from AI Overviews at as much as 25 percent, a figure Google disputes. For an independent forum owner the read is that discussion content is now valuable enough to license and exposed enough to be summarised, which argues for owning the archive rather than renting space on a platform that may renegotiate its own distribution.
Thread indexing and what kills it
Thread pages get indexed the ordinary way, through crawlable <a href> links, sitemaps and internal linking, and they fail in a few repeatable ways that Search Console names (the full list is in the table further down).
Thin threads produce "Crawled - currently not indexed": the page was crawled but not indexed, and may or may not be indexed later. A board with thousands of three-reply threads accumulates these, and resubmission changes nothing. Very large boards also hit "Discovered - currently not indexed", which the documentation attributes to Google rescheduling a crawl it expected to overload the site.
User-generated spam is a named category in Google's spam policies, which list "spammy posts on forum threads" and note that site owners are often unaware of it. The recommended handling for links inside member posts is rel="ugc", which the documentation says can be dropped for contributors who have consistently posted well over time. A related risk arrived in 2024 with Google's site reputation policy, aimed at third-party content published on a trusted domain to exploit its reputation. It was adjusted on 28 August 2026: from 30 August, manual actions under it affect results outside the European Economic Area, while inside the EEA the affected section may instead be separated so it ranks independently from the rest of the site. Either way the action shows in Search Console. Bulk AI-generated threads fall under a different heading, scaled content abuse.
Pagination, facets and noindex accidents
Google's pagination guidance is specific and often broken by forum software defaults. Give every page in a sequence a unique URL, typically ?page=n, and do not canonicalise page two onwards back to page one; each page needs its own canonical. Do not use fragment identifiers for page numbers, because Google ignores everything after the hash mark, and do not expect rel="next" and rel="prev" to help: Google no longer uses those tags.
Faceted and sorted URLs are the bigger drain. Google's crawling documentation warns that parameter-based filtering can generate infinite URL spaces, causing overcrawling and slower discovery of new pages. Every combination of sort order, tag filter, date range and view mode is a URL a crawler will try. The recommended fixes are blunt on purpose: disallow those parameter patterns in robots.txt, or move filters into URL fragments, which Google generally does not crawl. Canonical tags and nofollow are described as less effective long term.
The noindex mistakes are expensive because they are silent. Blocking a URL in robots.txt is not a noindex, and Search Console has a status for the result: "Indexed, though blocked by robots.txt", where Google indexes the page from external links without reading it. To keep a page out you must remove the robots block so Google can crawl it and see the noindex. The reverse error is more common on forums: software that ships noindex on member profiles, tag pages and search results, then extends it to thread pages after a template change. Those show up as "URL marked 'noindex'".
Search Console for a forum owner
Google's own guidance says a site with fewer than 500 pages probably does not need the page indexing report. Any active forum passes that line within months. Watch the ratio of indexed pages to total threads over time instead of the absolute number, and watch which statuses grow.
| Status | What it means | What to do |
|---|---|---|
Crawled - currently not indexed | The page was crawled but judged too thin to index | Resubmitting changes nothing; add real substance to the thread |
Discovered - currently not indexed | Google rescheduled a crawl it expected to overload the site | A server capacity limit, not a content or SEO problem |
Indexed, though blocked by robots.txt | Google indexes the page from external links without reading it | Remove the robots block so Google can crawl the page and see its noindex |
URL marked 'noindex' | Forum software shipped noindex on profiles, tags or search results and it spread to threads after a template change | Check the template for the accidental tag |
Duplicate without user-selected canonical | Points to pagination or session parameters rather than content quality | Give every page in a sequence its own URL and its own canonical |
Search Console added weekly and monthly aggregation to the performance charts on 10 December 2025, which suits forums better than daily data because thread traffic is spiky. A branded queries filter arrived in November 2025, which separates people searching for the community by name from the people who found a thread while looking for an answer. The second group grows the board.
Generative AI performance reports were announced on 3 June 2026 and, per Google's note on that post, rolled out to all websites worldwide as of 31 August 2026. They show impressions in AI Overviews and AI Mode by page, country, device and date, which is how you learn whether threads are being read into answers without being clicked. The discussion forum rich result report shows errors on marked-up thread pages, and URL Inspection confirms what Google rendered on a single thread when the aggregate reports disagree with expectations.