Setting Up 301 Redirects After a Site Move

What Is a 301 Redirect and Why Does It Matter After Migration?

A 301 redirect is a permanent HTTP signal that tells browsers and search engines an old URL has moved to a new location. After you migrate your site, every changed URL needs to map to its new home before you go live. Miss this step and Google treats your old pages as broken. Rankings you've built over months can collapse in days.

The process itself is straightforward: crawl first, map second, implement third, validate fourth, monitor for 30 days. But the sequencing is what saves you.

If you're still in the planning phase, read how to migrate a site without losing search rankings before touching any server settings. This article picks up where the planning ends and walks you through every implementation step, from URL mapping to validation on launch day.

Why 301 Redirects Matter for SEO After a Migration

A 301 tells Google the move is permanent and transfers the ranking signals you've accumulated on the old URL to the new one. A 302, by contrast, signals a temporary move. Google keeps indexing the old URL and withholds the authority transfer. This distinction matters.

If your old product page ranked on page one and you use a 302, Google keeps it in the index while your new URL starts from zero. You end up with two competing versions and your ranking signals split between them.

Four things happen when you implement a correct 301:

1. Link equity transfers. The authority from inbound links pointing to your old URL flows to the new destination. The transfer isn't instantaneous; Google processes it over crawl cycles.
2. The old URL is deindexed. Once Google processes the permanent redirect, it stops indexing the source URL and consolidates all signals to the destination.
3. Crawl budget is conserved. Clean redirects prevent bots from wasting time chasing dead ends across your site.
4. Users land on the right page. A 301 is invisible to visitors but protects the experience regardless of where they clicked the link from.

This step is part of the 20% of SEO that drives 80% of results. Redirect integrity is one of those foundational technical tasks that underpins everything else you build.

Step 1: Audit and Map Your URLs Before Migration Day

You need a complete map of every old URL paired with its new destination before you touch any server config. That map is the single most important document in your entire migration. Without it, implementation becomes guesswork and validation becomes impossible.

Here's the crawl-and-prioritise process, step by step.

Crawl Your Existing Site

Use Screaming Frog (free up to 500 URLs) or any site crawler to export a full list of every live URL. Export it as a spreadsheet. Include status codes so you can filter out pages that are already 404s or already redirecting.

Identify What Changed

Compare the old URL list against your new site architecture. Three things generate redirect requirements: URL slug changes, folder restructuring, and domain changes. Mark each row as "same", "changed", or "removed".

Prioritise by Traffic and Links

Not all URLs are equal. Sort your list by two signals you can actually measure: organic traffic from Google Search Console and inbound links from Google Search Console's Links report or any link analysis tool you already use. Redirect the high-traffic, high-link pages first. If something goes wrong during implementation, your most valuable pages are protected before your least valuable ones.

Build the Mapping Spreadsheet

Your spreadsheet needs four columns at minimum: old URL, new URL, HTTP status (to verify after launch), and priority (high/medium/low). This document becomes your validation checklist on launch day.

Treat this mapping exercise as part of a 30-minute weekly SEO routine for founders. Ongoing URL hygiene prevents the accumulated mess that makes future migrations painful.

One Rule for the Map

Every old URL maps to the most equivalent new URL available. If an exact equivalent doesn't exist, map to the closest category or parent page. Mapping to the homepage is a last resort, not a default.

Step 2: Implement 301 Redirects on Your Platform

The method depends on your server or CMS, but each platform has one canonical way to do it. Using the wrong method (JavaScript redirects, meta refresh tags) will technically move users but won't reliably transfer SEO signals. Stick to server-level or CMS-native methods.

Apache (.htaccess)

For Apache servers, add redirect rules to your .htaccess file in the site root:

Redirect 301 /old-page/ https://www.yoursite.com/new-page/

For large-scale migrations, use RedirectMatch with regex to handle pattern-based URL changes (a blog folder rename, for example) in a single rule instead of hundreds of individual lines. Watch out: .htaccess rules process top to bottom, so order matters. A poorly ordered rule can create a redirect loop.

Nginx (nginx.conf or server block)

Nginx handles redirects in the server configuration file, not a per-directory file:

location = /old-page/ {
    return 301 https://www.yoursite.com/new-page/;
}

Nginx return 301 is faster and more reliable than rewrite for simple redirects. Watch out: changes require a config reload (nginx -s reload) to take effect. Forgetting to reload is one of the most common reasons redirects appear not to work.

WordPress

WordPress handles redirects cleanly through a plugin or via the functions.php file. The Redirection plugin (free, widely maintained) provides a UI for managing rules without touching server config, which works well for non-technical founders. Learn more about configuring your site in the WordPress blog platform setup guide. Watch out: some hosts bypass .htaccess for WordPress sites; confirm your host's redirect handling before relying on file-level rules.

For a code-level approach, add to functions.php:

add_action('template_redirect', function() {
    if ($_SERVER['REQUEST_URI'] === '/old-page/') {
        wp_redirect('https://www.yoursite.com/new-page/', 301);
        exit;
    }
});

Shopify

Shopify has a built-in URL redirects tool under Online Store > Navigation > URL Redirects. Use it. You can't edit .htaccess on Shopify's infrastructure. For bulk imports, Shopify accepts a CSV upload of old and new URL pairs. Watch out: Shopify only redirects within your own domain; cross-domain redirects after a domain migration require DNS-level configuration.

CDN Fallback (Cloudflare, Fastly, etc.)

If you sit behind a CDN, you can implement redirects at the edge using redirect rules or page rules. This is useful when you can't modify the origin server directly. For founders building a professional website without coding on hosted platforms, CDN-level redirects are often the only server-level option available. Watch out: CDN rules have a hierarchy; ensure your redirect rule fires before any caching rule that might serve a stale response.

Redirect Setup by Migration Phase: What to Do and When

Redirect setup runs across five phases from pre-migration to 30 days post-launch. Each phase has a distinct action and a measurable outcome. Trying to compress all of this into a single launch-day sprint is how redirects get missed.

Treating migration as a project with phases also applies to your content strategy. The same discipline that makes redirects reliable makes planning your monthly content calendar work over time: defined phases, clear owners, measurable outcomes.

The table above is a checklist, not a guarantee. What it does guarantee is that if something goes wrong, you know exactly which phase to look at.

Step 3: Test and Validate Every Redirect After Launch

Use browser testing for spot checks, curl for server-level confirmation, and Google Search Console Coverage for comprehensive detection of missed URLs. All three methods serve a different purpose. None of them alone is sufficient.

Browser Spot Checks

Visit your highest-priority old URLs directly in a browser. You should land on the new destination with no visible redirect trail. This checks the end-user experience but doesn't confirm the HTTP status code.

curl for Server-Level Confirmation

The curl command tells you exactly what the server returns, including the status code and the Location header:

curl -I -L https://www.yoursite.com/old-page/

The -I flag returns headers only. The -L flag follows the redirect chain. You're looking for an initial HTTP/1.1 301 followed by a final HTTP/1.1 200. If you see HTTP/1.1 302, your redirect type is wrong. If you see multiple 301s before the 200, you have a redirect chain that needs cleaning.

Google Search Console Coverage Report

In Search Console, open the Coverage report and filter by "Not found (404)". After launch, any URLs that were mapped but not redirected will appear here as Google attempts to crawl them. Check this report daily for the first seven days.

Redirect Chain Detection

A redirect chain occurs when URL A redirects to URL B, which redirects to URL C. Each hop adds latency and dilutes the authority transfer. After launch, run your URL list through a bulk redirect checker to identify chains. Screaming Frog's bulk export mode will flag them. Fix chains by pointing the original URL directly to the final destination, bypassing intermediary hops.

For the full migration workflow these steps slot into, see the full site migration SEO checklist.

Common 301 Redirect Mistakes That Cost You Rankings

The four most costly mistakes are redirecting to the homepage instead of equivalent pages, using 302 instead of 301, setting up redirects after DNS has already propagated, and ignoring redirect chains from past migrations. Each one has a distinct, avoidable consequence.

Redirecting everything to the homepage. This is the most widespread mistake and one of the most damaging. When Google sees hundreds of URLs all redirecting to the homepage, it interprets them as soft 404s, not valid redirects. The ranking signals from those old URLs don't transfer. Map to the nearest equivalent page. Always.

Using 302 instead of 301. A 302 tells Google the move is temporary. Google continues indexing the old URL and withholds the authority transfer to the destination. Many CMS plugins and hosting dashboards default to 302; always verify the status code with curl after implementing.

Setting up redirects after DNS propagates. If your new site goes live and Google crawls it before your redirects are in place, those URLs return 404 errors. Even a short window matters: Googlebot crawls active sites frequently, and a 404 can be processed and cached before your redirect is in place. Implement redirects before or simultaneously with the DNS cutover, never after.

Ignoring chains from past migrations. If your site has been migrated before, you likely have existing redirect chains buried in your config. A new migration layered on top extends those chains further. Before launch, audit for existing redirects and consolidate chains to direct hops. This connects directly to the SEO fundamentals that actually move rankings: clean technical foundations compound over time; messy ones compound debt.

What to Do When You Find Missing Redirects After Launch

It's not too late if you find missing redirects after the site is already live. But speed matters. Google re-crawls active pages regularly, so a redirect added within 48 hours has a strong chance of being picked up before rankings drop significantly.

Triage First

Open Google Search Console Coverage and filter for 404 errors. Export the list. Cross-reference it against your original mapping spreadsheet to identify which URLs were missed. Sort by estimated traffic impact: URLs that were ranking for high-volume queries need fixing first.

Implement and Verify Immediately

Add the missing redirects to your server config or CMS the same day you find them. Verify each one with curl before closing the task. Don't batch them into the next sprint; every day without a redirect is a day Google may process a 404 and update its index accordingly.

Recovery Timeline

Recovery isn't linear and isn't guaranteed within a specific window. What's honest to say: once a correct 301 is in place, Google will pick it up during its next crawl of that URL. For pages with strong inbound links, ranking recovery often follows within weeks. For pages that were already losing traffic before the migration, the redirect alone may not be sufficient.

Incorporate this monitoring into your weekly SEO monitoring routine so missed redirects surface quickly rather than sitting undetected for months.

Frequently Asked Questions

How long does it take for a 301 redirect to be picked up by Google?

Google typically processes 301 redirects within days to a few weeks, depending on how frequently it crawls your site. High-authority pages with strong inbound links tend to be re-crawled faster. There's no guaranteed timeline; crawl frequency varies by site size and link equity.

Does a 301 redirect pass 100% of link equity?

No redirect passes 100% of link equity. The practical understanding is that a 301 passes the substantial majority of ranking signals; the loss is small enough that it's not a reason to avoid migrating.

How many 301 redirects can a site have?

There's no hard limit on the number of 301 redirects a site can have. Large e-commerce sites regularly maintain thousands of active redirects without measurable SEO penalty. The concern isn't quantity but quality: long redirect chains and loops are the performance and SEO problems to avoid, not a high count of clean one-hop 301s.

Do I need 301 redirects if I'm just changing my domain?

Yes, absolutely. A domain change is the highest-stakes migration scenario there is. Every URL on your old domain needs a 301 pointing to its equivalent on the new domain. Without redirects, all organic traffic to the old domain returns 404 errors and your entire site effectively disappears from search results. Read the full guide to migrating without losing rankings before proceeding.

Should I remove old redirects after a year?

Generally, no. Inbound links across the web continue pointing to old URLs indefinitely, and removing redirects turns those links into dead ends. Keep your redirects in place as long as the destination page exists. The server overhead from maintaining a large redirect list is negligible on modern infrastructure.

Redirects Done Right: The Migration Step You Cannot Skip

The process is crawl, map, implement, validate, monitor, and it runs for 30 days, not one afternoon. Treating 301 redirects after migration as a single task rather than a phased workflow is the root cause of most post-migration ranking drops.

Here's the process distilled:

• Before launch: Crawl your old site, build a prioritised URL map, and implement redirects in staging
• Launch day: Verify your top 20 priority URLs return HTTP 301 immediately after DNS cutover
• Days 1-7: Check Google Search Console Coverage daily for 404 spikes and fix missing redirects within 48 hours
• Days 7-30: Monitor ranking recovery on priority URLs, clean any redirect chains, and confirm deindexing of old URLs
• Ongoing: Keep redirects in place, review the list before any future migration

Ranking recovery after a redirect is in place is real, but it takes time. The closer your implementation is to migration day, the better the outcome tends to be.

If you're spending your time managing spreadsheets and server configs instead of building your product, founders are automating the repeatable parts of their SEO workflow. If AI automation for content creation is on your roadmap, Agent Solo handles the research, writing, and publishing so redirects and content can compound together rather than compete for your attention.

Founders who want their SEO infrastructure handled end-to-end can get early access.