-
Notifications
You must be signed in to change notification settings - Fork 6
chore: block robots.txt on all mfes, idas, and edxapp #300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
deborahgu
merged 2 commits into
master
from
dkaplan1/APER-4252_block-robots.txt-on-all-mfes,-idas,-and-edxapp
Dec 8, 2025
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Setting a default is fine, but this is currently overridden by stage, prod, and edge ansible vars, so it won't do anything. Stage and edge already have this disallow-all rule in effect. What we would need to change is prod: https://github.com/edx/edx-internal/blob/a7701a2f1415cef320e1cb50714dda60bbbd3c51/ansible/vars/prod-edx.yml#L280
However, Robert pointed out some previous work that raises a question of whether we're ready for this step: edx/edx-arch-experiments#852 (comment)
The LMS has had a noindex meta tag in place for over a year so we're probably fine to go ahead with a robots.txt change, but I'd want to check with SEO first and and I'm not sure what the status is of the other sites.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This default will also apply to the MFEs and IDAs, though, right? It's not just going to touch edxapp? Only a few of them have overrides. We want this rule to apply everywhere.
The plan is to make any necessary the
edx-internalchanges after this is approved and merged.The request comes from SEO and leadership (and legal), and should apply to all sites. None of the sites we'll be whitelisting are controlled in this stack (eg. marketing and support).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I honestly have no idea. I don't think very many things currently use edx/configuration -- I only know about edxapp and some analytics stuff. I thought MFEs are all already on k8s, and wouldn't be affected by this.
So you'd set this default and then remove the prod (and stage and edge) overrides?
I'm fine with this merging, just wanted to check if you were aware that it wouldn't do anything by itself (and that the noindex thing might be an issue).