SEO

301 Redirects: When to Use Them, When to Use a 302, and How to Set One Up on Your Platform

Most guides to 301 redirects explain the code well and then give a one-line menu path for each website builder. The details that break redirects in real life sit in the builders' own help pages: limits, which pages can be redirected at all, and defaults that quietly make a redirect temporary. This guide covers when to use each code, then what Webflow, Wix, Squarespace, Shopify, WordPress and Cloudflare Pages say about their own redirects, read on 15 November 2026.

301 Redirects: When to Use Them, When to Use a 302, and How to Set One Up on Your Platform

Key takeaways

  • A 301 says a page has moved for good. Google uses it as a strong signal that the new address should be the one shown in search. A 302 is a weak signal, and the old address may stay in the results.
  • 301 and 308 are treated the same by Google, and so are 302 and 307. Google's crawler documentation says so, and asks you to use the code that matches what you mean.
  • Redirect to the closest match, not the home page. Google says sending many old URLs to one irrelevant page may be treated as a soft 404. With no good match, a 404 or 410 is the honest answer.
  • Each platform has its own limits. Wix allows 5,000 redirects per site, Squarespace about 2,500 lines, Cloudflare Pages 2,100 rules in its file, and Shopify 100,000 outside the Plus plan.
  • On several builders the old page must be gone first. Shopify and Squarespace only redirect addresses that no longer load, and Webflow asks you to delete, draft or rename the page before adding the rule.
  • Cloudflare Pages defaults to 302. A line in its redirects file with no code is temporary. Write 301 at the end of every permanent rule.

The short answer

A 301 redirect is a server response that tells browsers and search engines a page has moved permanently to a new address. Use it when you change a page's URL, merge two pages, delete a page that has a real replacement, or move to a new domain. Use a 302 when the move is temporary and you want the old address to keep its place in search, such as a seasonal page. Set it up in your platform's redirect screen, point each old address straight at its final new one, keep the rules for at least a year, and test each one after publishing.

About us: Amariq designs, builds and moves websites on Webflow, Framer, WordPress, Shopify, Wix, Squarespace and static hosting. amariq.com itself runs on Cloudflare Pages with its redirects in a plain text file. Every platform rule below comes from the maker's own help page, read on 15 November 2026.

What ranks for this search, and what is missing

We searched Google (US, English) for "301 redirect" on 15 November 2026. The top results were MDN's reference page, Google's own redirects documentation, Wikipedia, Semrush's guide (18 February 2026), Webflow's blog (21 April 2025) and a Stack Overflow thread from 14 years ago. Google's AI summary said a 301 passes "roughly 90% to 100%" of a page's ranking power and cited Moz.

Semrush's guide is good on when to redirect and gives a menu path for eight platforms. None of the results says that most builders will not redirect a page that still exists, what each one's limit is, or that Cloudflare Pages makes a rule temporary unless you say otherwise.

The "90% to 100%" figure is not in Google's documentation. Google's pages describe a 301 as a strong signal for the new address, with no percentage. We left the number out.

What 301, 302, 307 and 308 mean to Google

Google's documentation on HTTP status codes, read on 15 November 2026, groups the redirect codes like this:

CodeMeaningHow Google treats itUse it when
301Moved permanentlyStrong signal that the new address is the one to keepA page or site has moved and will not move back
308Moved permanentlySame as 301Same as 301; some hosts send it for trailing slash changes
302FoundWeak signal; the old address may stay in searchA short, planned absence, such as a seasonal page
307Temporary redirectSame as 302Same as 302
Meta refresh, 0 secondsPage-level redirectRead as permanentYour platform gives you no server redirect
Meta refresh, delayedPage-level redirectRead as temporaryRarely the right choice
JavaScript redirectScript in the pageOnly seen if Google renders the pageLast resort, per Google

Google's redirects page lists these in order of how likely Google is to read them correctly, with a server-side redirect first. Its crawler documentation also notes that Google's crawlers follow up to 10 redirect hops, and that the URL Inspection tools do not follow redirects at all. That last point catches people out: inspecting an old address in Search Console shows the redirect, not the page it leads to.

When to use a 301, and when not to

SituationWhat to do
You changed a page's URL301 from the old address to the new one
You merged two pages on the same topic301 the weaker page to the one you kept
You deleted a page that has a close replacement301 to the replacement
You deleted a page with no replacementLet it return 404 or 410; do not send it to the home page
You moved to a new domain301 every old address to the matching new address
Your site answers on both www and non-www, or http and https301 every version to the one you chose
A page is away for a season and will return302, then remove it when the page is back
You are testing two versions of a pageA 302, not a 301

The home page mistake is the most common. Squarespace's own help page gives "redirect a deleted page to your homepage" as an example of a 301. Google's site move guidance says the opposite: do not redirect many old URLs to one irrelevant page, because it may be treated as a soft 404. If a deleted page has no real match, a proper 404 page that helps people find their way is the better answer.

How to set up a 301 on each platform

Every row below comes from the maker's own help page, read on 15 November 2026.

PlatformWhereLimitRules that catch people out
WebflowSite settings, Publishing, 301 redirectsNo hard limit; Webflow suggests 1,000 at mostNeeds a paid plan. Delete, draft or rename the old page first. Rules run oldest first, so add specific rules before wildcards
WixSEO and GEO dashboard, Tools and settings, URL Redirect Manager5,000 per siteNeeds a connected custom domain. Changing a page slug adds a redirect for you, but not for blog posts. The home page cannot be redirected here
SquarespaceDeveloper tools panel, URL mappings400 KB, about 2,500 linesOld page must be deleted or disabled. You type the code at the end of each line. Images and files cannot be redirected. Rules run top to bottom
ShopifyContent, Menus, View URL Redirects100,000; 20,000,000 on PlusRedirects only fire on addresses that show Page not found. Some paths, such as /cart and /apps, cannot be redirected
WordPressNo redirect screen of its own; most sites use a pluginSet by the pluginThe free Redirection plugin (2+ million active installs) can add a redirect when you change a permalink, and can write rules to .htaccess or Nginx
Cloudflare PagesA plain text file called _redirects2,000 static plus 100 dynamicA line with no code is a 302. Rules in _redirects do not apply to Pages Functions routes

Webflow

Enter the old path, such as /old-url, and the new path, click Add redirect path and publish. When you change a slug in Page settings, a box lets Webflow add the redirect for you. Folders use capture groups: /oldfolder/(.*) goes to /newfolder/%1. Localized folders need their own rule, so /es/old-url is a separate line, and characters such as ?, = and & in the old path must be escaped with %. Our WordPress to Webflow migration guide shows a full redirect map for a platform move.

Wix

In URL Redirect Manager, click New Redirect and choose a single redirect, or a group redirect for pages that share a path. Wix adds a redirect itself when you change the slug of most pages, including products and bookings services, but not blog posts. A deleted redirect cannot be recovered.

Squarespace

Each line in URL mappings has four parts: the old address, an arrow (a dash and a greater than sign), the new address, and 301 or 302, as in /about -> /team 301. A [name] variable moves a whole blog: /blog/[name] -> /posts/[name] 301. Match the capital letters of your real URLs. If the same redirect is hit twice within two minutes, Squarespace shows a 404 as a guard against loops, which can look like a broken rule while you test.

Shopify

Redirects start working at once, but only on addresses that are broken. If a product still exists, set it to Draft or remove it from sales channels first. One rule also covers market subfolders such as /en-ca. Shopify warns that browsers cache 301s, so a removed redirect may keep working for people who already used it.

WordPress

The free Redirection plugin, listed on WordPress.org with over 2 million active installations, adds the missing screen: old address, new address, done. It can add redirects when a permalink changes and logs 404 errors, which shows which old addresses still get visits. For a one-off rule on Apache, Google's documentation gives Redirect permanent "/old" "https://example.com/new".

Cloudflare Pages and other static hosts

Each line in _redirects is the old path, the new path and the code: /pricing /contact 301. The code defaults to 302, so write 301 every time. Past 2,100 rules, Cloudflare points to its Bulk Redirects feature. When two rules match, the higher one wins.

What we found when we checked our own redirects

We ran a header check (curl with the -I flag) on amariq.com on 15 November 2026 to see what a browser and a crawler actually receive:

RequestWhat came backHops
https://www.amariq.com/pricing301 to /contact, then 2001
https://amariq.com/blogs/website-backup301 to www, then 2001
https://www.amariq.com/blogs/website-backup.html308 to the address without .html, then 2001
http://amariq.com/blogs/website-backup301 to https, 301 to www, then 2002

Two lessons came out of it. First, some redirects come from the host, not from your rules: Cloudflare Pages sent a 308 for the .html version on its own. Google treats 308 like 301, so that is fine. Second, an old http link to a bare domain usually passes through two hops, one for https and one for www. Google follows up to 10, and its site move guidance asks you to keep chains short. Two is short. Five, built up over three redesigns, is the kind of chain to fix.

How to test a redirect

  1. Open the old address in a private window. You should land on the new page, with the new address in the bar.
  2. Check the code. In a terminal, curl -I followed by the old address shows the status line and the Location header. Free online header checkers do the same. You want 301 or 308, not 302, for a permanent move.
  3. Count the hops. curl -IL follows the whole path. Every old address should reach a 200 page in one hop where you can manage it.
  4. Update your own links. Point menus, buttons and internal links at the new address, so visitors and crawlers skip the redirect. Remove redirected addresses from your XML sitemap.
  5. Watch Search Console for a few weeks. Its page indexing report lists the addresses Google sees as redirects or as not found.

Mistakes that undo a redirect

  • A chain of old rules. Page A redirects to B, which redirects to C. Point A straight at C.
  • A loop. A redirects to B and B back to A. Browsers show a "too many redirects" error.
  • Temporary by accident. A 302 left in place for years, often from a host default or a plugin setting.
  • A rule that never fires. On Shopify and Squarespace, the old page still exists, so the redirect is ignored.
  • Removing redirects too soon. Google's guidance says to keep them for at least a year, and from the user's point of view, to consider keeping them for good. Links on other sites and in old emails do not update themselves.
  • Blocking the old address in robots.txt. A crawler that cannot fetch the old URL never sees the redirect. Our robots.txt guide covers what to leave open.

Moving a whole site? Our website redesign SEO checklist walks through the redirect map, launch day and the 90 days after.

How Amariq can help

Every rebuild or platform move we take on starts with the redirect map: each old address that earns visits or links, where it goes, and a test of every rule after launch. When we moved amariq.com off Webflow in September 2026, we kept every old blog address and wrote a rule for each page that changed. Projects are priced from scope, never by the hour, and paid 40% at the start, 30% when the design is approved and 30% before launch. Once the final payment is made, the design, copy and code belong to you, and the domain and hosting accounts sit in your name. See our Webflow migration service or book a call.

Frequently asked questions

What is a 301 redirect?

A 301 is the server response for "moved permanently". It sends visitors and search engines from an old address to a new one, and tells Google the new address is the one to keep in its results.

What is the difference between a 301 and a 302 redirect?

A 301 is permanent and a 302 is temporary. Google uses a 301 as a strong signal to show the new address, and a 302 as a weak one, so the old address may stay in search. Use a 302 only when the page is coming back.

Should I use a 301 or a 308?

Google treats them the same, so either works for a permanent move. Some hosts send a 308 on their own, for example when they drop .html or a trailing slash. Most builders only offer 301 and 302, which is fine.

Do 301 redirects hurt SEO?

Not when each one points to a close match. Google's documentation describes a 301 as a strong signal for the new address. What hurts is redirecting pages to unrelated ones, long chains, and loops.

How long should I keep a 301 redirect?

Google's site move guidance says generally at least one year, and suggests keeping them indefinitely for the sake of visitors. Old links on other sites, in emails and on printed material keep working only while the rule exists.

Why is my 301 redirect not working?

Check, in order: the old page still exists; the old path has a typo or different capital letters; a broader rule higher in the list catches it first; your browser cached an earlier rule; or, on Cloudflare Pages, the route is served by a Function, where _redirects does not apply.

Rahat Khondokar, founder of Amariq

Rahat Khondokar

Founder & CEO, Amariq

Rahat designs and builds websites for marketing teams and ecommerce brands, and writes here about the structure, copy and conversion work behind them. More about Amariq. Find him on YouTube, Dribbble and LinkedIn.

Keep reading

Related articles.

All articles

How Long Does DNS Propagation Really Take? What Decides the Wait, and a Launch-Day Plan That Keeps It Short
Web Design·8 November 2026

How Long Does DNS Propagation Really Take?

DNS propagation is cache expiry, set by TTL, not a fixed 48 hours. A launch-day plan to lower TTL, switch safely and check. Sources checked 8 Nov 2026.