Make robots.txt a static file again and remove dynamic route - #1968
Merged
Conversation
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
1 participant
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.
#1961 introduced an updated
robots.txtfile that included improvements for AI and agent readiness. Instead of a static text file inpublicit changed it to a controller handled dynamic route. The result is that when you visit https://statamic.dev/robots.txt you actually see the contents but looking at the request it returns a 404 status code. Reason is the nginx config and it having some rules in place for files such as robots.txt (happens locally with Herd too). This PR removes the dynamic route and controller and puts back the static but updatedrobots.txtfile which includes all the AI/agent stuff.