9 ms·

It doesn't cover everyone, but you should know about rel="canonical" (https://datatracker.ietf.org/doc/html/rfc6596 https://datatracker.ietf.org/doc/html/rfc659

It doesn't cover everyone, but you should know about rel="canonical" (https://datatracker.ietf.org/doc/html/rfc6596 https://datatracker.ietf.org/doc/html/rfc6596). For example, Amazon helpfully hints that this messy Kindle Paperwhite link (https://www.amazon.com/Kindle-Paperwhite-Signature-Essentials-including/dp/B09FNJZD68/ref=sr_1_4?crid=3H1D0BMHBNTQ0&keywords=kindle+paperwhite+2022&sprefix=kindl%2Caps%2C358&sr=8-4 https://www.amazon.com/Kindle-Paperwhite-Signature-Essential...) is actually https://www.amazon.com/Kindle-Paperwhite-Signature-Essentials-including/dp/B09FNJZD68 https://www.amazon.com/Kindle-Paperwhite-Signature-Essential.... Additionally, CleanURLs to the rescue! https://github.com/ClearURLs https://github.com/ClearURLs

karlicoss 5y ago
Yeah, sadly, to get the canonical attribute, you need to fetch the URL first (which is slow and wasteful). Also sometimes canonical would still be different on the desktop and mobile version of the site, so it still has to be normalised after that