Old doc versions pollute search engine results
See original GitHub issueLike many developers, I typically start at Google when I am curious about a feature in Wagtail.
Usually, I get a link to an old version of the docs:
Those docs will have a link like this at the top of the page:
Because the docs change structure over time, that link frequently 404s.
In contrast, when I search for things in Django, I always see a link to the most recent docs.
It’d be nice if via robots.txt
or some other mechanism, only the most recent docs were indexed by Google.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Check or revert to earlier file versions - Google Support
View, delete, download, or revert to previous versions any time; Access any version ... View or revert to earlier versions of Docs, Sheets,...
Read more >Wayback Machine
Archive-It enables you to capture, manage and search collections of digital content without any technical expertise or hosting facilities.
Read more >Site Specific National Cleanup Databases | US EPA
A list of Multi-Program & Single Program databases with information about cleanup sites, providing brief descriptions of each database.
Read more >Federal Register :: Reader Aids :: Using FederalRegister.Gov
This site has a basic search tool and an advanced search. The basic search box appears in the main navigation at the top...
Read more >Search Operators | GovInfo
Note: In certain cases, the search engine will automatically assume that two terms separated by a single space should be treated as a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is true, also happened to me. I would say the best way to tackle it is putting a
<link rel="canonical" href="http://docs.wagtail.io/en/<last_stable_version>/<page_slug>">
in the<head>.
I will try to make a PR within this week if nobody does it before.
Have now updated our release process docs with some extra steps to ensure the canonical URLs get updated correctly. Not perfect, since there’s apparently no way to rebuild old versions that have been deactivated, but hopefully it will help…
I’ve also added a bunch of redirects based on going through all docs.wagtail.io links that have been posted on StackOverflow, and ensuring they all point to somewhere useful in the current version of the docs. I’m sure that’s not an exhaustive list, but probably the best we can do unless anyone fancies trawling through our Git history for all page moves we’ve done 😃 We’ll try to keep up the habit of adding redirects whenever we move docs in future.