Check redirects and sitemaps before a website release
Use a small release checklist to catch missing pages, self-redirects and stale sitemap entries.
Identify the published source
A repository can contain multiple versions of a website. Confirm which directory the deployment actually publishes before fixing a route. A page in an application source folder will not appear in an artifact assembled only from a static public folder. Inspect the generated artifact as part of the release check.
- Record the deployed commit and artifact preparation command.
- Check that each repaired URL has an output file.
- Preserve the existing navigation and contact destinations.
Follow the destination
Check HTTP redirects and page-level refresh directives. Track every destination and stop when a URL repeats. Verify the final page contains the expected content rather than a generic error document. For retired URLs, use the intended current destination and make the relationship clear to visitors.
- Test trailing-slash variants when they are supported.
- Confirm canonical links agree with the intended destination.
- Provide a visible navigation link when automatic redirection is used.
Keep discovery consistent
A sitemap should describe pages intended for discovery. When an old URL becomes a noindex alias, remove its entry from the published sitemap. Keep unrelated entries intact and validate the resulting XML. Repeat the checks on the live domain after deployment, since a local artifact alone does not establish publication.
- Verify that the old URL no longer appears in the sitemap.
- Check the replacement destination directly.
- Save the deployment and live validation evidence together.