-
Notifications
You must be signed in to change notification settings - Fork 11
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
Google SEO #257
Comments
@mmann1123 do you want to get this in now, or do you want to review #252? |
@jgrss Happy to review 252 without this. Although it looks like CI tests are failing. |
I am going to assume that you want ownership of this. Unless I am told otherwise- since its associated with a particular google account. In particular if you can get the site registered:
I can help with the google analytics side of thing. |
Where is the Google HTML verification file supposed to live? |
and check to make sure
Then you need to sort out the A. To do this properly it requires you to generate a sitemap.xml and host it along side the website in the root directory.
B. Once the sitemap is published to the web, open
C. Go to google search console again. Hit the |
Steps 1-3 are done in #262. |
@jgrss can we close this? |
oops accidentally closed |
We should strongly consider including the google analytics SEO and sitemap. These should make the site much easier to find through search engines. Plus you can obsessively check how many people are looking at the site at any given moment.
I am not sure how much of this has been done, but I will walk you through it just in case:
- This can be generated with https://pypi.org/project/sphinx-sitemap/ although since you are publishing through CI (i think), I am not entirely sure how CI would push the sitemap.xml to your hosting service
- Search console will confirm things once it finds sitemap.xml, just make sure it has all your pages listed.
- Whenever you add a new page to your docs you need to create a new sitemap.xml to get it crawled.
I am happy to help just let me know.
The text was updated successfully, but these errors were encountered: