
301 Redirects and SEO: When to Use Them, 301 vs 302, and What They Can't Fix
How 301 redirects affect SEO: what Google does with a 301 vs a 302, when each one fits, how long to keep them, and the redirect mistakes that cost rankings.
November 9, 2026 · 11 min read
A 301 redirect tells browsers and search engines that a URL has moved for good. For SEO, that matters because Google uses it as a strong hint about which URL to keep in its index. Done right, a 301 moves a page's rankings to its new address. Done wrong (pointing to the wrong page, chaining through several hops, or removed too early), a page can quietly lose its traffic after a URL change.
Here is the short version:
- Use a 301 (or 308) when a page has moved permanently and you won't move it back.
- Use a 302 (or 307) only when the move really is temporary and you want the original URL to stay in search results.
- Redirect each old URL to its closest equivalent, in one hop, and leave the redirect in place for at least a year.
The rest of this guide explains why each of those rules exists, with Google's own wording, and how to check that your redirects are doing what you think.
What a 301 Redirect Actually Tells Google
A 301 response says "moved permanently." When Googlebot requests the old URL and gets a 301, it follows the Location header to the new URL and processes that page instead. Google's documentation on how HTTP status codes affect its crawlers puts it this way: for a 301, "Google systems use the redirect as a strong signal that the redirect target should be processed."
The key word is signal. A redirect doesn't force Google's hand. It is one input into canonicalization, the process where Google picks one URL to represent a group of duplicate or near-duplicate pages. Google's redirects guide says that "Google Search uses certain types of redirects as a signal that the redirect target should be canonical." Other signals, such as canonical tags, internal links, and sitemap entries, can agree or disagree with it. When they all point at the new URL, the switch is quick and clean. When they conflict, Google may take longer or pick a different URL than you wanted.
That is why a redirect works best alongside the other signals. Point the new page's canonical tag at itself (our guide to the self-referencing canonical tag shows what that looks like), list only the new URL in your sitemap, and update internal links so they point straight at the new address.
Do 301 redirects hurt SEO?
Not by themselves. Google's site move guide says that 301 and other permanent redirects "don't cause a loss in PageRank." What hurts is how redirects get used: sending pages to irrelevant destinations, building chains, or adding redirects that conflict with canonical tags. Each of those is covered below. If you want the background on how ranking value flows between pages in the first place, our post on link equity covers it.
301 vs 302: Which Redirect Should You Use?
The difference is about intent, and Google treats them differently in search results.
- Permanent (301, 308): Google shows the new URL in search results. The redirect is used as a canonical signal.
- Temporary (302, 303, 307): Google keeps showing the original URL. In Google's words, "Googlebot follows the redirect, but the indexing pipeline doesn't use the redirect as a signal."
Google's crawler documentation is direct about this: a 302 is a "weak signal" where a 301 is a "strong" one, a 307 is "equivalent to 302," and a 308 is "equivalent to 301." So a 308 is a fine choice for a permanent move; it behaves the same as a 301 for Google. Our own site uses it, for example: requesting http://trafficmonitor.app/ returns a 308 to the https:// version, and a URL with a trailing slash returns a 308 to the same path without one. Both are single, permanent hops.
The guidance on choosing is simple. From the redirects guide: "Use permanent redirects when you're sure that the redirect won't be reverted," and "If you just want to send users to a different page temporarily, use a temporary redirect."
In practice, a 302 fits cases like these:
- A product page that's out of stock for two weeks and sends visitors to a category page in the meantime.
- A seasonal landing page that redirects to a holding page off-season and comes back next year.
- A short A/B test that sends some visitors to a variant URL.
For almost everything else on a blog (renamed slugs, merged posts, a new folder structure, HTTP to HTTPS, an old domain to a new one), the move is permanent and a 301 or 308 is correct.
What happens if you use a 302 for a permanent move?
It isn't a disaster, but it slows things down. Because Google treats a 302 as temporary, it keeps the old URL in search results for longer. The redirects guide notes that one URL will end up canonical and that "which one, depends on signals such as whether the redirect was temporary or permanent." If the other signals all point at the new URL, Google may eventually choose it anyway. But you're asking it to guess. If a move is permanent, say so with a 301.
What about meta refresh and JavaScript redirects?
If you can't set server-side redirects (some hosted blog platforms don't allow it), Google lists fallbacks in order of how reliably it can interpret them. An instant meta refresh (0 seconds) is treated as permanent, and a delayed one is treated as temporary. JavaScript redirects come last: Google says to "only use JavaScript redirects if you can't do server-side or meta refresh redirects," because if rendering fails, Google may never see the redirect at all.
When to Use 301 Redirects on a Blog
These are the situations where a blog needs a 301:
- You changed a post's slug. Redirect the old slug to the new one. It is easy to forget, because many CMSs let you edit a slug without warning you that the old URL will break.
- You merged two thin posts into one. Redirect the weaker post to the combined one. Google's site move guide allows this: if content was consolidated, "you can redirect the older URLs to that new, consolidated page."
- You restructured URLs. Moving from
/2024/05/post-nameto/blog/post-name, or adding category folders, means every old URL needs a redirect. - You moved to HTTPS or a new domain. Every URL on the old version should redirect to its matching URL on the new one, not just the homepage.
- You redesigned the site. A redesign only needs redirects if URLs change, but they often do. Our website redesign SEO guide covers what else to check on launch day, and the website migration SEO checklist covers the full process for a URL or domain change, including Search Console's Change of Address tool.
When you delete a post with no good replacement, a 301 isn't the right tool. Let the URL return a 404 or 410. Redirecting it somewhere unrelated just to "keep the link equity" usually backfires, as the next section explains.
Redirect Mistakes That Cost Rankings
Each of these can cost a page its rankings after a URL change, and each has a simple fix.
Redirecting everything to the homepage. It is a tempting shortcut during a migration or cleanup, and Google's site move guide warns against it directly: "Don't redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site." The reason given is that it "can confuse users and might be treated as a soft 404 error." A soft 404 means Google treats the redirect as if the page were simply gone, so you get none of the benefit. If you see a cluster of old URLs reported this way, our guide to soft 404 errors in Search Console explains how to confirm it. The fix is a proper redirect map: each old URL points to the page that best replaces it.
Redirect chains. A chain happens when URL A redirects to B, which redirects to C. It can build up over time: you change a slug, then move to HTTPS, then change the slug again. Google's crawlers will follow up to 10 hops by default, but the site move guide advises "redirecting to the final destination directly," and if that isn't possible, keeping the chain "ideally no more than 3 and fewer than 5." Chains also slow visitors down. Our redirect chain checker guide shows how to find chains and flatten them so every old URL goes straight to the final page.
Removing redirects too soon. Redirects are easy to treat as temporary clutter. Google says otherwise: "Keep the redirects for as long as possible, generally at least 1 year." It adds that from users' perspective, you should "consider keeping redirects indefinitely," since old links on other sites and in bookmarks keep working. On a blog, the cost of keeping a redirect is close to zero, so there's rarely a reason to delete one.
Conflicting signals. A redirect from A to B, combined with a sitemap that still lists A, internal links that still point to A, or a canonical tag on B that points back to A, sends Google mixed messages. Search Console reports the old URL as Page with redirect, which is normal for a redirected URL. It becomes a problem when the new URL isn't getting indexed. Clean up the sitemap (see sitemap best practices) and update internal links so the only path to the old URL is through old external links.
Leaving internal links pointing at old URLs. Every internal link that goes through a redirect adds a hop for visitors and crawlers. After any URL change, search your posts for the old path and update the links. An internal linking audit catches these in bulk.
How to Check Your Redirects Are Working
You don't need special tools for a basic check. For any old URL, look at the response headers. From a terminal:
curl -sI https://example.com/old-post
You want to see a 301 or 308 status and a Location header that points to the final URL. Then request that final URL and confirm it returns 200. If the second request returns another redirect, you have a chain.
In Search Console, three places tell you whether Google has caught up:
- URL Inspection on the new URL. Check that it's indexed and that the Google-selected canonical is the new URL, not the old one.
- Pages report. Old URLs moving into "Page with redirect" is expected. New URLs appearing under "Duplicate" or "Alternate page" reasons may mean the signals are conflicting. Our post on alternate page with proper canonical tag explains how to read that status.
- Performance report, filtered by page. Compare clicks and impressions for the old URL before the change with the new URL after it. Google's site move guide says to expect temporary ranking fluctuation, and for a small site most pages can take a few weeks to move. A drop that is still there after several weeks deserves a closer look. The Search Console performance report guide covers how to compare two date ranges without misreading the numbers.
That last check is easy to skip, because it means coming back to the same report week after week. Traffic Monitor connects to Search Console with read-only access and shows clicks and impressions for every post, updated daily, so you can see whether a redirected post has picked up its old traffic or is still missing it. You can connect your site for free.
301 Redirect SEO Checklist
Before you change a URL:
- Decide whether the move is permanent. If yes, use a 301 or 308.
- Pick the closest matching destination for each old URL. Never default to the homepage.
- Write the redirect map down, one old URL and one new URL per line.
After the change:
- Request a few old URLs and confirm one hop to a
200. - Update internal links, the sitemap, and the new page's canonical tag to the new URL.
- Inspect the new URL in Search Console and check the selected canonical.
- Compare the page's clicks before and after over the next few weeks.
- Leave the redirects in place for at least a year, ideally for good.
Related posts
How to Add a User to Google Search Console (And Which Permission to Give)
How to add a user to Google Search Console, which level to pick (Owner, Full, or Restricted), the per-property limits, and how to remove access safely.
SEO Chrome Extensions for Bloggers: 6 Free Ones Worth Installing (And What Each Can't See)
The free SEO Chrome extensions a blogger actually needs, matched to one job each, plus the one Google retired and what no extension can tell you.
Track your blog rankings automatically
Connect Google Search Console and get daily alerts, keyword research, and AI diagnostics — free to start.
Start free →