Business Consultant Website Redesign: SEO Migration Checklist

Overview

A consultant website redesign often starts with a visual complaint.

"The site feels old."

That may be true, but an established website also contains accumulated assets that are easy to destroy:

A good redesign changes what needs improvement without resetting everything else to zero.

• indexed URLs;
• search visibility;
• backlinks;
• referral links;
• case studies;
• service-page history;
• analytics;
• forms;
• booking links;
• domain and email records.

Start with an inventory before opening the editor

Create a simple spreadsheet with every important public URL.

Record:

Do not start by deciding that the new site needs only Home, About, Services and Contact.

That is how valuable old pages vanish.

• current URL;
• page type;
• title;
• main search intent;
• whether it receives search traffic;
• whether it has external links;
• whether people use it in proposals, email signatures or profiles;
• planned destination after redesign.

Identify the current canonical topics

A consultant site can quietly accumulate duplicate pages over time.

Examples:

If they all target the same buyer and same problem, the redesign is a chance to consolidate rather than recreate the duplication in a prettier layout.

For each topic, choose one owner.

• /operations-consulting
• /operational-excellence
• /process-improvement-consulting
• /business-operations

Separate three decisions: keep, improve, retire

Protect service pages that already earn attention

Consultants sometimes replace a detailed old service page with one paragraph on a new "Capabilities" page.

That can look cleaner while becoming less useful.

If a page already ranks, earns referrals or explains a distinct service, preserve enough depth to continue satisfying that intent.

The new design can be elegant without collapsing every concept into a landing page.

Keep case-study URLs stable when possible

Case studies may earn links from:

If the URL can remain unchanged, keep it.

If it must change, map the old case to the new case directly.

• client sites;
• industry articles;
• social posts;
• conference bios;
• newsletters;
• sales documents.

Review titles and headings before launch

A redesign can accidentally replace descriptive titles with brand-heavy language.

Before publishing, compare old and new:

A new title should still describe the service or topic.

• page title;
• meta description;
• H1;
• core H2s;
• copy depth;
• internal links;
• image alt text where relevant.

Preserve internal link logic

Old pages may link naturally between:

When the structure changes, update those links deliberately.

Useful internal linking helps a visitor and a crawler understand:

• services;
• case studies;
• industry pages;
• insights;
• consultation pages.
• what the firm does;
• which proof belongs to which service;
• where the next step lives.

Rebuild the discovery path, not only the pages

A redesign is incomplete if the new homepage looks better but the consultation path breaks.

Document the old flow:

page → CTA → form/calendar → confirmation → calendar/client record

Then document the new one.

If OneStudio is used, its online booking can connect the public booking path to service availability and client records.

Do not assume the platform automatically recreates:

Verify each dependency.

• old form logic;
• third-party scheduler rules;
• video links;
• complex qualification forms;
• redirects.

Protect domain and email records

The website and email often share the same domain.

Before changing DNS, save the current DNS zone and identify records for:

Changing the website should not silently break email.

Do not delete records simply because you do not recognize them.

• website hosting;
• MX;
• SPF;
• DKIM;
• DMARC;
• Search Console verification;
• analytics/verification tools;
• other business services.

Plan redirects in the system that controls them

If URLs change, the old URL should usually redirect to the most relevant new URL.

But do not claim OneStudio automatically imports or manages every redirect unless that exact behavior is verified for the project.

Your migration plan should state:

If redirect support must be handled elsewhere in the infrastructure, assign it there.

• old URL;
• new URL;
• redirect owner/system;
• status after launch;
• test result.

Keep analytics and Search Console continuity

Before launch, record:

After launch, verify:

Do not treat same-day ranking changes as a verdict. Migration effects can take time to settle.

• analytics property;
• Search Console property;
• verification method;
• sitemap location;
• key landing pages;
• current top queries/pages if available.
• tracking still fires;
• Search Console verification remains;
• sitemap is reachable;
• important URLs are indexable;
• old important URLs redirect correctly;
• new pages are discoverable from navigation/internal links.

Create a pre-launch test list

Test on staging or preview where possible.

Launch in a controlled sequence

A safer sequence is:

This sequence reduces the number of unknowns at once.

1. Freeze major content changes.
2. Take final URL/content inventory.
3. Test the new site.
4. Prepare DNS and redirect plan.
5. Confirm email records.
6. Publish/cut over.
7. Test critical pages immediately.
8. Test old URLs.
9. Test enquiry/booking.
10. Check analytics and Search Console.
11. Crawl the public site.
12. Watch errors and important landing pages.

What to monitor after launch

For the next days and weeks, check:

Do not change ten SEO variables at once in response to one bad day.

• 404 errors;
• redirect errors;
• missing images;
• form/booking failures;
• Search Console indexing changes;
• important query/page movements;
• broken internal links;
• sudden traffic loss to a specific old URL;
• bookings/enquiries from the site.

When a redesign is also a repositioning

Sometimes the firm has changed more than the website.

If you are moving from broad "business consulting" to a narrower specialization, decide explicitly:

SEO preservation does not mean preserving an old strategy forever.

It means changing it deliberately.

• which old services remain;
• which old pages should be consolidated;
• which case studies support the new position;
• which old audience should no longer be targeted;
• whether the domain still fits;
• how old referral links will resolve.

Redesign the experience without deleting the evidence

The goal is not to keep an old site frozen.

It is to preserve what already works while improving positioning, proof, usability and the path to a client conversation.

Use the new website as a controlled migration, not a blank-slate deletion.

Explore OneStudio features and service-business solutions.

Questions businesses ask