An XML sitemap is a file that lists the pages on your site you want search engines to find. On a forum with thousands of threads, many older discussions sit deep in the pagination where crawlers rarely reach, and a sitemap gives them a direct path. This guide explains what a forum sitemap should contain, the size limits to know about, and how to submit it.
What a sitemap does and does not do
A sitemap helps search engines discover URLs and learn when they last changed. It does not force a page into search results. Google describes submitting a sitemap as merely a hint: it may not download it or use every URL in it. Listing a URL in a sitemap is also only a weak signal when Google chooses which version of a page is canonical, compared with redirects and canonical tags.
So think of the sitemap as a helpful map, not a ranking tool. It works best on a site that already has clean URLs, sensible internal links, and good content.
What to include on a forum
Include pages a guest can actually view and that are worth finding in search:
- Forum index pages, such as
/forums/php-programming/. - Threads, which make up most of your sitemap.
- Tag pages that have enough threads to be useful.
- Member profiles, if they are public and contain something worthwhile. Many forums leave out profiles of members who have never posted.
Leave these out:
- Private forums, staff areas, and anything that needs a login.
- Search result pages, redirect pages, and posting forms.
- Pages marked
noindex, since listing them sends mixed signals. - Duplicate addresses, such as old query-string links that now redirect.
Quick BB's built-in sitemaps exclude private content automatically and list the friendly URLs rather than old parameter links.
Size limits and sitemap index files
Google's documentation sets these limits for each sitemap file:
| Limit | Value |
|---|---|
| URLs per sitemap file | 50,000 |
| File size per sitemap | 50MB uncompressed |
| Sitemaps listed in one sitemap index | 50,000 |
| Encoding | UTF-8 |
A busy forum can pass 50,000 threads sooner than you might expect. The answer is a sitemap index file: a small file that lists several sitemaps, each under the limits. A common approach is to split by content type (forums, threads, tags, members) and then split threads into numbered files. You submit the index, and search engines find the rest from it.
Google also says the sitemaps listed in an index should be on the same site and in the same directory as the index file or below it. Keeping all your sitemap files together at the root of the forum avoids problems.
Quick BB generates sitemaps with index files, so a growing forum is split automatically.
Getting the details right
Use full, canonical URLs
Every <loc> entry should be a fully qualified address, including https:// and your domain. Google crawls URLs exactly as listed, so they should match the canonical version of each page: same protocol, same www or non-www choice, same trailing slash.
Make lastmod honest
The <lastmod> date tells search engines when a page last changed. Google says it uses this value only if it is consistently and verifiably accurate, and that it should reflect significant changes such as new content, not trivial ones. For a thread, a sensible lastmod is the time of the latest reply. Do not set every page to today's date; that teaches search engines to ignore the field.
Do not bother with priority or changefreq
The sitemap format allows <priority> and <changefreq> tags, but Google states that it ignores both. You can leave them out.
Paginated threads
Long threads have several pages, each with its own replies and its own canonical URL. Listing the first page of each thread is the minimum. Including later pages can help search engines find replies deep in long discussions, as long as those pages are linked normally and not marked noindex.
Submit your sitemap
There are two simple ways to tell search engines where your sitemap is, and it is worth doing both:
- Add it to robots.txt. Put a line like
Sitemap: https://www.example.com/sitemap.xmlanywhere in your robots.txt file. Google picks it up the next time it reads that file, and other search engines read this line too. - Submit it in Google Search Console. Add your forum as a property, open the Sitemaps report, and enter the sitemap index address. The report shows when it was last read and any errors.
Google retired its old sitemap "ping" address in 2023, so there is no need to set up automatic pings to it. An accurate lastmod and the two methods above are enough. Other search engines offer their own webmaster tools with similar submission options.
Check that it works
- Open the sitemap in your browser. You should see well-formed XML with your real URLs, not an error or a login page.
- Spot-check a few URLs while logged out. Each should load the page without redirecting.
- Look for private content. Search the file for the name of a private or staff forum. It should not appear.
- Review the Search Console report after a few days for errors such as "couldn't fetch" or URLs blocked by robots.txt.
- Compare counts. The number of thread URLs should be close to the number of public threads on your forum.
Keep it tidy over time
A sitemap should update itself as members post. If you merge, move, or delete threads, the old URLs should drop out. When you change your URL structure or move to new software, regenerate the sitemap and make sure old addresses redirect; see SEO-friendly forum URLs and migrating to new forum software. For the wider picture, read the forum SEO guide and forum tags and hashtags. Quick BB's sitemap and SEO features are listed on the features section of the home page.
Frequently asked questions
How many URLs can one sitemap hold?
Google allows up to 50,000 URLs or 50MB uncompressed per sitemap file. Larger forums use a sitemap index that lists several sitemap files.
Should private forums be in the sitemap?
No. List only pages a logged-out visitor can view, and leave out private forums, staff areas, search results and noindex pages.
Do priority and changefreq matter?
Google says it ignores both. An accurate lastmod date, such as the time of the latest reply, is far more useful.
