Audit your website free →
100% free · No signup · No login

How to Check a 301 Redirect: A Simple Step by Step Guide

The only reliable way to know a page move worked is to check 301 redirect behavior from the outside, the same way a browser or Googlebot sees it. Clicking the old link and seeing the new page load is not enough to check 301 redirect quality. That quick click does not tell you which status code the server sent, how many hops it took, or whether the old URL is quietly using a temporary redirect.

We test redirects on almost every site that comes to us after a redesign or a domain move, and the same pattern keeps showing up. The redirects “work” for visitors, yet the server is sending a 302, pointing to the wrong page, or stacking three rules where one would do. None of it is visible on the screen. All of it shows up the moment you look at the response headers.

Four methods cover almost every situation, and each one takes only a few minutes once you know what to look for.

How to check 301 redirect status with a redirect checker showing old URL

What a 301 Redirect Tells Browsers and Google

Before you check 301 redirect rules on your own site, it helps to be clear on what a correct 301 actually says. A 301 is a server response, not a page. When someone requests the old URL, the server answers with the status code 301 and a “Location” header that holds the new address. The browser reads that header and requests the new URL straight away. According to MDN, a 301 Moved Permanently response means the resource has moved for good to the address in the Location header, and search engines pass ranking signals to that new URL.

Google treats permanent and temporary redirects differently. Its guide on redirects and Google Search explains that a permanent redirect (301 or 308) is a signal that the target should be the canonical URL. A temporary redirect (302, 303 or 307) is followed too, but Google does not use it as a canonical signal, which means the old URL may stay in search results.

That difference is the main reason to check 301 redirect codes instead of trusting what you see in the browser. A 302 and a 301 look exactly the same to a visitor. Only the status code tells them apart, and you can only see that code when you check 301 redirect responses with a proper tool.

Signs You Need to Check 301 Redirect Rules Right Now

In our experience, most redirect problems are found by accident, usually weeks after the damage started. A few situations should always trigger a check, even if nothing seems broken yet.

You recently moved pages or changed URLs. Any permalink change, category rename or page merge creates new redirects. Check 301 redirect rules for each one the same day it goes live.

You switched to HTTPS or changed your domain. These moves affect every URL on the site at once. A small mistake in one rule can send thousands of pages through an extra hop or to the wrong place, which is why you should check 301 redirect paths for a sample of pages from every section of the site.

Search Console shows “Page with redirect”. This label in the Page indexing report is normal for URLs you redirected on purpose. It becomes a warning sign when pages you expect to rank appear in that list, and it is a good moment to check 301 redirect targets for those pages.

Old rankings dropped after a migration. When traffic from old URLs does not move over to the new ones, wrong redirect codes and wrong destinations are among the first things to rule out. Check 301 redirect codes for the pages that lost the most traffic first.

A plugin, theme or host was changed. Redirects often live inside plugins and hosting panels. Switching any of them can remove rules or add new ones without anyone noticing, which means you should check 301 redirect behavior again after every switch.

What to Look For When You Check 301 Redirect Status

When we test a redirect, we are not only asking “does it go somewhere?” We are checking six specific things. Any method you use to check 301 redirect status, from a tool to the command line, should give you answers to all of them.

What to checkWhat a correct result looks like
Status code301 or 308 for a permanent move
Location headerPoints to the exact new URL you intended
Number of hopsOne hop from the old URL to the final page
Final statusThe destination returns 200 OK
Protocol and hostLands on your preferred https and www (or non www) version
Redirect typeServer side, not a meta refresh or JavaScript redirect

Two smaller details are worth a look as well. If your old URLs carry tracking parameters, confirm those parameters survive the redirect. And if your site uses trailing slashes, make sure the target URL already has one, otherwise the server may add a second hop to fix it.

Method 1: Check 301 Redirect Status With an Online Redirect Tester

For most people, an online tool is the fastest and most accurate way to check 301 redirect setups. It sends a fresh request every time, it ignores your browser cache, and it shows every hop in one view. We built the URL redirect checker on SiteAuditHub for exactly this job, and it is free to use without signing up.

How to test a 301 redirect with the tool

  1. Open the Redirect Checker page.
  2. Enter the old URL you want to test. If you enter your domain, the tool also tests your homepage, up to 15 internal links it finds there, and the http, https and www versions of your domain.
  3. To test specific old URLs, paste up to 20 of them in the list box, one per line. Only those URLs are checked when the list has entries.
  4. Run the check and wait a few seconds. A scan can take up to 30 seconds.
  5. Read the full redirect path for each URL, from the first request to the final page.

How to read the redirect tester results

Each URL shows its full path with the status code at every step. When you check 301 redirect results here, a healthy result has one line with 301 and one line with 200. If the tool flags a URL, it is usually for one of three reasons: three or more hops, a loop, or a destination that is dead or unreachable. Each flagged result comes with a plain English suggestion, such as pointing the old URL straight at the final page. When you are done, the CSV export gives you every checked URL with its full path and final status, which is handy to share with a developer.

Keep one limit in mind. Like most redirect testers, this one covers server side redirects. Redirects done inside the page with a meta refresh tag or a script may need a manual look at the page source.

301 redirect checker results showing each hop, its status code and the final URL
301 redirect checker results showing each hop, its status code and the final URL

Method 2: Test 301 Redirect Behavior in Chrome DevTools

When we want to check 301 redirect details for one URL, the browser’s own developer tools are often the quickest option. They show every request, every status code and every header, with nothing to install.

  1. Open Chrome and press F12 (or right click the page and choose Inspect).
  2. Go to the Network tab.
  3. Tick “Preserve log”, which keeps the redirect requests visible after the page changes.
  4. Tick “Disable cache”. This step matters more than most people think.
  5. Paste the old URL into the address bar and press Enter.
  6. Click the first row in the list. Under Headers, look at the Status Code and the Location value.

The “Disable cache” box is important because browsers remember 301 redirects very strongly. If you visited the old URL before you changed the rule, Chrome may skip the server completely and use the old answer it saved. That leads to a confusing situation where your fix is live, but your own browser keeps showing the old redirect. Ticking that box, or testing in a private window, avoids the problem.

DevTools is great for detail, but it is slow for anything more than a handful of URLs. To check 301 redirect status for a list, a url redirect checker or the command line saves a lot of time.

Method 3: Use curl to Check 301 Redirect Headers

Developers on our team reach for curl first, because it shows the raw server response with nothing hidden or cached. It works on Mac, Linux and Windows 10 or newer.

See the first response only

The command below sends one request and prints only the headers. It does not follow the redirect.

curl -I https://example.com/old-page

A correct result looks something like this:

HTTP/2 301
location: https://example.com/new-page/

This is the simplest way to check 301 redirect codes from a terminal. If the first line says 302 or 307, the redirect is temporary. If the location line points somewhere you did not expect, the rule needs updating.

See the final status and destination in one line

To test 301 redirect results quickly for a short list, this version prints the status code and the target on a single line, which is easy to copy into a spreadsheet:

curl -s -o /dev/null -w “%{http_code} %{redirect_url}\n” https://example.com/old-page

The output will read something like “301 https://example.com/new-page/”. You can then run the same command on the target URL to confirm it returns 200. Many developers save this as a small script to check 301 redirect lists before a launch. If you would rather not use a terminal, our HTTP header checker shows the same status and location headers in your browser.

Method 4: Check Redirects in Google Search Console

The first three methods check 301 redirect responses from your server. Search Console tells you what Google has actually recorded. Both views matter, and we use them together after every migration.

The Page indexing report

In Search Console, open Indexing, then Pages. Under the reasons why pages are not indexed, look for “Page with redirect”. Click it to see the URLs Google found that redirect somewhere else. Old URLs belong in this list. Your important live pages do not. If you see a page you expect to rank in that list, check 301 redirect behavior for that URL with a redirect tool to see where it is sending people.

The URL Inspection tool

You can also paste a single URL into the inspection bar at the top of Search Console. For a redirected URL, the result shows that Google sees it as a redirect. Keep in mind that Google’s documentation on HTTP status codes notes that its inspection tools do not follow redirects. To check the final page, inspect the destination URL separately.

Search Console data is not instant. Google needs to recrawl a URL before the report changes, which can take days or weeks. Use it to confirm the long term picture, not to check 301 redirect changes you made five minutes ago.

Method 5: Test 301 Redirects in Bulk After a Migration

After a site move, we never test URLs one at a time. We build a redirect map and test it in batches. It sounds like more work, but it is the only way to check 301 redirect coverage and be sure nothing was missed.

Start with a spreadsheet. List every old URL in the first column. Good sources are your old XML sitemap, an export of your top pages from Search Console or Google Analytics, and a list of URLs with backlinks. In the second column, write the new URL each one should go to.

Then add four more columns: actual status code, actual final URL, number of hops, and pass or fail. Run the old URLs through a 301 redirect checker in batches of 20, paste the results in, and mark each row. When you check 301 redirect results this way, a row passes only when the code is 301 or 308, the final URL matches your intended target, the hop count is one, and the final page returns 200.

The rows that fail usually fall into a few groups. Some point to the homepage instead of a matching page. Some go through two or three hops because older rules were never cleaned up. If you find many of those, our guide on what a redirect chain is walks through how to collapse them into one hop.

Common Problems You Will Find and How to Fix Them

Once you check 301 redirect results across a real site, the same handful of issues show up again and again. Here is what each one means and the simplest fix.

The redirect returns 302 instead of 301

Many plugins, hosting panels and CMS settings create 302 redirects by default. If the page has moved for good, open the rule and change the type to 301 (often called “Permanent”), then check 301 redirect status again to confirm the change took effect. In Rank Math, the redirect type is a dropdown on each rule.

The old URL lands on the wrong page

Usually a typo in the target or a pattern rule that catches more URLs than intended. Fix the target, then check 301 redirect paths for a few URLs that share the same pattern to make sure the rule does not affect them in a way you did not plan.

Everything goes to the homepage

This is quick to set up but weak for SEO. Google often treats a redirect to an unrelated page as a soft 404. Point each old URL to the closest matching page instead.

The final page returns 404

The redirect works, but the target is missing. Either the new page was deleted, or the target URL has a small spelling mistake. Update the rule to a live page, then run a broken link checker across the site to catch internal links that point at the same missing page.

It works in the browser but the tool shows something different

There are two common causes. The first is cache: your browser is still using an old saved 301. The second is a client side redirect, where the page itself sends visitors on with a meta refresh or JavaScript. The browser follows it, but a server level check will show a 200 on the old URL. Replace client side redirects with proper server 301s wherever you can.

Only some versions of the URL redirect

The https version redirects correctly, but the http version or the version without www goes somewhere else. Check 301 redirect behavior on all four versions of your domain for every important URL, and make sure each one reaches the same final page in a single hop.

Where 301 Redirects Usually Live

When you check 301 redirect results and a test fails, the next question is where the rule is stored. On the sites we work with, redirects tend to sit in one or more of these places, and checking each one saves a lot of guessing.

WordPress plugins. Rank Math, Yoast Premium and dedicated redirect plugins each keep their own list of rules. In Rank Math, you will find them under Rank Math, then Redirections.

Server configuration. On Apache servers, rules often sit in the .htaccess file in the site’s root folder. On Nginx, they live in the server configuration files, which usually need a developer or host to edit.

Hosting control panels. cPanel and many managed hosts have a Redirects section that writes rules for you, often as 302 by default.

CDN and DNS services. Cloudflare and similar services can redirect requests before they ever reach your server. If a redirect does not match any rule on your site, check here next.

Keeping all page level redirects in one place, usually your SEO plugin, makes it faster to check 301 redirect rules in future and avoids rules that fight each other.

A Monthly Routine to Check 301 Redirect Health

Redirects are not a one time task. New ones are added every time content changes, and old ones can break when plugins update or hosts change settings. We keep the routine short enough that it actually gets done.

Once a month, check 301 redirect status for your 20 most valuable old URLs: pages with the most backlinks and pages that used to bring the most traffic. Test your homepage in all four domain versions. Look at the “Page with redirect” list in Search Console for any page that should not be there. Then run a full site audit to catch internal links that still point at redirected URLs, because those links should be updated to the final address directly.

The whole routine takes about 20 minutes on a small site, and it catches most redirect problems before they cost you rankings.

FAQs

How can I check if a redirect is 301 or 302?

To check 301 redirect type, use a url redirect checker, Chrome DevTools or the curl command to look at the status code the server sends. The browser alone cannot tell you, because a 301 and a 302 look the same to a visitor.

Is there a free 301 redirect checker?

Yes. The SiteAuditHub Redirect Checker is free and needs no signup. It shows each hop, its status code and the final destination, and it can test up to 20 URLs at once.

Why does my browser still show the old redirect after I changed it?

Browsers cache 301 redirects. Test in a private window, tick “Disable cache” in DevTools, or check 301 redirect status with an online tool that sends a fresh request each time.

How long should I keep a 301 redirect in place?

Google does not give a fixed timeframe. Many SEOs keep redirects for at least a year, and keep them longer for URLs that still have backlinks or get traffic. Removing a redirect too early turns those old links into 404 errors.

Should I use 301 or 308?

Both are permanent and both are treated as a strong signal by Google. A 308 keeps the request method the same, which matters for forms and APIs. For normal page moves, a 301 is the common choice.

Does Google Search Console show my 301 redirects?

Indirectly. The Page indexing report lists URLs under “Page with redirect”, and URL Inspection shows when Google sees a URL as a redirect. It does not show the full path or hop count, which is why a redirect tester is still needed.

Test Your Most Important Old URLs Today

A redirect that looks fine in the browser can still be the wrong type, the wrong target or one hop too long, and none of that shows until you look at the server’s answer. The quickest fix is to check 301 redirect status for the old URLs that matter most. Pick ten of them, paste them into our free 301 redirect checker, and see exactly where each one sends Google and your visitors.

ED

Editorial Team

SiteAuditHub builds free WordPress plugins and Chrome extensions for SEO audits, site health, malware scanning and faster publishing. Every tool is tested on real websites to give you clear, practical results.

Connect on LinkedIn

Ready to check your own site?

Run a free scan and see exactly where you stand.

Analyze my site →