HQ Paphos, Cyprus · worldwide
Yes. An audit decides what moves, what merges and what gets redirected before any page is rebuilt. On A1 Sure Services' WordPress site it covered 36 pages, 155 blog posts and 257 thin tag archives; the archives closed with one redirect rule, and the final crawl before launch found zero broken links.
Start from the list of URLs that actually exist, not from the menu. On the A1 Sure Services site the list came from the WordPress sitemaps, because the menu hid several pages. Each URL was then checked: a few were already WordPress redirects to other posts, so they became redirects again instead of pages.
An audit is also where thin and overlapping pages come out. A1 Sure Services showed both kinds:
| Found in the audit | Decision | Result |
|---|---|---|
| 257 tag archives | Thin pages, two to five posts each | Not rebuilt: one wildcard 301 sends every /tag/ address to the blog |
| 15 category archives and 1 author page | Archive pages, not rebuilt | Redirected to the blog the same way |
| Nine North Shore copies of the service pages | Overlapping pages | Folded into one North Shore hub |
| Six other overlapping pages | Overlapping pages, retired | Merged into the pages that replaced them |
When an old URL is clean and still matches what the page is for, keeping it lowers the risk. A1 Sure Services kept 155 blog posts on the exact addresses they had, which is why the audit mattered: it separated the pages worth carrying over unchanged from the ones that needed a destination. Every URL that does change needs a deliberate target, a 301 redirect and internal links updated to match. On A1 Sure Services that meant 34 redirect rules, each requested once after publishing, and over 300 internal links repointed so none of them goes through a redirect.
The URL and redirect map is usually the highest-risk step of a migration, because it controls whether old ranking signals and links reach the right new pages. Auditing first means that map is written from the real site rather than from memory, and the launch check has something to be measured against. A1 Sure Services ended with 190 pages live on Webflow and 0 broken links on the final crawl, run before the domain was switched.
What the audit finds, such as plugin-dependent content, page-builder layouts and custom fields, is also what sizes the job, so it comes before any quote. For scope and timing, see Webflow migration cost and timeline. The full case is on the A1 Sure Services case study.
Webflow's MCP server lets an AI agent build pages, restructure CMS collections and apply SEO metadata across a whole site. Here is what that changes at each stage of a WordPress-to-Webflow migration — and the parts it changes nothing about.
Tell us what you are building and we'll reply within 24 hours on business days.
Prefer to talk? Book a free intro call.
