Technical SEO

Redirects (301, 302, 307, 308)

Server instructions that send users and crawlers from one URL to another.

The Definition

A redirect tells browsers and search engines that a URL has moved. 301 and 308 are permanent; 302 and 307 are temporary (307 and 308 also keep the request method). Google can also follow meta refresh and JavaScript redirects, but server-side redirects are the most reliable.

Why It Matters

A permanent redirect passes the old URL's signals to the new one and tells Google which URL to index. Redirect chains slow crawling (Googlebot follows up to 10 hops), loops break pages entirely, and temporary redirects left in place can keep the old URL in the index.

Best Practices

  • Use 301 (or 308) when a page has moved for good

  • Redirect each old URL to its closest equivalent, not the homepage

  • Keep redirects to a single hop; update chains to point straight at the final URL

  • Update internal links to the new URL instead of relying on the redirect

  • Keep redirects in place for at least a year after a migration

Mistakes to Avoid

  • 1

    Using 302 for a permanent move

  • 2

    Building chains during repeated migrations (A to B to C to D)

  • 3

    Creating loops between HTTP/HTTPS or www/non-www versions

  • 4

    Deleting redirects too soon after a site move

Audit Checks

How Digispot AI identifies and fixes related issues

View all redirects (301, 302, 307, 308) solutions
high

This URL redirects round in a circle and never lands on a real page.

Impact: A looping URL can't be crawled or indexed, and visitors hit a browser error.

Trace the redirect rules for this URL. • Point it at a single final destination that returns 200. • Re-crawl to confirm the loop is gone.

medium

This URL bounces through several redirects before reaching the final page.

Impact: Each hop adds delay and leaks ranking signal; long chains can make crawlers give up.

Redirect the starting URL straight to the final destination in one hop. • Update internal links to point at the final URL directly. • Re-crawl to confirm a single redirect remains.

medium

A "next/previous" pagination link points to a page that redirects or errors instead of loading normally.

Impact: Broken pagination wastes crawl budget and can leave deeper pages undiscovered.

Point rel=next/prev links at live, working pages. • Remove stale pagination links. • Re-crawl to confirm.

critical

The page could not be fetched at all — the request never returned a usable document (redirect loop, timeout, DNS failure, or refused connection).

Impact: Visitors and search engines hit the same dead end: the page can't be read, indexed, or ranked, and any links pointing at it are wasted.

Open the URL in a browser and confirm the failure (e.g. "too many redirects" or a timeout). • Fix the server, DNS, or redirect rule responsible so the URL returns a healthy 200. • Re-run the audit to confirm the page is reachable again.

critical

We could not read this page's content properly — the HTML may be broken or the page returned an error mid-load.

Impact: If our crawler cannot read the page, search engines likely struggle with it too, so it may not rank.

Open the page and confirm it loads fully without errors. • Validate the HTML for unclosed tags or broken markup. • Re-run the audit once the page loads cleanly.

high

The page shows an "not found"-style error message but still returns a success (200) status code.

Impact: Google keeps crawling and may index these empty pages, wasting crawl budget and cluttering results.

Return a real 404 (or 410) status for pages that no longer exist. • Redirect to a relevant live page if there is one. • Avoid showing error text on a 200 page.