Website redesign redirects, a URL mapping worksheet and a practical migration check

Before changing a website's URLs, decide where each existing page will go. A bookmarked service page and a link in a partner's directory still need to help the person who follows them after launch.

This guide checks Google's migration, redirect and HTTP documentation, then turns that guidance into a small-site review workflow. The worksheet is an editorial and technical planning aid. It contains no traffic forecasts or customer results.

Build the map before writing redirect rules

Collect existing URLs from the sitemap, site navigation and analytics that you are authorized to access. Add the links used in sales documents, company profiles and partner listings. A page with little recorded traffic can still be someone's saved reference.

Keep useful URLs when the redesign does not require changing them. If content moves, map it to the equivalent new page. If several pages are merged, check that the destination retains their useful information. If content is retired without a relevant replacement, record that decision explicitly.

Choose the response that matches the decision

For a permanent move, a server-side 301 or 308 communicates the change. Google's redirect documentation identifies these as permanent redirects and distinguishes them from temporary responses.

A retired page without a suitable replacement can return 404 or 410 with a useful explanation. Returning 200 alongside an empty error page can create a soft 404. Google's HTTP status guidance also makes clear that a successful response does not guarantee indexing.

Review destination relevance by opening the page. Sending every old service URL to the homepage forces visitors to start again. Google's migration guidance warns against irrelevant mass redirects and recommends avoiding redirect chains.

Inspect the initial response and the final page

For a single public URL that you are authorized to check, these commands make GET requests without modifying the site. Replace the example address with the old URL from your worksheet. The commands below use a macOS or Linux shell.

curl -sS --max-time 20 -D - -o /dev/null \
  "https://www.example.com/old-service"

curl -sS --max-time 20 -L --max-redirs 5 -o /dev/null \
  -w 'Final status %{http_code}\nFinal URL %{url_effective}\n' \
  "https://www.example.com/old-service"

On Windows, use curl.exe and replace /dev/null with NUL; enter each command on one line. Preserve normal TLS certificate verification. If a command fails, investigate the reported failure before interpreting the result as a page status.

The first request exposes the initial status and any Location header. The second follows a bounded number of redirects and reports the final address. A final 200 only establishes a response condition. Open the final page and check whether it still answers the original visitor's question. Test the initial headers separately because a final 200 can hide an unnecessary chain.

Check the new page's other URL signals

Compare the canonical, internal links and sitemap entry with the intended destination. Google's canonicalization guidance recommends consistent signals. A new page that still declares an old canonical deserves investigation before launch.

Review language destinations separately. An English article should lead to content that serves its English-speaking reader. A Chinese service page needs the same consideration. Do not use the homepage as a substitute for deciding where each language version belongs.

For content-access problems on the destination itself, use the separate HTML inspection guide.

Keep a reviewable release record

For each important old URL, save the initial response, final URL and a short content-review result. Include service pages, externally linked articles and both language entry points. After release, keep checking important old entry points for errors and update links you control to the final addresses.

Open GEO Console's free homepage report can provide a starting view of the homepage's public access conditions. The URL map and individual inner-page checks still need their own review.

A working redirect does not establish that an AI product has refreshed an answer. If a saved answer still cites an old URL, record the product, question and source URL, then inspect that specific path.

References

• Google site migration guidance
• Google redirect documentation
• Google HTTP status guidance
• Google canonicalization guidance