-
Notifications
You must be signed in to change notification settings - Fork 145
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
[Docs] Add search console tag for verification #921
Conversation
View the example dashboards of the current commit live on PyCafe ☕ 🚀Updated on: 2024-12-05 11:00:55 UTC Link: vizro-core/examples/dev/ Link: vizro-core/examples/scratch_dev |
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 approved but would also be curious what this actually does?
@antonymilne So when we next do a release, this means mkdocs will build a site verification tag into google search console. The site console will trust that we own the site, and will report on the google search keywords that brought users to the vizro.readthedocs.io pages. It basically gives us some better insights into what we're ranking for (and what our users are looking for when we surface on Google and they're convinced by the metadata text to follow the link). We can match up if we're delivering in the docs what the user looked for and, if not, plan to improve it. Sadly, we can't use google analytics since that keeps track of users across the site and there are various European GDPR implications. But search console is safe since it's search data that is kept by google, not tracked by us. |
Oh nice, that sounds great. I look forward to hearing what we learn from this tracking 👍 |
Description
As part of ticket 1377 on the internal repo.
Adding
CYb3cxosCgsN2QDQVaSGQpMQCesqpsGQ3oTM02NtvkY
as our tag to enable readthedocs to add it to our hosted docs for verification by Google search console.Screenshot
Notice
I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":