Open nickpistone opened 9 months ago
Need to coordinate request with USAGov WebOps to enforce Spanish redirects to /es/
path
Do you need anything from me on this @scottqueen-bixal?
It's unclear that this is an issue with any redirects we set up on the initial move from v1 -> v2
these were all the url's we redirected
Current |
New |
---|---|
https://benefits-tool.usa.gov | usa.gov/benefit-finder |
https://benefits-tool.usa.gov/death-of-a-loved-one | usa.gov/benefit-finder/death |
https://benefits-tool.usa.gov/disability | usa.gov/benefit-finder/disability |
https://benefits-tool.usa.gov/retirement | usa.gov/benefit-finder/retirement |
https://benefits-tool.usa.gov/es | http://usa.gov/es/buscador-beneficios |
https://benefits-tool.usa.gov/es/death-of-a-loved-one | http://usa.gov/es/buscador-beneficios/muerte |
https://benefits-tool.usa.gov/es/retirement | http://usa.gov/es/buscador-beneficios/jubilacion |
https://benefits-tool.usa.gov/es/disability | http://usa.gov/es/buscador-beneficios/discapacidad |
these were all the url's we redirected
It's likely that the url is a static link in the cms that points to our application, but hasn't included the es
prefix
@nickpistone do the new redirects look correct on your end?
The 404s are still there. But they're not being linked to from anywhere on the site. So if everyone is ok with that, then we can move on. Otherwise we could add a redirect from the old versions of the URLs (without "/es") to the new versions (with "/es").
Description
Old versions of the URLs for the Spanish pages did not contain /es/ and now they do. But those pages are not redirected anywhere so in the case that someone found them like the ahrefs tool did, they would hit a 404. We can add redirects to the versions with "/es/" to solve this issue.
Example: redirect https://www.usa.gov/buscador-beneficios/discapacidad to https://www.usa.gov/es/buscador-beneficios/discapacidad
User Story
1027
Acceptance Criteria
No response