APG vNext generates an XML sitemap automatically. Submitting it to Google Search Console (formerly Google Webmaster Tools) helps Google discover and index all your forum content faster.
Step 1: Enable and Verify the Sitemap
- Go to Admin Panel → Settings → SEO and ensure XML Sitemap is enabled.
- Your sitemap URL will be:
https://yourdomain.com/community/sitemap.aspx - Visit this URL in your browser to verify it returns valid XML.
Step 2: Submit to Google Search Console
- Log in to Google Search Console.
- Select your property (verify your domain if you haven't already).
- Click Sitemaps in the left sidebar.
- Enter your sitemap URL in the "Add a new sitemap" field and click Submit.
Step 3: Monitor Indexing
- Google Search Console will show how many URLs from your sitemap have been discovered and indexed.
- Check back after 1-2 weeks to see indexing progress.
- If some pages are not indexed, check the Coverage report for specific errors.
For more SEO tips, see the Content Marketing Features in APG vNext.
Advanced Sitemap Optimisation for APG vNext
The default APG vNext sitemap includes all public forum threads, Knowledge Base articles, and static pages. For large communities with thousands of threads, the sitemap can contain too many low-quality or thin-content pages that dilute the crawl budget Google allocates to your site. Optimise the sitemap by excluding forum categories with very low post counts, archived or locked forums, and member profile pages from the sitemap. Configure sitemap exclusions in Admin Panel → SEO → Sitemap → Exclude Categories. Keeping the sitemap focused on high-quality, substantive content pages signals to Google that all indexed pages are worth crawling, improving the overall indexing rate.
Sitemap Priority and Change Frequency
APG vNext assigns sitemap priority values based on page type: the forum home page receives priority 1.0, forum category pages receive 0.9, active thread pages receive 0.8, and inactive thread pages receive 0.5. Change frequency values are set based on observed activity: threads with recent posts use changefreq=daily, while older inactive threads use changefreq=monthly. These values guide search engine crawlers on how frequently to revisit each page, helping ensure that active, current content is recrawled promptly while stable historical content is revisited less often to conserve crawl budget.
Monitoring Sitemap Processing in Google Search Console
After submitting the sitemap, monitor its processing status in Google Search Console → Sitemaps. The report shows the number of URLs submitted versus the number indexed, and any sitemap errors that prevented processing. A significant gap between submitted and indexed URLs (less than 50% indexed) typically indicates crawl budget constraints caused by thin content, duplicate content, or too many low-value pages included in the sitemap. Address these by improving content quality, implementing canonical tags, and reducing the number of pages in the sitemap until the indexing rate improves.
Image Sitemaps for Forum Media Content
If your APG vNext forum hosts significant image content (galleries, product photos, user-uploaded images), consider enabling the image sitemap extension that APG vNext 5.x supports. Image sitemaps include metadata about each image (URL, title, caption, location URL) that helps Google Image Search discover and attribute forum images to the correct source page. Enable image sitemaps in Admin Panel → SEO → Sitemap → Include Image Data. Image sitemaps can drive significant additional traffic from image searches, particularly for communities in visual niches such as photography, design, food, or travel.
Related Resources
Sitemap Performance and Crawl Budget Management
For APG vNext forums with a large number of threads, effective sitemap management is critical to maximising Google's crawl efficiency. A common mistake is submitting a sitemap with thousands of low-quality, short-content, or near-duplicate threads that consume crawl budget without contributing to organic search visibility. Google allocates a finite crawl budget to each domain based on domain authority, page load speed, and server response consistency. Submitting too many low-value URLs causes Google to distribute the crawl budget across more pages, resulting in each page being crawled less frequently. The practical effect is slower indexing of new, high-quality content because the crawler is spending time on old thin-content pages.
Segment Sitemaps by Content Type
For communities with more than 10,000 URLs, use the APG vNext multiple-sitemap feature to generate separate sitemap files for different content types: one sitemap index for Knowledge Base articles (high-quality content), one for active threads (threads with recent activity), and one for archived threads (older threads with no recent activity). Submit the Knowledge Base and active thread sitemaps to Google Search Console for active crawling. Consider omitting the archived thread sitemap or submitting it with a low priority signal to guide Google toward your best content first. The sitemap index file (/sitemap-index.xml) references all individual sitemaps, while Search Console allows selective submission of specific sitemap files from the index.
Monitoring and Responding to Coverage Errors
Google Search Console's Coverage report identifies specific URLs from your sitemap that cannot be indexed, along with the reason for each exclusion. Common exclusion reasons for APG vNext forums include: Redirect (the URL redirects to a different URL, which should be updated in the sitemap to point to the final destination), Soft 404 (a thread page that returns HTTP 200 but contains very little content — usually deleted threads where APG vNext shows a generic message rather than a 404), and Blocked by robots.txt (URLs that APG vNext has flagged as no-index in robots.txt that are also present in the sitemap — a contradiction that confuses crawlers). Review the Coverage report monthly and address each category of errors to improve the overall indexing health of the community.
Looking for more help? Browse the support forum or check the Knowledge Base.