sitemap: the new /welcome routes are not excluded like the other journey pages #122
Etiketter
Inga etiketter
area/backups
area/ci
area/control-panel
area/identity
area/infra
area/observability
area/payments
area/security
area/storage
area/web
blocked
needs-info
needs-triage
ready-for-implementation
type
bug
type
chore
type
docs
type
epic
type
feature
type
task
wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
Inga beroenden satta
Referens
bitborg/bitborg-web#122
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "%!s()"
Borttagning av en gren är permanent. Även om den borttagna grenen kan fortsätta existera en kort tid innan den faktiskt tas bort, kan det INTE ångras i de flesta fall. Vill du fortsätta?
astro.config.mjsfilters journey and gated routes out of the sitemap —/signup,/account,/auth/*— but the two routes added for the sign-up journey were not added to that list./welcomeand/en/welcomeare public, static and harmless to index, so nothing breaks. But they are journey pages, meaningless out of context: a search result landing someone on "Start using Bitborg — sign in to finish setting up" with no account and no idea what preceded it is a poor entry point, and it competes with the pages we do want indexed.Fix
Add both routes to the existing sitemap filter, following whatever pattern
/signupuses there.Done when
Neither
/welcomenor/en/welcomeappears in the generated sitemap.Already done — shipped by
8439fa4(PR #125), whose body listed this issue but whose close keywords never fired.Verified: the sitemap filter at `astro.config.mjs:120` excludes it —
`!//(signup|account|welcome)/?$/.test(page)` — and the live sitemap confirms it:
`curl https://www.gitborg.se/sitemap-0.xml | grep -c welcome` returns `0`.
Closing as already implemented; no code change was needed.