Page URL resolves without redirectingWhat it checks and how to fix it

What it checks

Requests each audited page URL without following redirects, retrying with GET when the server rejects HEAD. Passes on a 2xx response, fails when the URL redirects (3xx), returns 404 or 410, or returns a 5xx server error, and warns on any other status.

Why it matters

The URLs you link to, list in your sitemap and declare as canonical should answer directly. A URL that redirects costs every visitor and crawler an extra round trip, and search engines read a redirecting sitemap or canonical URL as a mixed signal about which URL to index. A 404 or a server error on a page you promote means visitors and crawlers hit an error.

How to fix it

See where the URL goes:

curl -sI https://example.com/some-page

• 3xx: update the links, sitemap entries and canonical tags that use this URL to the final URL in the Location header. A common cause is a trailing-slash mismatch (/pricing vs /pricing/): pick one form and generate every link with it.
• 404 or 410: restore the page, or remove it from your links and sitemap and add a 301 redirect to its closest replacement.
• 5xx: check your application and server logs for the error behind it.

In Rails, build links and sitemap entries with route helpers (pricing_url) rather than hand-written paths, so they always match the routes the app actually serves.