What should I do if I get a "Prerender integration not detected" error in the Domain Manager?

TL;DR

The "Prerender integration not detected" error in the Domain Manager means the validation check did not see the Prerender.io integration responding on your domain. Simulate a bot visit and look for the x-prerender-requestid response header. If the header is missing, the most common causes are integration placement (it should sit at the CDN or reverse proxy layer, not in your app), missing or incorrect token, or a conflicting plugin. Fix the underlying cause and re-run the Domain Manager validation.

What this error means

The "Prerender integration not detected" error appears in the Domain Manager when the validation check can't confirm that Prerender.io is intercepting bot traffic on your domain. If left unresolved, AI crawlers and search engines will not receive your prerendered HTML snapshots, which directly affects how your site shows up in search results and AI answers.

Step 1: verify the integration with a bot request

Before treating this as a real configuration problem, confirm the error is not just a transient validation issue.

• Simulate a bot visit. Open your site in Chrome, open DevTools, switch to the Network tab, and emulate a search engine bot User-Agent (Googlebot is the easiest). For step-by-step instructions, see how to verify your Prerender.io integration.
• Check the response headers. If x-prerender-requestid is present, the integration is working and the Domain Manager validation may have failed transiently. If x-prerender-requestid is missing, there is a real configuration issue to fix.

Step 2: identify the cause and apply the fix

If the x-prerender-requestid header is missing, work through the three most common causes below. Each scenario is independent, so you can skip to the one that matches your setup.

Cause 1: the integration is at the wrong layer

Prerender.io should be integrated as close to the visitor as possible, ideally at the CDN or reverse proxy layer. If it is implemented at the application layer instead, traffic from bots may reach your app directly and never hit Prerender.io.

Fix: move the integration to your CDN or reverse proxy so it can intercept bot requests before they reach your application. For CDN-specific guidance, see how Prerender.io works with CDNs.

Cause 2: the integration is misconfigured

The integration may be installed in the right place but configured incorrectly. The most common configuration mistakes are a missing or incorrect Prerender.io token, a User-Agent allow-list that doesn't match the bot you tested with, or URL routing patterns that don't include the page you tried to load.

Fix:

• Confirm your Prerender.io token is set correctly. You can find it under the Security and Access menu.
• Check that the User-Agent you tested with is in your integration's allow-list.
• Confirm the URL pattern in your integration covers the routes you intend to prerender.

Cause 3: another tool is interfering

Caching plugins, edge workers, security middleware, or other reverse proxies can intercept the request before Prerender.io and either short-circuit it or strip the response headers.

Fix:

• List every layer that handles incoming requests for your domain (CDN, edge worker, load balancer, security plugin, application middleware).
• Temporarily disable suspected conflicting tools one at a time and re-run the bot simulation.
• Once you identify which layer is interfering, reorder it so Prerender.io intercepts first, or add an exclusion so the conflicting tool ignores bot requests.

Step 3: re-run the Domain Manager validation

After fixing the underlying cause, go back to the Domain Manager and run the validation again. The error should clear once Prerender.io sees its own x-prerender-requestid header on a bot request to your domain.

Related articles

• Easy integration guide
• How does Prerender.io work?
• Available integrations
• How to verify your Prerender.io integration
• How Prerender.io works with CDNs