Educational Consultant Website Redesign and SEO Migration: A Safe Checklist

Overview

A redesign is a marketing project and a migration project.

If the current educational consulting site already ranks for useful queries, receives referral traffic or has links pointing to service pages, changing the design without a migration plan can erase value that took years to build.

The safest redesign starts with an inventory, not a blank canvas.

1. Crawl or inventory the current site

Create a list of existing URLs.

Include:

For each page, record:

• homepage;
• service pages;
• package pages;
• About;
• testimonials;
• consultation page;
• resources;
• guides/articles;
• location pages;
• contact;
• high-value legacy pages.
• current URL;
• title;
• purpose;
• whether it receives meaningful traffic or enquiries;
• whether it should keep, merge, redirect or retire.

2. Protect pages that already serve a search intent

A redesign is not a reason to rewrite every URL.

Keep a strong URL when:

Changing /college-admissions-consulting to /services/college-help may look cleaner internally while harming accumulated search equity.

Change URLs only when there is a real reason.

• the topic is still relevant;
• it ranks or earns impressions;
• it has external links;
• it converts;
• the service still exists.

3. Map one primary page to each intent

Before redesigning, identify the owner for:

Avoid creating multiple near-identical pages that compete.

• broad educational consulting;
• college admissions consulting;
• each major service;
• consultation booking;
• location intent if relevant;
• About/credentials.

4. Decide what to merge

Old sites often accumulate thin pages.

Possible merge candidates:

When merging, redirect the retired URL to the closest relevant surviving page.

Do not send every old URL to the homepage.

• duplicate service descriptions;
• outdated package pages;
• old team bios;
• city pages with no unique content;
• articles that repeat the same topic.

5. Prepare a redirect map before launch

For every changing URL, define:

Old URL → New URL

A good redirect points to the most relevant replacement.

Examples:

/services/senior-package → /services/comprehensive-senior-admissions

/book-a-call → /consultation

Do not rely on post-launch memory.

6. Preserve titles and metadata deliberately

During redesign, review:

Do not let template defaults replace optimized titles with generic text.

• page title;
• meta description;
• H1;
• internal links;
• canonical URL;
• indexability.

7. Rebuild the consultation path early

The new design is not finished if the conversion path breaks.

Test:

OneStudio supports contact forms/enquiries, website booking on applicable plans and related client workflows. See Features and Pricing.

• enquiry forms;
• direct consultation booking;
• service selection;
• availability;
• payment/deposit where enabled;
• confirmation;
• reminders.

8. Keep Google Calendar assumptions out of the design

If the practice uses Google Calendar, test the real integration.

OneStudio's current Privacy Policy says the connection creates a separate work calendar for the business and manages OneStudio booking events inside that OneStudio-created calendar. It does not read or change the Google account's personal calendar or other calendars.

Do not design the booking flow on the assumption that personal-calendar events will block availability. Test the actual OneStudio availability rules and work-calendar sync before launch.

9. Migrate proof carefully

Review:

A redesign is a good time to remove:

• testimonials;
• credentials;
• professional memberships;
• logos;
• student/family attribution;
• case studies.
• outdated affiliations;
• testimonials without clear permission;
• stale claims;
• unsupported acceptance statistics.

10. Protect privacy during content migration

Old CMS systems sometimes contain non-public form data or internal drafts.

Do not move private student information into the new website simply because it exists in the old system.

Separate:

Move each into the appropriate system.

• public website content;
• business contact records;
• private student/admissions records.

11. Test the mobile conversion flow

Before launch, test on a phone:

A redesign that looks excellent on desktop but makes the CTA hard to use on mobile is not ready.

• homepage;
• services;
• credentials;
• consultation CTA;
• form;
• calendar;
• confirmation;
• email links;
• phone links.

12. Verify analytics and search tools

Before and after launch, confirm:

Do not assume measurement survives a domain, platform or URL change.

• Search Console property;
• sitemap availability;
• analytics;
• robots/indexing behavior;
• key conversion tracking where used.

13. Launch with a monitoring list

For the first days and weeks, check:

Search performance naturally fluctuates. Look for structural problems, not one-day noise.

• 404 errors;
• redirect mistakes;
• lost pages;
• indexing changes;
• form submissions;
• booking failures;
• unusually large traffic drops;
• broken internal links.

14. Avoid changing everything at once

If possible, separate:

Doing all of them at once makes diagnosis much harder.

• platform migration;
• domain change;
• full URL rewrite;
• brand rename;
• content overhaul.

Migration checklist

CTA

Redesign the website without casually throwing away the search value already earned.

Use OneStudio website and booking tools, review current plans, and treat redirects and content ownership as part of the build.