Skip to content

Authenticate jsha to use Google Search Console #1768

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

Closed
wants to merge 1 commit into from

Conversation

jsha
Copy link
Contributor

@jsha jsha commented Jul 14, 2022

This allows troubleshooting issues with why Google doesn't crawl docs.rs deeply enough.

Related to #1438 (comment)

Per https://support.google.com/webmasters/answer/9128668?visit_id=637926083810327397-791277710&rd=2:

Search Console offers tools and reports for the following actions:

  • Confirm that Google can find and crawl your site.
  • Fix indexing problems and request re-indexing of new or updated content.
  • View Google Search traffic data for your site: how often your site appears in
  • Google Search, which search queries show your site, how often searchers click through for those queries, and more.
  • Receive alerts when Google encounters indexing, spam, or other issues on your site.
  • Show you which sites link to your website.
  • Troubleshoot issues for AMP, mobile usability, and other Search features.

Per https://support.google.com/webmasters/answer/7687615#manage-owners&zippy=%2Cadd-or-remove-verified-owners, removing this handler later will deauthenticate me.

Here's an example of the sort of report I'll be able to get from Google Search Console:

image

This allows troubleshooting issues with why Google doesn't crawl docs.rs
deeply enough.
@github-actions github-actions bot added the S-waiting-on-review Status: This pull request has been implemented and needs to be reviewed label Jul 14, 2022
Copy link
Member

@jyn514 jyn514 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is fine.

@pietroalbini do you have strong opinions about giving @jsha access to the Google webmaster console? They're not on the docs.rs team but they are on rustdoc, and have a history of contributions. Plus I don't think there's terribly much you can do there other than tell Google not to crawl the site.

@@ -21,6 +21,10 @@ pub(super) fn build_routes() -> Routes {
// https://developers.google.com/search/reference/robots_txt#handling-http-result-codes
// https://support.google.com/webmasters/answer/183668?hl=en
routes.static_resource("/robots.txt", PermanentRedirect("/-/static/robots.txt"));
routes.static_resource(
"/googleb54494ba4d52c200.html",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where does this string come from? I clicked on the "verification flow" link in the webmaster docs, but didn't see anything that looked relevant.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you visit https://search.google.com/search-console/welcome from a logged-in Google Account, and click the "URL Prefix" box, enter "https://docs.rs", and hit "continue," you'll get a similar string.

@pietroalbini
Copy link
Member

I have no problem with giving them access to the webmaster console, but we should do it by having the infrastructure team setup the account and then granting jsha access to it, rather than having jsha setup their own account linked to docs.rs. I'll add that to my todo list.

@jyn514 jyn514 closed this Jul 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: This pull request has been implemented and needs to be reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants