Page redirects to another URL
What it is
The URL listed for this page redirects to a different URL, and the finding shows where it ends up. A redirect is the right tool when a page moves, but a URL your sitemap or menus still list should be the final address, not a stop on the way to it.
Why it matters
Each redirect costs visitors and crawlers an extra request, and chains of them add up. Google treats a permanent redirect as a signal that the target should be the indexed URL; a temporary one is not such a signal, so the old address can stay in search results. A sitemap that lists redirecting URLs also muddies which address you want indexed.
How Asky checks it
Asky requests the URL, follows redirects (301, 302, 303, 307, 308) to the end of the chain, and compares the final URL with the listed one. A redirect that only adds or removes a trailing slash, switches between http and https, or adds or drops www. is recorded but not reported; any other change of host, path or query is. When the final URL is another audited page (in your sitemap, or the homepage), this URL carries only this finding; otherwise the final URL’s findings appear here, or just its 4xx or 5xx status. Meta refresh and JavaScript redirects are not followed. Links to this URL are reported as links to internal redirects.
Reported as a warning with medium severity.
How to fix it
- Open the finding to see the final URL, and decide which address should be the real one.
- If the final URL is right, list it in your sitemap in place of the old one, and point menus and internal links straight at it. Keep the redirect itself for bookmarks and links from other sites.
- If the move is permanent, make sure the redirect answers 301 or 308, not 302 or 307.
- If the redirect is a mistake, such as a rule that catches the wrong pattern or sends a live page to the homepage, remove it so the URL answers 200.
- For a chain, point every old URL straight at the final one.
- To leave it as it is: if the listed URL is meant to redirect, such as a language picker that sends visitors to their localized page, mark the issue resolved.
Example
The sitemap of https://example.com still lists last year’s URL of an article:
curl -sI https://example.com/blog/pricing-guide-2025 | grep -i -E "^(HTTP|location)"
# HTTP/2 301
# location: https://example.com/blog/pricing-guideList https://example.com/blog/pricing-guide in the sitemap instead, and keep the redirect.