Pegasus: set noindex meta tag properly for a bunch of pages #27982
Conversation
This file contains 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
Erin007
approved these changes
Apr 11, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Properly set the
"noindex"meta tag for a bunch of pages that we'd apparently attempted to hide from indexing previously:https://code.org/educate/professional-learning/facilitator-2019
https://code.org/educate/regional-partner/playbook
https://code.org/educate/regional-partner/playbook/FAQ
https://code.org/educate/regional-partner/playbook/administrator
https://code.org/educate/regional-partner/playbook/advocacy
https://code.org/educate/regional-partner/playbook/communications
https://code.org/educate/regional-partner/playbook/community
https://code.org/educate/regional-partner/playbook/curriculum
https://code.org/educate/regional-partner/playbook/data
https://code.org/educate/regional-partner/playbook/directory
https://code.org/educate/regional-partner/playbook/facilitator-support
https://code.org/educate/regional-partner/playbook/funding
https://code.org/educate/regional-partner/playbook/legacy
https://code.org/educate/regional-partner/playbook/ordering-supplies
https://code.org/educate/regional-partner/playbook/payments
https://code.org/educate/regional-partner/playbook/reporting-and-evaluations
https://code.org/educate/regional-partner/playbook/summit
https://code.org/educate/regional-partner/playbook/teacher-recruitment
https://code.org/educate/regional-partner/playbook/timeline
https://code.org/educate/regional-partner/playbook/training-materials
This is a belated followup to #20662