301 redirects migrate a URL’s backlinks, PageRank, and anchor text to the destination on the next crawl cycle. 302 may not consolidate signals. Chains of 3 or more hops degrade equity per hop and waste crawl budget resolving old paths instead of indexing new content.
What a Redirect Actually Does
When a user or Googlebot requests a URL, the server returns an HTTP status code before any page content loads. A redirect code in the 3xx range instructs the client to go to a different URL instead. This happens at the network layer, before the browser renders anything.
For SEO, the status code you choose is a direct instruction to Google about authority transfer. When Google receives a 301, it migrates the old URL’s indexed signals, including backlinks, PageRank, and anchor text, to the destination URL during the next crawl cycle. Choose the wrong code and that migration either stalls or never happens.
Redirect Types and What Each One Signals
Not all redirects are equal. The table below shows the types you will encounter in real work, what each signals to Google, and when to use it.
| Code | Name | Permanent or Temporary | Link Equity Transfer | Common Use Case |
|---|---|---|---|---|
| 301 | Moved Permanently | Permanent | Strong | Page or domain moved for good |
| 302 | Found (Moved Temporarily) | Temporary | Partial, may not consolidate | A/B tests, short-term page swaps |
| 307 | Temporary Redirect | Temporary | Partial | Temporary move, method preserved |
| 308 | Permanent Redirect | Permanent | Strong | Same as 301, method preserved |
| Meta Refresh | Client-side delay | Varies | Weak | Avoid for SEO purposes |
The 301 is the default choice for any permanent URL change. The 302 has its place for genuinely temporary situations, but left in place for months, Google may never fully migrate ranking signals to the destination URL.
The 307 and 308 codes matter in specific technical contexts. Both preserve the HTTP method of the original request, meaning a POST request stays a POST rather than being reissued as a GET. You will encounter 307 most often on modern HTTP/2 stacks handling form submissions or API calls, and 308 as the permanent equivalent in the same scenarios. For standard page redirects in SEO work, 301 remains the correct choice.
Google has stated publicly that the gap between 301 and 302 for canonicalization purposes has shrunk in recent years. That does not mean they are interchangeable. A 301 remains the clearest, most unambiguous instruction you can give Google for a permanent move.
Redirect Chains and Link Equity Decay
A redirect chain occurs when URL A redirects to URL B, which redirects to URL C. Each hop adds latency and introduces the possibility that Googlebot stops following the chain before reaching the final destination. Chains also consume crawl budget disproportionately: on sites with large blog archives or product catalogs that have moved through two or more CMS platforms, Googlebot can spend a significant portion of each crawl session resolving old chain paths rather than discovering new content.
Collapsing chains to a single direct redirect from the original URL to the final destination is consistently the fix that surfaces the most stalled pages in the first recrawl cycle. It solves an equity problem and a crawl budget problem at the same time.
A redirect audit we ran on a Phoenix-area home services site found 340 redirect chains with 3 or more hops, almost all tracing back to a 2021 redesign whose redirect file was copied wholesale into a later migration without being updated. After collapsing all chains to single direct 301s and removing 47 redirects that pointed to the homepage for deleted pages with no real replacement, pages that had stalled re-entered the top 20 for several target terms within about five weeks. The crawl logs confirmed Googlebot had been spending measurable session time resolving those chains rather than indexing new content — making this simultaneously a link equity fix and a crawl efficiency fix.
How chains build up. Each redesign team typically adds a new redirect layer without collapsing the previous one. A site through two or three redesigns carries all of those layers simultaneously. Audit tools like Screaming Frog or Sitebulb surface these chains so you can collapse them to direct hops.
Redirect loops. Conflicting htaccess rules and CMS-level redirect plugins most often create loops, where URL A redirects to URL B, which redirects back to URL A. That collision returns an error to both users and crawlers. Test key URLs with a header-checking tool or curl immediately after any migration to catch loops before they compound.
When to Use a Redirect
Redirects are not only for site migrations. Here are the most common legitimate scenarios:
Permanent page moves. You restructure URL slugs or move a blog post to a new category path. Any URL that has earned backlinks or organic traffic needs a 301 to carry that history forward.
Domain changes. A rebrand moves you from one domain to another. Every page on the old domain should map to its closest equivalent on the new one with a 301.
HTTP to HTTPS migration. Any HTTP URLs still receiving traffic need permanent redirects to their HTTPS versions. One common mistake here produces a chain: HTTP redirects to the www version, which then redirects to HTTPS. That is two hops where one would do.
Consolidating duplicate URLs. If the same content is accessible at multiple URLs, such as with and without trailing slashes or with and without “www”, pick one canonical version and redirect the others permanently.
Removing a page with no replacement. When no relevant page exists to redirect to, a 410 status code is cleaner than a 301 pointing to your homepage. A 410 tells Google the resource is permanently gone, and Google removes it from the index faster than a 404. A 410 is not a redirect and does not transfer any equity to another URL.
Pro Tip: Never redirect a deleted page to your homepage as a catch-all unless that page had zero meaningful backlinks. A homepage redirect from an unrelated old URL sends a confusing topical signal, and Google frequently treats it as a soft 404, ignoring the redirect entirely.
JavaScript Redirects and Indexing Delays
Server-side redirects appear in the HTTP response headers, so Googlebot sees the destination URL the instant it makes the request. JavaScript redirects work differently.
When a redirect runs via JavaScript (window.location assignment, React Router navigation, or similar client-side routing), Googlebot must first download the page, queue it for rendering in its JavaScript engine, and then discover the new URL. That rendering step can delay indexing by days to weeks depending on crawl queue depth, compared to a server-side redirect that resolves before any HTML loads.
The result: a page that should be indexed at its new URL may continue to appear in Google Search at the old address for a prolonged period, or may never cleanly consolidate ranking signals at all.
Use server-side redirects wherever your stack allows. If your site is a single-page application using client-side routing, configure your server or CDN to return a 301 at the HTTP layer before the JavaScript ever runs.
Pro Tip: If you manage a WordPress site, plugins like Redirection or Yoast SEO write server-side redirects, not JavaScript ones. Confirm this by opening browser DevTools, going to the Network tab, and requesting the old URL — you should see a 301 response before any HTML loads. You can also run
curl -I https://yoursite.com/old-urlin a terminal and look forHTTP/1.1 301as the first line.
404 vs. 410 vs. Redirect: Choosing the Right Response
404 Not Found tells Google the resource does not exist right now but might return. Google keeps 404 pages in its crawl queue and rechecks them periodically.
410 Gone tells Google the resource is permanently removed. Google deprioritizes recrawling 410 pages and clears them from the index more quickly. Use this when content is gone with no meaningful replacement and you want the fastest possible removal from search results.
301 Redirect tells Google to permanently transfer all signals from the old URL to a new one. Use this when a relevant destination page exists.
Redirecting to an unrelated page, or routing all deleted pages to the homepage, provides so little topical relevance that Google often classifies those as soft 404s anyway — making the redirect accomplish nothing.
Site Migration Redirect Strategy
Site migrations are where redirect errors cause the most measurable ranking damage. The steps below combine pre-launch preparation with post-launch monitoring into a single workflow.
Rankings typically fluctuate for 3 to 6 weeks after a migration even when redirects are implemented correctly. A sustained drop beyond 6 to 8 weeks signals missing redirects on high-value pages, not a reason to make broad content changes.
Before the migration begins, running through a small business SEO checklist will surface technical issues beyond redirects that could compound ranking loss if left unaddressed.
Common Redirect Mistakes on Small Business Sites
These errors show up consistently on sites that have been through one or more redesigns.
Redirecting every deleted page to the homepage. Developers reach for this as a fast fix, but Google recognizes the pattern and classifies those as soft 404s, making the redirect pointless.
Stacking redirect rules from multiple sources. When a WordPress plugin manages some redirects and an htaccess file manages others, conflicting rules for the same URL create chains or loops. Consolidate redirect management to one layer and audit both when something breaks.
Forgetting image and asset URLs. A migration that changes the media folder path can break image URLs that other sites have embedded or linked. Run your crawl tool against non-HTML resource types too, not just pages.
Carrying old redirect rules forward. Developers often copy the previous site’s htaccess redirect block into the new server config. On a new URL structure, those old rules produce loops or unintended chains. Review every inherited redirect rule against the new site architecture before launch.
The broader list of common small business website mistakes covers additional technical and content issues that drain organic traffic alongside redirect problems.
How Redirects Fit Into Your Broader Local SEO Strategy
When a redesign breaks URLs that local directories, chamber of commerce pages, or local news outlets link to, those backlinks are gone until each source manually updates its link. That rarely happens. A missed redirect on a high-authority local citation surrenders years of earned authority permanently, which is why redirect coverage matters more for local service businesses than the raw page count might suggest.
Redirects are a technical foundation, not a standalone tactic. A clean redirect structure lets Google crawl and index your correct pages efficiently, which supports everything built on top: content relevance, backlink equity, and local signals. The technical side of local SEO for service businesses depends on this foundation being solid before any other optimization produces reliable results.
Pro Tip: After any site redesign, pull your backlink report from Google Search Console and check whether the top 20 linking URLs still return a 200 on your new site. Any that return a 404 or redirect to the homepage represent recoverable authority you can reclaim with a targeted redirect fix.
What We See Running Campaigns
The redirect problem we find most often during technical audits is not a missing redirect on a recent migration. Site owners typically handle the obvious ones. The deeper issue is redirect chains inherited from redesigns two or three cycles back, layered silently under the current site with nobody tracking them.
On the Phoenix-area home services site described in the chains section above, the crawl logs told the clearest part of the story: Googlebot was burning crawl session time on chain resolution rather than discovering the new content the client had been publishing for months. Fixing the redirect structure did not just recover stalled rankings — it freed up crawl capacity that started producing indexing improvements on content that had been invisible for the same period.
If rankings have never fully returned after a domain change or redesign, a redirect audit is the right first move — before new content, before link building, before anything else.
DMD Digital
Frequently asked questions
Do 301 redirects pass full link equity?
Google has said the difference between 301 and 302 for link equity has narrowed, but a single clean 301 still sends the strongest consolidation signal. Equity degrades meaningfully across chains of 3 or more hops, so keep each redirect direct.
How many redirects are too many for SEO?
On chain depth: beyond 3 to 4 hops, equity transfer becomes unreliable and Googlebot may abandon the chain before reaching the final URL. On total volume: sites carrying hundreds of unresolved redirect URLs force Googlebot to spend crawl budget resolving old paths instead of indexing new content — the two problems are related but distinct.
Will a 302 redirect hurt my rankings?
A temporary 302 left in place too long can prevent Google from fully updating its index to the new URL. If the move is permanent, switch to 301 so Google consolidates ranking signals to the destination.
What is the difference between a 404 and a 410?
A 404 tells Google the page is not found but may return. A 410 tells Google the page is permanently gone. Google removes 410 pages from its index faster, which is useful when you have deleted pages with no relevant replacement. A 410 is not a redirect and does not transfer equity.
How do JavaScript redirects affect SEO?
JavaScript redirects require Googlebot to render the page before discovering the new URL, which can delay indexing by days to weeks. Server-side redirects are visible in the HTTP response headers immediately, so use those whenever your stack allows.
Should I redirect every old URL during a site migration?
Redirect every URL that has backlinks or measurable organic traffic. Pages with zero inbound links and no organic traffic can return 404 with minimal ranking impact, but when in doubt, map and redirect. Rankings typically stabilize within 6 to 8 weeks of a clean migration.
