Skip to content

Conversation

@its-miroma
Copy link
Member

@its-miroma its-miroma commented Jan 1, 2026

this is certainly very buggy still. it also is probably pretty bad for SEO.

JS-based redirect seems to work fine, but meta-tag (which is the one that's acceptable for SEO) is not working at all. the main problem is that I cannot obtain the original path that caused a 404, which means I cannot set up a redirect like this.

I implemented the following redirects for now:

  • remove all file extensions (should be already getting done by default)
  • remove index as it's implied (again, done by default)
  • redirect all URLs to lowercase
  • redirect hyphened locales to underscores (it-it -> it_it)
  • redirect item-groups to creative-tabs as an example

TODO:

  • fix meta-tag implementation
  • redirect "it" to "it_it"
    • must be careful with el_gr, ja_jp, ko_kr, ms_my, pt_br, uk_ua, vi_vn, zh_cn / zh_tw
  • change references to "Item Groups" to "Creative Tabs"

@its-miroma its-miroma added the framework Related to the VitePress framework label Jan 1, 2026
@netlify
Copy link

netlify bot commented Jan 1, 2026

Deploy Preview for nimble-elf-d9d491 failed.

Name Link
🔨 Latest commit 7b955cc
🔍 Latest deploy log https://app.netlify.com/projects/nimble-elf-d9d491/deploys/695adfe649c22600088d27a1

NOTE: meta redirects don't work currently because
the `currentUrl` is always `/404`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

framework Related to the VitePress framework

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant