Render
Render preview environments: no default noindex
Render does not add X-Robots-Tag: noindex to previews automatically. How to add response headers yourself, per service type, and verify.
Render does not add "X-Robots-Tag: noindex" to preview environments or onrender.com URLs; no header comes from Render by default, so previews are indexable unless you add the header yourself. Static sites take headers in the dashboard as path and value pairs, and web services set them in application code gated on Render's IS_PULL_REQUEST environment variable.
Why Render does this
Render's docs describe preview environments as "a disposable copy of your production environment" created per pull request, each with its own onrender.com URL, and say nothing about sending a robots header; the platform has a standing feature request for noindex headers on onrender.com URLs rather than shipped behavior. What Render does give you is a documented signal: the default environment variable IS_PULL_REQUEST is "true" for pull request previews and "false" otherwise, as strings. For static sites, the headers doc says custom headers are defined "in the Render Dashboard", with a relative header path and wildcards, for example "/*" with the header "X-Robots-Tag" and value "noindex". For web services there is no dashboard header setting, so the header has to come from the framework or server code, branched on IS_PULL_REQUEST so production stays clean.
Check it right now
Before changing anything, confirm what a crawler actually sees. The check is free, takes one URL and needs no account.
How to fix it
- Run the X-Robots-Tag checker on the preview URL to confirm the header is absent.
- For a static site: open the service in the Render Dashboard, find the Headers section, add a rule for path "/*" with name "X-Robots-Tag" and value "noindex".
- For a web service: gate the header in application code on the IS_PULL_REQUEST environment variable being the string "true", so previews get noindex and production does not.
- Redeploy the preview and run the checker again on the preview URL.
- Run the checker on a production URL too, to confirm production is still clean.
- If a preview URL is already in Google, request removal in Search Console after the header is live; previews are destroyed on merge, which clears them eventually on its own.
Why it happens again
Preview environments are created fresh for every pull request and destroyed on merge, so the population of indexable preview URLs is never the same twice and each one starts indexable by default. The static-site header rule survives, but a new web service blueprint is a new code path that needs the IS_PULL_REQUEST branch written again.
stillindexed re-checks the URLs you give it every 30 minutes on Starter and alerts when a directive changes, at most 30 minutes after it does. It is a monitor rather than a crawler: it watches a list you choose and tells you when one of seven things changes. Start with a 30-day free trial, 3 sites, no card required, and a 30 day refund after that.
Catching it next time
Fixing it once is the easy half. The setting that caused this can be changed again by anyone with access, and the page will keep returning 200 while it happens.
A staging or preview site indexed by Google, on other platforms
How Search Console reports it
Sources
Every claim about Render above is from their own documentation, read on 2026-10-25. Platforms change their settings; if one of these is out of date, their page wins and we would like to know.