A 301 redirect is a permanent redirect from an old URL to a new URL. As a result, visitors and search engines both end up at the new address automatically. Only use a 301 when the move really is permanent, not as a temporary stopgap.
Short answer: what is a 301 redirect?
A 301 redirect is a permanent redirect from an old URL to a new URL. When someone visits the old URL, the server automatically sends them on. The same goes for search engines.
Think of it as the notice on a shop that has moved: the old door doesn’t just say “we’ve moved” but sends you straight to the new address.
How does a 301 redirect work technically?
A 301 redirect works through an HTTP status code. That’s the response a server sends back as soon as someone requests a URL. In this case, the server is effectively saying: this page isn’t here any more, use this new location from now on.
The browser follows that signal and opens the new URL. Search engines read the same signal and understand that the old URL has been replaced permanently. That keeps old and new addresses logically connected.
Giacomo Perticara puts it sharply: “We don’t build pages, we build logic.”
What does the browser see, and what does the search engine see?
For a visitor, a 301 redirect often feels simple. You click an old link and land on the right new page. The browser handles that almost instantly.
To a search engine, it’s more than convenience. A 301 is a clear signal: this old URL should be replaced by the new URL in the index, as far as that makes sense within the rest of your site. If you send mixed signals here, for example a redirect to page A and a canonical to page B, you’re making things unnecessarily unclear.
When do you use a 301 redirect?
Use a 301 redirect when a URL changes for good and a logical alternative exists. Think of situations such as:
- you change a URL structure
- you merge two pages into one stronger page
- you move content to a new URL
- you move to a new domain
- you switch pages from http to https
- you delete a page, but you do have a suitable replacement for its content
This is about a well-thought-out structure. Not every old URL automatically deserves a redirect. The question is always: where would a visitor and a search engine both expect to end up?
When should you not use a 301 redirect?
Not every deleted page needs a redirect. If there’s no relevant replacement page, a 404 or 410 can make more sense.
That matters. Sending everything to the homepage looks tidy, but it’s often messy. Someone looking for a specific product page who lands on the homepage doesn’t get what they expected. It isn’t a strong signal for search engines either.
Only redirect if the new destination fits in terms of content. If there’s no such match, not redirecting is sometimes the better choice.
301 vs 302 redirect: what’s the difference?
The difference is simple:
- a 301 redirect is permanent
- a 302 redirect is temporary
So choose based on what you plan to do with the old URL. If the old URL isn’t coming back, use a 301. If that page will return later, a 302 makes more sense.
The code is technical, but the choice is mostly practical.
Decision rule: is the old URL coming back or not?
The shortest decision rule is this: is the old URL coming back, or not?
- Yes, the old URL is coming back: you’ll usually want a 302 redirect.
- No, the old URL isn’t coming back: you’ll usually want a 301 redirect.
Not sure? Then “temporary” isn’t automatically safer. A wrong 302 can actually cause confusion if the move is in fact permanent.
What does a 301 redirect do for SEO?
A properly set up 301 redirect helps search engines understand that content has moved. That supports your site’s internal logic, helps with indexing and stops old URLs from being left floating around.
That means a redirect simply belongs in technical SEO and a clear site structure. Even if you look more broadly at AI visibility, the same foundation applies: clear signals beat noise.
Giacomo Perticara puts it this way: “It is still SEO. Only the priorities have shifted.”
Why the relevance of the destination page matters
A redirect’s destination has to fit the content it replaces. If you redirect an old blog post about technical audits to a general services page, that soon feels forced.
A better approach: old content about topic X goes to the best new page about topic X. Not a perfect match? Then a redirect sometimes isn’t feasible, and the more honest choice is a 404 or 410.
So sending everything to the homepage usually isn’t a good solution. That moves the problem rather than solving it.
Common 301 redirect mistakes
Many mistakes come from a lack of structure. Here’s what you’ll often see:
- redirect chains, where URL A goes to B first and only then to C
- redirect loops, where URLs keep pointing to each other
- a canonical tag that says something different from the redirect
- old URLs still listed in the sitemap
- irrelevant destination pages, such as mass redirects to the homepage
- redirects that weren’t tested after go-live
Preventing redirect chains and loops
Prevention is better than cure here, so use this mini checklist:
- point old URLs straight to the final destination
- avoid intermediate steps when they aren’t needed
- check that pages don’t point back to each other
- update internal links to the new URL right away
- test after go-live that the status code really is 301
A clean redirect goes to the new URL in one step.
How to set up a 301 redirect
How you set up a 301 redirect depends on your website and your level of access. The route differs, but the logic stays the same: old URL out, new URL in, choose a permanent redirect.
Via the server or .htaccess
If you’re working in an Apache environment, you can often set up a 301 redirect at server level through .htaccess. That’s a practical route if you have technical access and want to decide exactly which URL goes where.
Watch out for typos here, though. One wrong line can affect more than just that one page.
In WordPress or via a plugin
In WordPress, you can often manage redirects through a plugin. That’s handy if you don’t want to edit server files. For simple URL changes, this is often the most accessible route.
Just make sure several plugins or settings don’t all step in at once. The same applies here: one clear rule beats overlap.
Via hosting panel or CMS
Some hosting environments and CMSs have a built-in redirect feature. That’s especially useful if you don’t have server access but still want to redirect URLs.
There too, explicitly choose a permanent redirect if the move is permanent. Choosing temporary “to be on the safe side” usually isn’t a good idea.
Testing and monitoring 301 redirects
A redirect isn’t finished until you’ve checked it.
Checking remains necessary, especially after migrations, a content clean-up or a change in URL structure.
What to check after a redirect
After setting it up, check at least the following:
- does the old URL really return status code 301?
- does the redirect land on the correct new URL?
- do internal links already point to the new URL?
- is only the new URL in the sitemap?
- is Search Console free of unexpected indexing or error signals?
If you want a better grasp of the basics behind checks like these, also read more about technical SEO.
Redirect, canonical tag and sitemap: what’s the difference?
A redirect, a canonical tag and a sitemap don’t do the same thing.
- A redirect sends visitors and search engines on to another URL.
- A canonical tag indicates which URL is the preferred version.
- A sitemap shows which URLs you actively want counted as important pages.
These signals work best when they support each other. That’s why 301 redirects belong to the logic of your whole site.
Which solution fits which problem?
Use this as a rule of thumb:
- page moved for good: 301 redirect
- several similar pages, but one preferred version: canonical tag
- submitting current, indexable URLs: sitemap
Practical example: from old to new URL without a mess
Say you have an old URL about a service, but the content has been rewritten and now sits at a new, clearer address. In that case you publish the new page first, then redirect the old URL with a 301.
That keeps things clean: no duplicate pages, no loose ends, no unclear route. It fits an approach where you decide on the structure first and only then set up the redirects.
Step-by-step plan for a clean move
Work in this order:
- publish the new URL
- put a 301 redirect on the old URL
- update internal links
- update the sitemap
- check the canonical tag
- test that everything redirects correctly
If you want to go deeper into the basics of topics like these, SEO basics is a logical starting point.
Frequently asked questions about 301 redirects
What is a 301 redirect?
A 301 redirect is a permanent redirect from an old URL to a new URL. Visitors and search engines are sent on automatically.
When do you use a 301 redirect?
When a page has moved or been replaced for good. For example, with a URL change, a content merge or a domain migration.
What’s the difference between a 301 and a 302 redirect?
A 301 is permanent. A 302 is temporary. Only choose a 302 if the old URL really is coming back.
Is a 301 redirect good for SEO?
Yes, if it’s set up logically. It helps search engines understand the move. The content of the destination page does have to fit, though.
Should you always leave a 301 redirect in place?
In many cases, yes, as long as old links might still be out there or people might still visit the old URL. Removing it too soon can still cause error messages.
What if there’s no good replacement page?
Then a 301 redirect isn’t always the right choice. A 404 or 410 can make more sense, depending on the situation.
Conclusion
Use a 301 redirect when a URL moves permanently. Only use a 302 if the old URL is coming back. And if there’s no logical alternative, having no redirect is sometimes more honest than having a bad one.
Our order of priority is simple: first decide whether the move is permanent, then choose the right destination page, and only then set it up and test it. After that, you can take a broader view, for example of what redirects and other technical signals mean for your AI visibility.
Want to know whether your redirects make sense or mostly just move the mess around? Then now’s the time to take a critical look at your URL structure.
