Do redirects hurt SEO?

A single, correct 301 does not hurt SEO. It passes nearly all link equity to the new URL and is the right tool for moving a page permanently. Redirects start costing you when they chain, loop, land on a dead page, or use a 302 for a move that is actually permanent. The fix is always the same shape: redirect directly to the final, live destination.

How long does it take for a 301 redirect to pass ranking value?

It is not instant. A search engine has to recrawl the old URL, see the redirect, and process the consolidation, which plays out gradually rather than immediately, and for a large site it takes even longer to complete across every URL. Judging a migration in the first few days is the most common reason teams panic and revert a change that was actually working.

Should I redirect a deleted page to the homepage?

No. Mass-redirecting deleted pages to the homepage is frequently treated as a soft 404, in which case no equity transfers and you have gained nothing over a clean 404. Redirect each removed page to the closest relevant live page instead. If nothing on the site is genuinely relevant, let the URL return a 404 rather than forcing an irrelevant redirect.

How many redirects can a page have before it hurts SEO?

There is no hop count that is actively fine, only a number nobody has removed yet. One direct redirect is the target. Search engines follow several hops in practice, so a two-step chain is unlikely to be catastrophic on its own, but every additional hop adds latency, wastes crawl budget, and risks the chain breaking later if one link in it starts returning an error.

Do redirects need to be updated in internal links too?

Yes. A redirect rule gets a page to its destination, but a link that still points at the old, redirecting URL wastes a hop on every crawl and every click, and it is entirely within your control to fix since you own both ends. Update internal links and navigation to point directly at the final URL, and keep the redirect only as a safety net for old bookmarks and external backlinks.

Can I use JavaScript to redirect a page for SEO?

Prefer a server-side redirect (a real 301 HTTP status) over a client-side one whenever you can. A server-side redirect is seen immediately by the crawler with no rendering required. A JavaScript or meta-refresh redirect depends on the page being rendered first, adds delay, and is why the audit flags meta-refresh redirects used in place of a 301.

Home/SEO Guide/Redirects

SEO guide · category 04 · site structure

RedirectsDoes every moved URL land in one hop?

A redirect tells browsers and search engines where a page went. Done right it carries the old URL’s signals across; done wrong it adds hops, loops or dead ends.

Last reviewed · 1 Oct 2026Reference article · 13 sources →Kalenux engineering

Check my redirects free →Broken Link Checker

http://shop.com/Sale · trace3 hops → collapse to 1

1http://shop.com/Sale301 · to https→ hop

2https://shop.com/Sale301 · to lowercase→ hop

3https://shop.com/sale301 · to trailing slash→ hop

✓https://shop.com/sale/200 · final URL✓ lands

fix: one 301 straight to the final URL · illustrative

which response to send

Two questions decide every redirect.

Before choosing a status code, answer these in order. The answer isn’t always a redirect.

ASKIs the old URL coming back?

YES: SHORT-TERM MOVE302 / 307Temporary redirectMaintenance, a seasonal detour, A/B tests. Google keeps the old URL as canonical.

ASKNo: is there a close replacement?

YES301 / 308Permanent redirectMoved, renamed or merged pages. Signals pass to the new URL.

NO404 / 410Let it goNothing equivalent exists. Don’t send people to the homepage instead.

what each hop costs

One hop is fine. Every extra hop is waste.

Each hop is another round trip before anything loads. Googlebot stops following after 10.

1 hop · target2–3 · collapse them4–9 · slow for users and crawlers10 · Googlebot stops here

Bar height is the cumulative delay before the page starts loading: each hop adds a full request. Illustrative scale.

reviewing a redirect map

Six rules, four mistakes.

A redirect map is the list of old URL → new URL rules. This is what a review of one looks like.

/2019/sale→ /offers/301correct

/about-us→ /about/301correct

/blog/old-guide→ /blog/guide/302should be 301

/products/discontinued-x→ /301soft-404 risk

/shop/boots→ /shop/boots-2301 → 301chain

/legacy/faq→ /help/faq-old301 → 404ends in 404

illustrative

how the redirect is sent

Server-side beats everything else.

Google follows all three methods, but they aren’t equal.

HTTP 301 / 308sent by the server

Seen byevery client

Speedinstant

Signal to Googlestrong

Meta refreshin the page HTML

Seen byafter HTML loads

Speedslower

Signal to Googleweaker

JavaScript redirectin page scripts

Seen byafter rendering

Speedslowest

Signal to Googlemay be missed

redirect questions, answered

What people ask before a migration.

Q1301 or 302: does it still matter?

Yes, as a signal. A 301 or 308 tells Google the move is permanent and the new URL should be canonical. A 302 or 307 says the old URL is coming back, so Google may keep showing it.

Q2How long should I keep redirects?

As long as you can. Google recommends keeping redirects from a site move for at least a year, and longer if old URLs still get links or traffic.

Q3Is a redirect chain really a problem?

Past a hop or two, yes. Googlebot follows up to 10 hops, but each one delays the page for users and crawlers. Collapsing chains to a single hop is quick and removes the risk.

Reference article · 13 sources

Every status code, from HTTP/1.0 to RFC 9110.

An HTTP redirect is a server response with a 3XX status code and a Location header that sends a browser or crawler from one URL to another. Search engines treat redirects as signals about which URL should be shown: a permanent redirect (301 or 308) strongly suggests the target is the canonical URL, while a temporary one (302 or 307) suggests the original should stay.

KALENUX REFERENCEHTTP redirects and SEO