Limiting Prerender rendering to your sitemap URLs
Prerender renders every URL a crawler requests — not just the ones in your sitemap. Here's what that means and how to control it.
TL;DR
By default, Prerender renders and caches every URL that an AI crawler or search engine requests — not just the URLs listed in your XML sitemap. There's no built-in sitemap filter in Prerender. To limit rendering to sitemap URLs, you need to modify your integration so it only routes sitemap-listed URLs through Prerender. Prioritizing high-value pages and monitoring your render history are the most practical ways to keep render usage efficient.
Why Prerender renders URLs outside your sitemap
Prerender works by intercepting requests from AI crawlers and search engines as they arrive — not by reading your sitemap first. When a crawler follows a link to a page on your site, Prerender renders that page regardless of whether it appears in your sitemap.
Your sitemap tells AI crawlers and search engines which pages you want indexed. It doesn't instruct Prerender on what to cache. These are two separate signals, and Prerender acts on the crawler request — not the sitemap.
On large or dynamic websites, this means Prerender may render pages you didn't intend to cache: filtered results, user-specific paths, paginated URLs, and others.
ℹ️ Updating your XML sitemap does not automatically restrict what Prerender caches. Your sitemap and Prerender's rendering behavior are independent of each other.
How to limit rendering to sitemap URLs
Prerender doesn't have a built-in option to filter rendering by sitemap. To restrict rendering to your listed URLs, you need to modify your integration so that AI crawlers and search engines are only routed through Prerender for URLs that appear in your sitemap.
The implementation depends on your stack — the filtering logic belongs in your server configuration, CDN worker, or integration layer. See how to control crawling and indexing for guidance, or contact our support team if you need help identifying where to add this logic for your specific setup.
ℹ️ Not sure where to start? Ask Nexus, your AI integration assistant in your Prerender dashboard — describe your stack and Nexus will recommend the right approach for adding sitemap-based URL filtering to your integration.
Best practices for controlling what gets cached
Cache high-value pages. Focus your Prerender usage on landing pages, category pages, and the URLs most likely to appear in AI-generated answers and search results. These are the pages where pre-rendering delivers the most value.
Refresh your sitemap parsing regularly. If your site content changes often, stale sitemap data can mean new or removed pages aren't handled correctly. Set a sitemap reload interval that reflects how frequently your content changes.
Exclude irrelevant URLs. Add logic to your integration to block login pages, user-specific dashboards, and URLs with query parameters that generate near-duplicate pages.
Monitor your render history. Check your Prerender dashboard regularly to spot URLs being cached that shouldn't be. Unexpected renders can indicate crawler behavior or integration gaps worth addressing.
💬 Still need help?
If you're not sure how to add sitemap filtering to your integration, our support team can help you work through the right approach for your stack.
→ Contact us at support@prerender.io