You do a content audit before a migration by listing every page on the site, then deciding for each one whether to keep it, merge it, improve it, or remove it, based on its traffic, its backlinks, and its purpose. The reason the audit comes before the move is that it decides what the move should carry. The pages worth keeping migrate and get redirects, the thin or duplicate ones get merged into stronger pages, the valuable but dated ones get noted for improvement, and the genuinely dead ones are retired deliberately rather than dragged along. Doing this first turns a migration from a blind copy of everything into a considered transfer of what earns its place, which is both cleaner and less work to rebuild. It also produces the redirect map as a by product, because every keep and merge decision defines where an old URL should point. The one rule that protects SEO is that no page with traffic or links is removed without a 301 to a relevant replacement. WPBuildAI scans your site and returns the full URL list with each page’s content, so the audit starts from the real site rather than a guess.
Audit for citation as well as for rankings and traffic, because the two now diverge: Seer Interactive found pages cited in an AI Overview earning about 2.1 percent click-through while uncited pages managed 0.9 percent, so a page with modest traffic that answer engines quote is worth more than its analytics suggest.
Why the audit comes before the move
It is tempting to migrate everything and sort it out later, but that order costs you twice. You spend effort rebuilding pages that should have been retired, and you risk breaking URLs you have not thought about. Auditing first inverts this: you decide what deserves to move, so the migration carries only what earns its place, and every decision about a page is also a decision about where its URL should go. The audit is therefore not a separate chore from the migration; it is the planning stage of the migration. A move guided by an audit is lighter to build and safer for SEO, because nothing is transferred or dropped by accident.
Step one: list every page
The audit starts with a complete inventory, because you cannot judge pages you do not know you have. List every URL on the site, including old posts, tag and category pages, and anything that accumulated over the years. Web Almanac 2024 (HTTP Archive) is a reminder that sites carry far more URLs than their owners remember, so a list built from memory will miss pages, and the ones it misses are exactly the ones that break silently in a move. A complete inventory, produced by find and extract all URLs, is the foundation. Everything else in the audit is a decision applied to each item on this list.
Step two: bring in the evidence
Judge pages on data, not on how attached you feel to them. For each page, gather three signals: how much traffic it gets, how many and how valuable its backlinks are, and what purpose it serves in the site. Traffic and links matter because value concentrates on a minority of pages, as the Ahrefs study and the Backlinko analysis both show, so a small set of pages deserves the most protection. Purpose matters because some pages earn their place by function rather than traffic, such as a contact or policy page. With these three signals attached to every URL on your list, you can make consistent decisions rather than sentimental ones.
Step three: sort into keep, merge, improve, remove
Now apply four buckets to each page. Keep is for pages that perform or serve a clear purpose: they migrate as they are and get a redirect if their URL changes. Merge is for thin or overlapping pages that are stronger combined: their content folds into a better page, and their old URLs redirect to it. Improve is for pages with value but obvious weaknesses: they migrate, with a note to strengthen them after the move. Remove is for pages with no traffic, no links, and no purpose: they are retired. These four decisions cover every page, and crucially each one also says what happens to the URL, which is how the audit doubles as the start of your redirect map.
Step four: turn decisions into a redirect map
Because every keep, merge, and remove decision implies a destination, the audit naturally produces the redirect plan. A kept page with a changed URL gets a 301 to its new self. A merged page gets a 301 to the page it was folded into. A removed page that had traffic or links gets a 301 to the most relevant survivor, while a removed page with nothing gets an honest 404 or 410. This is the same redirect discipline as any site move, but arrived at deliberately rather than scrambled together at launch. The audit means you reach the migration with the redirect map already written, instead of discovering gaps from lost traffic afterward.
The rule that protects SEO
Through all of this, one rule keeps the audit safe: never remove or merge a page that has traffic or links without a 301 to a relevant replacement. The whole risk of a content audit is that, in the enthusiasm to trim, you delete pages that were quietly earning value, and the value goes with them. The signals you gathered exist precisely to prevent that, by flagging which pages must not disappear into a 404. Pruning is healthy, but it has to be done with the evidence in front of you. A page can be removed from the navigation and the build while still being honored with a redirect, so trimming the site never has to mean discarding the value it earned.
Steps to run a pre-migration content audit
- List every URL on the site for a complete inventory.
- Attach traffic, backlinks, and purpose to each page.
- Sort each page into keep, merge, improve, or remove.
- Record the destination each decision implies for its URL.
- Build the redirect map from those destinations.
- Protect value: never remove a page with traffic or links without a 301.
Worked example: trimming a bloated site before a move
Imagine a company site of nine hundred pages, grown over a decade, about to replatform. The team builds a full inventory and attaches traffic and link data to every URL. The audit reveals that around two hundred pages carry almost all the traffic and links, several hundred are thin or duplicated, and a few hundred are dead, including old event pages and abandoned drafts. They mark the two hundred as keep, fold dozens of thin pages into stronger merges, flag forty dated but valuable pages as improve, and retire the dead ones. Every keep and merge gets a redirect destination; the few dead pages with old links get 301s to relevant survivors, the rest return 404. They reach the migration with a redirect map already in hand and a much smaller, stronger site to rebuild, which is part of judging the difference between redesign and replatforming.
Limitation: an audit guides the move, it does not perform it
It is fair to mark the boundary. A content audit tells you what to carry, merge, improve, and retire, and it produces the redirect map, but it does not execute the migration or guarantee rankings by itself. You still have to carry the kept content across intact, apply the redirects, and preserve metadata, which is the migration work the audit only plans. The audit also reflects the site at the moment you run it, so if the move is months away, recheck the data before launch. Think of the audit as the blueprint that makes the migration deliberate, then carry it out with the same care, finishing with a proper launch checklist.
Common mistakes
- Migrating everything by default instead of deciding what earns its place.
- Building the page list from memory and missing forgotten URLs.
- Judging pages by attachment rather than by traffic, links, and purpose.
- Removing or merging valuable pages without a 301 to a replacement.
- Auditing after the move, once clutter is already copied and URLs are broken.
Key points
A content audit before a migration lists every page, then sorts each into keep, merge, improve, or remove based on its traffic, backlinks, and purpose, so the move carries only what earns its place. Doing it first makes the migration lighter to build and safer for SEO, and it produces the redirect map as a by product, since every decision defines where an old URL should point. Use evidence, not sentiment, and protect value with the one firm rule: never remove or merge a page with traffic or links without a 301 to a relevant replacement. Start from a complete inventory so no forgotten page breaks silently, a step that pairs with finding orphan pages before a redesign. WPBuildAI scans your site and returns the full URL list with each page’s content, so the audit starts from the real site rather than a guess. Send your web address for a free analysis.
Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.