fix: prevent dev/staging subdomains from being indexed by search engines#17748
Merged
Conversation
Use NEXT_PUBLIC_CONTEXT (already inlined at build time via next.config.js) instead of parsing SITE_URL hostname. This ensures IS_PRODUCTION_DEPLOY is false on all non-production deploys (branch deploys, deploy previews), closing the canonical URL leak for arbitrary branch deploys where SITE_URL would fall through to "https://ethereum.org".
Move the SITE_URL fallback chain (NEXT_PUBLIC_SITE_URL → DEPLOY_PRIME_URL → DEPLOY_URL → URL) into next.config.js env config so it gets resolved at build time and inlined by webpack. This ensures SSR pages on deploy previews and branch deploys use the correct deploy-specific URL instead of falling through to "https://ethereum.org".
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
config ⚙️
Netlify does not support `[[context.*.headers]]` syntax in netlify.toml. Headers cannot be scoped per deploy context directly. Removing the broken X-Robots-Tag header blocks — the remaining SEO protections (robots.txt disallow and noindex meta tags) still work correctly.
wackerow
approved these changes
Mar 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Cherry-pick of #17741 (merged into dev) into staging.
NEXT_PUBLIC_SITE_URLper branch so canonical URLs and noindex meta tags resolve correctly at build timeIS_PRODUCTION_DEPLOYfrom deploy context instead of URL hostname checkSITE_URLat build time vianext.config.jsso deploy previews get correct URLsTest plan
staging.ethereum.orgpages have<meta name="robots" content="noindex, nofollow">staging.ethereum.orgcanonical URLs point tostaging.ethereum.org, notethereum.orgethereum.org(production) is unaffected