- 01 / BEFORE DESIGN
1. Record what is working now
Export organic landing-page data from Google Search Console and analytics before anyone changes navigation. Record queries, clicks, impressions, conversions, backlinks, indexed pages, and current Core Web Vitals. Note pages that drive calls or appointment requests even if they are not visually impressive.
This benchmark gives the team a list of assets to protect and a way to judge launch impact. Do not rely on a rank tracker alone; rankings vary by location, device, and personalization. Search Console shows the queries and pages Google actually connected with your site. Save the exports outside the old platform so they remain available after launch.
- Export at least 12 months of Search Console page and query data.
- List top organic landing pages and the actions they generate.
- Capture backlinks and pages with strong external references.
- Save analytics annotations and current crawl reports.
- 02 / URL INVENTORY
2. Map every old URL to its destination
Crawl the current site and combine that list with XML sitemaps, Search Console, analytics, server logs if available, and backlink data. A crawler alone may miss orphaned pages that still receive traffic. Put every known URL in a spreadsheet with status, traffic, target URL, action, and owner.
Keep strong URLs unchanged whenever the content and purpose remain the same. A new design does not require a new address. When pages must move, map each old URL to the closest relevant new page. Do not redirect hundreds of unrelated services to the homepage; that is poor for users and can be treated as a soft 404.
- 03 / REDIRECTS
3. Build and test one-to-one 301 redirects
Use permanent 301 redirects for content that has moved for good. Implement them at the server or platform level, not with JavaScript or a delayed meta refresh. Avoid chains in which URL A redirects to B and then C. Point A directly to C. Keep redirects active long enough for users, search engines, and old links to catch up; in practice, retaining them indefinitely is often simplest.
Test the redirect file on a staging or local environment before launch. Check for loops, chains, 404s, and accidental redirects to irrelevant pages. Update important internal links to point directly at new destinations rather than relying on redirects. Redirects are a safety net, not a substitute for cleaning up the new site.
- Use 301 status codes for permanent moves.
- Map old pages to the closest equivalent, not automatically to the homepage.
- Remove redirect chains and loops.
- Update navigation, body links, canonicals, and sitemaps to final URLs.
- 04 / CONTENT AND SIGNALS
4. Preserve the reasons a page ranked
A high-ranking service page may look wordy, but deleting half of it without analysis can remove the exact answers and context that made it useful. Preserve the page purpose, primary topic, important sections, clinician details, location facts, internal links, title tag, and relevant headings until performance data supports a change.
Maintain canonical tags, robots directives, hreflang where used, Open Graph data, and structured data. Schema should describe the visible new page accurately; do not copy markup blindly if facts changed. Carry over image alt text when it is still correct. If the redesign combines pages, make sure the destination fully covers the intent of each retired URL.
- 05 / PRE-LAUNCH
5. Crawl staging like a search engine
Keep staging blocked from indexing, but make sure your testing setup does not hide errors. Crawl the full site and verify status codes, titles, descriptions, headings, canonicals, internal links, image paths, schema, and pagination. Test forms, booking links, phone numbers, analytics, consent tools, and location information on mobile devices.
Prepare the final redirect rules and new XML sitemap. Confirm production robots.txt will allow the pages you want indexed. One of the most damaging launch mistakes is carrying a staging noindex tag or password rule into production. Assign a launch owner who can roll back or repair critical failures quickly.
- No production page accidentally contains noindex.
- Canonical tags use the final production host and URL.
- The XML sitemap contains only indexable 200-status URLs.
- Analytics, Search Console verification, forms, and conversions work.
- Priority templates pass mobile, speed, accessibility, and schema checks.
- 06 / AFTER LAUNCH
6. Monitor for 30, 60, and 90 days
In the first 30 days, crawl frequently and watch server errors, 404s, excluded pages, redirect failures, analytics gaps, and changes in clicks to priority pages. Submit the new sitemap in Search Console and inspect a sample of important URLs. Small ranking movement is normal while systems recrawl and reassess the site.
At 60 days, compare queries and landing pages with the benchmark, accounting for seasonality. Investigate page-level losses rather than assuming the entire redesign failed. At 90 days, review broader trends, conversion quality, Core Web Vitals, backlinks landing on errors, and pages that have not been indexed. Keep the old benchmark and mapping document; they remain useful for every later diagnosis.
- Days 0-30: technical errors, indexing, tracking, and priority-page checks.
- Days 31-60: query and landing-page comparisons with focused corrections.
- Days 61-90: trend review, conversions, performance, and unresolved indexing.
- 07 / COMMON FAILURES
Mistakes that routinely tank visibility
The biggest failures are predictable: changing every URL for style, deleting useful pages, redirecting everything to the homepage, launching with noindex, replacing specific copy with vague marketing language, and forgetting internal links. A visually cleaner site can still provide less information to both patients and search engines.
Another mistake is making major SEO, platform, domain, copy, and design changes on the same day. That makes diagnosis difficult. Keep the domain when possible, preserve URLs, and stage changes deliberately. There are no guarantees in organic search, but a documented migration sharply reduces preventable loss and gives the team evidence when something moves.