# What we check before we touch a single redirect | Plyo

> The URL inventory that keeps old links working and search traffic steady when a website moves.

Source: https://plyo.studio/blog/before-we-touch-a-single-redirect

1.  [Home](/)
2.  [Blog](/blog)
3.  What we check before we touch a single redirect

# What we check before we touch a single redirect

The URL inventory that keeps old links working and search traffic steady when a website moves.

Plyo Studio 7 May 2024 6 min read

On this page

[Step 1: Find every URL that exists](#step-1-find-every-url-that-exists)[Step 2: Don’t forget the non-page URLs](#step-2-dont-forget-the-non-page-urls)[Step 3: Rank by value](#step-3-rank-by-value)[Step 4: Map old to new](#step-4-map-old-to-new)[Step 5: Test before launch](#step-5-test-before-launch)[Step 6: Watch after launch](#step-6-watch-after-launch)[The short version](#the-short-version) [Common questions](#common-questions)

Related service

[Website migration](/services/website-migration)

Redirects are the safety net of a website migration. When someone follows an old link, from Google, a newsletter or another site, a redirect sends them to the right new page. Get them right and the move is invisible. Get them wrong and traffic leaks away quietly for months.

The redirects themselves take an afternoon. The work that matters is the inventory that comes before them.

## Step 1: Find every URL that exists

No single source has the full list, so we combine several:

-   **A full crawl** of the live site, following every internal link
-   **The sitemap**, which often lists pages the navigation has forgotten
-   **The CMS export**, for blog posts, collections and draft pages that went live once
-   **Google Search Console**, for every URL Google has indexed or shown in results
-   **Analytics**, for landing pages that have had visits in the last year
-   **Backlinks**, from Search Console’s links report or an SEO tool, for pages other sites link to

The overlap is large, but the gaps are where problems hide: an old campaign page still linked from a partner site, or a PDF that ranks for a valuable search.

## Step 2: Don’t forget the non-page URLs

These catch people out most often:

-   PDFs, brochures and downloadable files
-   Images that rank in image search
-   Old blog category and tag pages
-   Pages with tracking parameters still linked from emails
-   Different versions of the same URL: with and without `www`, with and without a trailing slash

## Step 3: Rank by value

Not every URL deserves the same attention. We sort the list by traffic, backlinks and conversions. The top twenty or so get a hand-checked redirect to the best possible match. The long tail gets sensible rules.

> Every old link is a promise someone else made on your behalf. Redirects keep it.

## Step 4: Map old to new

For each URL we decide one of three things:

Situation

What we do

The page exists on the new site

Keep the same URL if possible. If not, 301 redirect to it.

The content merged into another page

301 redirect to the page that now covers it.

The page is gone with no equivalent

Redirect to the closest parent page, or let it return a proper 404 if nothing fits.

A few rules we follow:

-   **Use 301s, not 302s.** A 301 says the move is permanent, which is what you want search engines to remember.
-   **No chains.** Old page to new page, in one step. Redirects that hop through several URLs slow things down and dilute their value.
-   **Use patterns carefully.** Rules that redirect a whole folder at once are useful, but we test them against the full list so they don’t catch pages they shouldn’t.

## Step 5: Test before launch

We load the redirect map onto staging and run every old URL through it with a script. Each one should land on a working page in a single hop. Anything that returns an error or lands on the homepage gets a second look.

On Cloudflare, redirects can live in a simple file alongside the site or as rules at the network level, so they respond almost instantly.

## Step 6: Watch after launch

Even with a careful inventory, something occasionally slips through. For the first month we check Search Console for new 404 errors each week and add redirects as needed. After that, the list is stable and the old site can be retired.

## The short version

1.  Combine every source to find every URL
2.  Include files, images and odd URL variations
3.  Rank by value and hand-check the important ones
4.  Map each one with a single permanent redirect
5.  Test the whole list before launch
6.  Monitor for a month afterwards

If you’re planning a move and want this done properly, it’s part of every migration we run.

## Keep reading.

[All posts](/blog)

-   [
    
    Migration Leaving Wix or Squarespace: what to plan for 6 min read](/blog/leaving-wix-or-squarespace)
-   [
    
    Migration Moving from WordPress without losing rankings 8 min read](/blog/moving-from-wordpress-without-losing-rankings)
-   [
    
    Migration Website migration: the do’s and don’ts 8 min read](/blog/website-migration-dos-and-donts)

Updated 7 May 2024

FAQ

## Common questions

[Ask a question](/contact)

### How long should I keep redirects after a migration?

Keep them for as long as possible, ideally permanently. Old links in emails, documents and other websites can keep sending visitors for years.

### What happens if I don't set up redirects?

Old links return errors, visitors leave, and search engines gradually drop the old pages, taking their rankings with them.

### Should I use a 301 or a 302 redirect?

Use a 301 for permanent moves like a migration. A 302 is for temporary changes and doesn't signal that the move is permanent.

About Plyo Studio

## Custom Astro websites. Built on Cloudflare.

Plyo Studio is an independent web studio that designs and builds fast, search-ready websites, web apps and interactive maps. Sites are custom-built in Astro and hosted on Cloudflare, so they load quickly and are easy for search engines and AI answer engines to read.

Founded by Chloe Nixon, a full stack developer and UI/UX designer from Australia, and Micky, a software engineer from New Zealand. Clients work directly with the founders from the first call to launch. Typical work: custom websites, migrations off Webflow, WordPress, Wix and Squarespace, web apps, and interactive maps and GIS. Projects are quoted at a fixed price before work starts.

[Start a project](/contact) [hello@plyo.studio](mailto:hello@plyo.studio) [About us](/about)

## Related pages

-   [Blog Read practical notes on designing, building and moving websites.](/blog)
-   [Website migration Move off WordPress, Wix or Squarespace without losing the rankings you have earned.](/services/website-migration)

Start a conversation

## Ready for a website that works harder?

[Start a project](/contact) [Free website audit](/audit)
