Short answer: audit before design, not after launch
The safest WordPress redesigns start with an SEO inventory before visual design begins. Export every indexable URL, identify the pages that rank or convert, decide what stays, map anything that moves, and keep the strongest page intent intact. That is the difference between a controlled website redesign and a launch that quietly loses traffic.
Pre-redesign checklist
- Crawl the current site: export URLs, status codes, titles, descriptions, H1s, canonicals and internal links.
- Pull Search Console data: identify pages with impressions, clicks, backlinks or commercial keywords.
- Mark page decisions: keep, improve, merge, redirect or noindex.
- Preserve intent: do not merge a ranking service page into a vague homepage section.
- Plan redirects: every changed URL needs a specific 301 target.
- Check content parity: the new page must keep the useful answers, proof and local signals from the old page.
Redirect mapping table
| Old URL decision | What to do | SEO risk |
|---|---|---|
| Same page, same intent | Keep the URL where possible. | Lowest risk. |
| Better URL needed | 301 old URL to the closest matching new page. | Moderate if intent is preserved. |
| Duplicate or cannibalising page | Merge unique content into the stronger page, then 301. | Good upside when done carefully. |
| Thin low-value page | Redirect if there is a relevant replacement; otherwise noindex or 410 only with care. | Depends on backlinks and traffic. |
Keep the SEO elements that already work
A redesign often rewrites the visual system and accidentally deletes ranking signals. Preserve or improve title tags, meta descriptions, H1s, service headings, internal links, image alt text, FAQ content, schema and local proof. If a page currently ranks for "website redesign Australia" or "WordPress website design Brisbane", do not make the new page more generic.
Use the redesign to strengthen chunks for AI retrieval: answer-first sections, comparison tables, specific service/location headings and proof links. This helps search engines and AI systems retrieve the right section, not just the page.
Technical launch checks
- XML sitemap contains only canonical, indexable URLs.
- Robots.txt does not block public CSS, JS, images or key pages.
- Canonical tags point to the final URL, not staging or old slugs.
- Redirects return one clean 301 hop with no chains.
- Core Web Vitals are tested on mobile before launch.
- Schema matches visible page content.
- Forms, phone links and analytics events work after deployment.
Post-launch monitoring
After launch, submit the sitemap in Search Console, test important redirects, inspect priority URLs and watch the Coverage, Pages and Performance reports for two to four weeks. Temporary movement is normal; missing pages, redirect chains and canonical mistakes are not.
If the current site is mostly sound and does not need a full rebuild, read website refresh vs rebuild before committing to a bigger scope.
WordPress redesign SEO FAQs
Not if the redesign preserves useful content, maps changed URLs with 301 redirects, keeps metadata and schema aligned, and monitors Search Console after launch.
Only when there is a clear benefit. Keeping strong URLs is usually safer. If a URL must change, map it to the closest matching new page with a 301 redirect.
Check redirects, indexability, sitemap, canonicals, Core Web Vitals, schema, forms, analytics and Search Console performance for priority pages.
Planning a redesign without losing rankings?
We redesign WordPress websites with URL mapping, SEO foundations, speed and content parity handled before launch.