-
Notifications
You must be signed in to change notification settings - Fork 909
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
Control excessive Kedro versions in search results #2980
Comments
This has bothered me for a while too, and I did restrict some of the older versions in RTD for that reason, but figured the flyout needed to show most, if not all, recent versions. I like the idea of modifying |
I'm going to suggest we put this in the coming sprint as a task for engineering (maybe @SajidAlamQB ?) but it's not a high priority if we need to push it over to the next. |
Starting point: the automatically generated |
We will need to guide @tynandebold and @SajidAlamQB on which versions we want to index and which we want to hide. Do we want to be fairly proscriptive and have just these indexed:
Or be a bit more generous and index these:
|
I think we may as well be quite strict but it does depend how familiar people are with the flyout at the bottom left, if they want more versions. Can we change the RTD settings so the docs always load with the flyout open? |
Or maybe instead of
|
Sounds reasonable, probably more useful than just going with the initial versions of each major release. Let's do it! |
I've changed my mind, and think we should now update robots.txt to just allow these for search indexing:
All the versions are still on the RTD site and accessible. Just not indexed for SERP presentation. |
Description
Sometimes when I search content from the Kedro docs, too many versions appear:
Context
Ideally, only one version (the latest one) should be shown.
Possible Implementation
Read the Docs allows you to hide a version from search engines https://docs.readthedocs.io/en/stable/guides/deprecating-content.html#deprecating-versions however, doing so also hides the version from the flyout menu.
Possible Alternatives
Alternatively, we can create our own
robots.txt
file https://docs.readthedocs.io/en/stable/guides/technical-docs-seo-guide.html#use-a-robots-txt-file that disallows certain versions from search engines while leaving the flyout menu untouched. This would need a bit of maintenance over time.cc @stichbury
The text was updated successfully, but these errors were encountered: