Conversation

This is one of the MAJOR failings of the web, that urls are not persistent, and most web admins do not bother to setup redirects to the new location when things change.

Quote Tweet

John-Mark Gurney

@encthenet

Jun 30

Google for all it's CI/CD work can't even have tooling to verify that the URLs in it's own documentation aren't 404. Or even put in a redirect to the correct when an old url disappears.

Show this thread

Daniel Micay

@DanielMicay

Replying to

@encthenet

We take great take to do this for the GrapheneOS sites but there are serious browser limitations. We had to make github.com/GrapheneOS/gra to handle section redirects. It's a missing HTML feature. We link to a proposal which would have been a nicer way to handle these redirects.

github.com

grapheneos.org/redirect.js at main · GrapheneOS/grapheneos.org

Main website servers. Contribute to GrapheneOS/grapheneos.org development by creating an account on GitHub.

2:12 AM · Jun 30, 2022Twitter Web App

Replying to

and

Also, all of these redirects are based on people making typos: github.com/GrapheneOS/gra We were using ahrefs.com to find broken backlinks we could fix on other people's behalf although unfortunately that now requires a paid plan which is too expensive to justify.

ahrefs.com

Ahrefs - SEO Tools & Resources To Grow Your Search Traffic

You don't have to be an SEO pro to rank higher and get more traffic. Join Ahrefs – we're a powerful but easy to learn SEO toolset with a passionate community.

Replying to

I'm a little more forgiving of fragments not working as long as it takes me to the correct page, but as I see with grapheneos, you moved data off a page, and so fragment detection was necessary.

Replying to

If it's moved within the same page, it's possible to create additional elements to provide legacy anchors but we don't really want to add a bunch of those and it doesn't address moving content across pages. It's going to be very common for us to move sections between pages.

Show replies