-
Notifications
You must be signed in to change notification settings - Fork 914
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
Set up search console verification #2616
Comments
Yeah, having |
File is live at https://docs.kedro.org/en/stable/googlebce3ad2fda582ae8.html as per gh-2631, hopefully this can be closed? |
@astrojuanlu it's not working :( So the file needs to be at docs.kedro.org/google..... and because of the way the RTD folder structure is set up, obviously isn't (it's in the en/stable subdirectory). I set up a redirect in RTD but that doesn't seem to be working (https://docs.kedro.org/googlebce3ad2fda582ae8.html is returning page not found). Please can you advise? Is there a way I can fake the location? |
Merghhhh too bad. I see there are other verification methods available: https://support.google.com/webmasters/answer/9008080?hl=en#choose_method Maybe we can try HTML Meta tags or using the existing GA tracking code? |
I guess I should revert the commit that added the file for completeness. Will do that now and close this. |
xref gh-2674 Do you still intend to explore the other methods? (Otherwise let's indeed keep the issue closed) |
I'm trying to add a verification file to the docs so that I can use search console on the docs to see what query strings are bringing users to our pages.
Have been following this https://stackoverflow.com/questions/27748396/using-google-analytics-in-readthedocs-org
docs/source
and updatedconf.py
html
folderI think this is because
source
is in the exclusion list inconf.py
and wondered if you have any thoughts @astrojuanlu on whether I can put the verification elsewhere and then move it into the root, or get around the exclusion list somehow?Here's my branch
PS: I'm mindful that RTD does give us comprehensive search analytics so this is a nice-to-have rather than essential, but it'll sit well side by side with the analytics we're getting for kedro.org and the blog.
The text was updated successfully, but these errors were encountered: