Audit Before You Migrate: Why Every Website Move Should Start With a Full Site Audit

If your law firm, clinic, or restaurant has run on WordPress for a few years, your website has quietly picked up baggage. Plugins were added and removed. Pages were renamed. A developer changed the menu, someone else installed a new SEO plugin, and the old tracking code may or may not still be firing.

None of that is unusual. But it matters a lot the moment you decide to move to a new platform. A migration is the single best chance you will get to clean house, and the single easiest way to carry every hidden problem forward into a brand-new site. The difference comes down to one step: a full site audit before anything moves.

Why “copy everything over” is the wrong starting point

The instinct during a migration is to replicate the old site exactly, page for page. That feels safe. The problem is that “exactly” includes the broken links, the duplicate pages, the missing descriptions, and the schema markup that stopped validating two plugin updates ago.

If you copy those issues, you get a new site that looks better but performs the same, or worse, because now nobody remembers which problems were already there. When rankings dip after launch, you can’t tell whether the migration caused it or whether the problem was inherited.

An audit changes the goal from copying the old site to improving on it, while keeping everything that is already working.

What a proper pre-migration audit covers

A useful audit is not a single score from a free tool. It is a structured look at every layer that affects how search engines and visitors experience your site.

Structured data (schema)

Schema markup tells Google what kind of business you are. Two things to check:

• Validity. Does the markup pass Google’s Rich Results Test and the Schema.org validator without errors?
• Type. Is it the right type? A law firm should usually use Attorney or LegalService, a clinic MedicalClinic or a related medical type, and a restaurant Restaurant, all of which are more specific forms of LocalBusiness. Many WordPress sites use a generic Organization type set by a plugin years ago, or have two plugins outputting conflicting markup.

Titles, meta descriptions, and headings

Crawl every page and look for missing, duplicated, or truncated title tags and meta descriptions. Check that each page has one clear H1 and a logical H2/H3 structure. These are easy to fix during a migration and easy to lose if nobody records them first.

Broken links, redirect chains, and 404s

• Broken internal links send visitors and crawlers to dead ends.
• Redirect chains (page A redirects to B, which redirects to C) slow things down and dilute signals. Years of URL changes often stack up into chains nobody intended.
• 404 errors that already exist should be found now, so you can decide which ones deserve a redirect and which can stay gone.

Sitemap, robots.txt, and canonicals

Confirm that your XML sitemap lists the pages you actually want indexed, and nothing else. Check that robots.txt isn’t blocking anything important. Review canonical tags: a common WordPress issue is canonicals pointing to the wrong version of a page (with or without a trailing slash, HTTP instead of HTTPS, or a staging domain).

Core Web Vitals and page speed

Record your current Core Web Vitals (Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift) from Google Search Console or PageSpeed Insights. You need these numbers to prove, after launch, that the new site is faster rather than just assuming it.

Indexing, thin content, and duplicate content

Google Search Console’s page indexing report shows which pages are indexed and which are excluded, and why. Look for:

• Thin pages with very little useful content (old tag archives, empty category pages, placeholder service pages).
• Duplicate or near-duplicate pages, such as the same service page published for several cities with only the city name changed.
• Pages that should be indexed but aren’t.

The migration is the right moment to merge, improve, or retire these pages deliberately.

Image alt text

Missing alt text hurts accessibility and gives up a small but real SEO signal. An audit gives you a list of images to fix rather than re-uploading them exactly as they were.

Tracking: GTM, GA4, and call tracking

This is the item most often broken by migrations and the one business owners notice last. Document:

• Which Google Tag Manager container is installed, and what tags it fires.
• Your GA4 property and the conversions (form submissions, calls, bookings) you rely on.
• Call tracking numbers and the scripts that swap them on the page.
• Any ad platform pixels.

If a clinic’s call tracking silently stops after launch, the site may look fine while the marketing reports show leads “dropping.” Recording the setup in advance prevents that.

Fix issues, don’t migrate them

Once the audit is done, sort the findings into three groups:

1. Keep as-is. URLs, content, and metadata that already perform well. These get preserved exactly.
2. Fix during migration. Missing metadata, wrong schema type, broken links, redirect chains, missing alt text. It is usually cheaper to fix these as the new site is built than to patch them later.
3. Retire or consolidate. Thin or duplicate pages that should be merged into stronger pages, with 301 redirects pointing old URLs to the new destination.

This turns the migration from a risky copy job into a planned upgrade.

The audit is also your baseline

The most underrated benefit of a pre-migration audit is that it gives you a baseline: a snapshot of where things stood before the move. That includes:

• Rankings for your important keywords.
• Organic traffic and conversions by page.
• Indexed page count.
• Core Web Vitals scores.
• The full list of URLs and their metadata.

After launch, you compare against that baseline. If something moves, you can see exactly what changed and respond quickly. Without it, every conversation about post-launch performance becomes guesswork.

How we approach it at GrowthFlow360

When a business moves to GrowthFlow360, the AI-managed website and marketing platform from Hispanic Market Advisors, the audit comes first. We crawl the existing WordPress site, document every URL and its metadata, validate schema, review tracking, and record a performance baseline. Issues get fixed as part of the build instead of being carried over, and the baseline is what we measure the new site against.

The bottom line

A migration is not just a technical move. It is a chance to correct years of small problems at once. Start with a complete audit, decide deliberately what to keep, fix, and retire, and keep a baseline you can measure against. The new site should be better than the old one, and you should be able to prove it.