4 hours lost to a trailing slash: what shipping multilingual SEO actually looks like
A developer shares how a tiny mismatch in URL trailing slashes derailed multilingual SEO for a 6-language tool site.
Stock photo for illustration only, not from the actual event
- A 6-language tool site faced an issue where Chinese pages merged into the English version on Google.
- The root cause was a mismatch between canonical URLs with trailing slashes and sitemap entries without them.
- It took a full 4 hours of staring at rendered HTML to track down and fix the bug.
- The developer plans to implement a build-time check to prevent future canonical discrepancies.
Building a multi-language browser-based tool site sounds straightforward on paper, but for solo developers handling everything manually, managing multilingual SEO often comes with unexpected hurdles. Small syntax details like a trailing slash can unexpectedly break search engine indexing.
The first warning sign appeared when Chinese pages failed to show up as independent URLs in Google Search Console, getting merged with their English counterparts instead. While the English version ranked normally, the Chinese version vanished completely.
Stock photo for illustration only, not from the actual event
Inspecting the source of a Chinese tool page showed that the canonical URL correctly pointed to the Chinese version featuring a trailing slash, matching Next.js's default behavior. However, the submitted sitemap entry lacked the trailing slash. Cloudflare silently rewrote URLs in the background, leading Google to conclude that the sitemap version did not exist and default to indexing the English page.
Once the rendered page, canonical tag, and sitemap entries were fully aligned, the Search Console error count dropped to zero within approximately three days.
From a technical standpoint, multilingual SEO frequently trips up over strict URL normalization rules. Search engines treat URLs with and without trailing slashes as distinct pages, which can easily trigger duplicate content penalties if not handled uniformly. Edge proxies like Cloudflare must be configured carefully to avoid rewriting URLs in a way that contradicts declared canonical tags.
The site runner is currently cleaning up remaining pages flagged for duplicate content warnings, aiming to introduce a build-time check that fails deployment if any canonical URL disagrees with the sitemap. If successful, the script will be open-sourced for the community.
Source: Dev.to
Found something wrong in this article? Report an issue with this article
Comments
Leave a Comment