Moving to Astro? Make a plan for your links.

The challenge

There is more to move than the pages in your menu

Search results, bookmarks, and links from other websites can send visitors to old articles, downloads, or landing pages. Those addresses are easy to miss during a redesign, especially if nobody has edited them in years.

We list the existing addresses and give each one a plan: keep it, redirect it to a relevant replacement, or remove it with the right response. You can review the changes before anything goes live.

What's included

Check the pages, the links, and the launch

Find the pages people rely on

We use your sitemaps and available search and traffic data to find important pages, images, and downloads. If records are missing, we explain what we can and cannot check.

Compare the agreed SEO fields

You receive an inventory of source URLs, planned destinations, response codes, titles, descriptions, and preferred page addresses (canonicals). We compare the agreed templates and fields on the new site, record omissions, and identify anything we could not verify. Language versions, archives, and pagination are scoped explicitly.

Check the launch settings

We test redirects, check the new sitemap and search engine access, and remove the search restrictions used on the test site. Forms and tracking are included in the launch checks listed in your proposal.

Price and scope

Know which checks your quote covers

We quote from the URL inventory, available records, template types, and proposed changes. The scope distinguishes planning, implementation, pre-launch checks, and post-launch follow-up. It names the URLs and fields covered, responsibilities, unresolved items, and follow-up period. Missing analytics or historical URLs are recorded as limits.

The steps

How the work happens

1. 1

   List the pages and plan the move

   We review the current site and available traffic data, then map changed addresses to their destinations. We discuss any content being merged or removed.

2. 2

   Test before launch

   We check the new site against the page list, search details, and redirect plan, then fix issues before the move.

3. 3

   Check after launch

   We test the live addresses and sitemap, then review Search Console with the access you provide. Your proposal sets the follow-up period and how new issues are handled.

Before we begin

Is this right for your site?

At handover

What you keep

You get the URL and metadata inventory, the agreed redirect decisions, dated check results, and an issue log with owners and next actions. A checked item includes its evidence; an unchecked item stays visible. The proposal lists the launch checks and follow-up included, whether migration is a separate engagement or part of your rebuild.

Technical background: Google Search Central: site moves.

Free planning resource

Give every old URL a decision

Use this inventory in Excel, Google Sheets, or another spreadsheet. It connects each existing address to its intended destination, metadata, owner, and check result. No email is required.

1. 1

   Collect the source addresses

   Start with a crawl and sitemaps. Add available search, analytics, backlink, download, and campaign records. Record missing sources so an incomplete inventory stays visible.

2. 2

   Agree the destination and fields

   Choose keep, redirect, or remove. For a redirect, use a relevant final destination. Record the expected response, title, description, canonical, and indexability. Assign a priority and owner.

3. 3

   Check and retain the evidence

   Check the implemented response and final page, then record the date, result, and evidence location. A redirect should reach its intended final page without a loop or avoidable chain. Recheck after launch. Keep unresolved items open.

This URL inventory is one part of launch acceptance. Use the project brief to include content, forms, publishing, access, and analytics checks too. A completed spreadsheet alone does not guarantee preserved rankings.

Plan the work

Useful before you choose

Prepare the rebuild brief

Give URL decisions, business-critical features, and launch responsibilities a place in the project scope.

Understand migration cost factors

Separate the visual rebuild from content, integrations, SEO checks, and ongoing operation.