fix: remove invalid context-specific headers from netlify.toml#17749
Merged
Conversation
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.
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
[[context.*.headers]]blocks fromnetlify.toml— this syntax is not supported by Netlify for scoping headers per deploy contextIS_PRODUCTION_DEPLOY) still work correctlyTest plan