Info Technical SEO
Redirecting URL
- Severity
- Info
- Impact
- Low
- Effort to fix
- Low
- Issue code
redirect
Why it matters
This internal URL redirects. Each redirect adds latency and spends crawl budget.
How to fix it
Update internal links so they point directly to the final destination.
What this means
The URL returned a 3xx redirect instead of a page. The evidence shows the status and the target, for example 301 to https://example.com/new-page. This is an Info notice: redirects are normal and often correct.
When a redirect is fine
- An old URL redirecting to its new address after a move.
- HTTP redirecting to HTTPS, or the non-www host to the www host.
- A deleted page redirecting to its closest replacement.
When it needs attention
- Your own pages link to it. Internal links should point to the final URL. See Links to redirecting internal URLs.
- It is in the XML sitemap. Sitemaps should list final URLs only. See Non-200 URL in XML sitemap.
- It redirects again. See Redirect chain and Redirect loop.
- It is temporary but permanent in practice. A 302 or 307 used for a move that will not be undone should be a 301 or 308.
- It has no target. "(no Location header)" in the evidence means the server sent a redirect status without saying where to.
Status codes
| Status | Type |
|---|---|
| 301, 308 | Permanent: search engines move signals to the target |
| 302, 307 | Temporary: the original URL usually stays indexed |
| 303 | After a form submission; rarely relevant for SEO |
Verify
Nothing to do if the redirect is intended and nothing on your site links to it. After updating links and sitemaps, recrawl: the redirecting URL is then only reached by outside links, which is exactly what the redirect is for.
How it affects your score
Info notices never lower any score. They are listed so you can confirm the behaviour is intended. A note for review. It never lowers the score.
Find the affected URLs
Open Crawl > Issues and pick Redirecting URL. Each affected URL is listed with its evidence, and Copy URLs or Export URLs hands the list to a developer. The issue also appears in the Action Plan, ranked by impact (low) and effort (low), and in the issues CSV under the code redirect. After fixing, run a new audit and use Compare to confirm the URLs moved to fixed.