Repository navigation
Add search engine verification tags to the docs - #307
Merged
Merged
Conversation
Google Search Console and Bing Webmaster Tools both verify a URL-prefix site by looking for a meta tag on the home page. The tokens go in mkdocs.yml and the theme override writes them into the head.
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.
This puts the Google Search Console and Bing Webmaster Tools ownership tags in the head of every docs page. With them in place, both services can verify the site and read the sitemap.
The two token values live in
mkdocs.ymlunderextra, andoverrides/main.htmlwrites a meta tag for each one that is set. Leave them in after verification. Both services check again later, and removing a tag drops the site out of the account.mkdocs build --strictpasses locally and the built index.html has both tags.