A newly designed website can look considerably better than the one it replaces and still be worse for your business. A service page that used to attract qualified enquiries may disappear, an old URL may stop working, or a form may look polished while silently failing to deliver messages. Your developers may call the launch successful because every page loads. Your sales team may tell a different story two weeks later.

A website redesign is not merely a visual project. It is a change to an existing customer acquisition system. The safest approach is to preserve what already works, test what is changing, and agree in advance what evidence must exist before the new site goes live.

Key takeaways

• Keeping existing URLs, where practical, reduces the number of search signals that need to be transferred during a redesign.
• Where URLs must change, map old URLs to relevant replacements and use server-side permanent redirects.
• A launch-ready website needs working contact journeys and analytics, not just clean visuals and SEO metadata.
• Google warns that rankings and traffic can fluctuate during URL migrations; measure trends and investigate technical errors rather than promising zero disruption.
• Use explicit launch ownership, blocking criteria, a rollback plan and post-launch monitoring to protect business continuity.

First identify what kind of redesign you are planning

Not all redesigns carry the same SEO risk. Changing colours, layout and imagery while retaining URLs and substantive content is different from replacing a WordPress installation, rebuilding category structures or moving to another domain. The more search-facing signals you change at once, the harder it can be to diagnose what caused a performance shift.

Google provides separate instructions for moves with URL changes and hosting changes without URL changes. For a domain migration it recommends the Change of Address tool in Search Console; that step is not necessary for ordinary path changes within the same domain. Read Google’s site migration guidance.

The overlooked risk: protecting enquiries, not just rankings

Suppose a hypothetical Nairobi consulting firm receives 20 qualified enquiries each month through a service page. The redesign replaces the page with a more attractive template but removes the old URL and sends its contact form submissions to an inactive email address. In the first month, the firm loses two opportunities while the redesigned homepage performs perfectly in a visual review. The exact figures here are illustrative, not measured SEO Consulting Kenya client results.

This example matters because search visibility, website interaction and commercial response form a chain. Preserving rankings without preserving enquiries can still damage the business. A realistic pre-launch baseline should therefore include the pages customers use, the way they contact you and the process by which staff respond.

The 30-point website redesign SEO checklist

Use the checklist below with your developer, SEO consultant and business owner. Treat each item as complete only when there is evidence: a crawl output, source URL, test result, screenshot, working form submission or documented approval. A checked box without proof is not a meaningful control.

Phase 1: Protect the existing website before design begins

• 1. Export a complete list of current URLs, including service pages, products, articles, downloads and important landing pages.
• 2. Record a Search Console baseline by page and search query, using a representative period and noting seasonality.
• 3. Capture verified enquiries, form submissions, calls and sales data before the redesign so commercial performance can be compared.
• 4. Identify pages that earn meaningful organic traffic, qualified leads or external links; mark them for preservation or special handling.
• 5. Save page titles, headings, copy, metadata, structured data, canonical rules and internal links from priority pages.
• 6. Confirm a tested site backup, restoration route, owner of DNS and hosting access, and a named person authorised to approve launch.

Phase 2: Plan the new architecture and redirects

• 1. Decide which URLs can remain unchanged; retaining a working URL usually removes unnecessary migration risk.
• 2. Create an old-to-new URL map for every URL being changed, including documents and URLs reached from external links.
• 3. Choose the closest relevant replacement for each changed page; avoid sending unrelated retired URLs to the homepage.
• 4. Document legitimate removals that should return 404 or 410 rather than inventing irrelevant redirects.
• 5. Check that important services, locations and product categories still have suitable landing pages and are easy to navigate.
• 6. Assign one person to own URL mappings, another to validate SEO and an accountable launch decision-maker; record dependencies.

Phase 3: Audit and test the staging website

• 1. Restrict staging from public indexing and verify that its staging-only access or indexing restrictions will not be copied to production.
• 2. Compare the text and search intent of priority old and new pages; investigate material content loss or changes in targeting.
• 3. Check new canonical tags, indexability rules, structured data, headings, mobile layouts and important internal links.
• 4. Test a representative sample of redirects and error handling in a controlled environment, then prepare full-volume testing for launch.
• 5. Submit test enquiries through forms, phone links and WhatsApp on both mobile and desktop, and confirm delivery to staff.
• 6. Validate analytics events, conversion definitions, consent handling, performance, accessibility and third-party integrations.

Phase 4: Apply go/no-go controls on launch day

• 1. Take a fresh production backup, agree a maintenance window and define exactly which failures trigger an emergency response.
• 2. Deploy the approved redirect map and test old high-value URLs against their final destinations and HTTP status codes.
• 3. Remove staging-only noindex or crawl blocks from intended public production pages, while keeping private areas protected.
• 4. Validate production canonical URLs, XML sitemap contents, navigation links, robots.txt and essential structured data.
• 5. Complete live end-to-end tests of forms, WhatsApp, telephone, checkout or quote flows and analytics measurement.
• 6. Have the authorised launch owner sign off critical technical and commercial tests before declaring the move complete.

Phase 5: Monitor performance and complete the handover

• 1. Submit the updated sitemap and use Search Console’s Change of Address tool if you actually moved to a different domain or subdomain.
• 2. Monitor Page Indexing, URL Inspection and redirect errors; investigate unexpected 404s, soft 404s and noindex signals.
• 3. Compare relevant search impressions and clicks against the baseline using consistent page groups, dates and context.
• 4. Reconcile received leads, calls, form submissions and orders with analytics events; escalate missing enquiries immediately.
• 5. Keep permanent redirects in place for the long term, generally at least one year per Google’s migration guidance.
• 6. Hand over the redirect map, access ownership, change log, test evidence, known issues, recovery instructions and monitoring responsibilities.

The launch go/no-go matrix

Many migration checklists say to test everything. Fewer explain what happens when something fails. A practical control is to classify defects by the business consequence and prevent launch when unresolved defects could interrupt customer journeys or indexing.

This matrix is an editorial decision tool, not an official Google risk classification. The severity of a problem depends on site size, industry, regulatory obligations and the exact functionality affected. For an e-commerce store, a broken checkout is clearly a blocker; for a brochure site, a broken quotation form may be equally serious.

Redirects are not an invitation to erase your existing information architecture

When a page moves permanently, Google recommends a server-side permanent redirect such as 301 or 308. However, the destination must remain relevant. Sending every retired service or article URL to the homepage can confuse people and may be treated as a soft 404. If no reasonable replacement exists, an accurate 404 or 410 status can be preferable to a misleading redirect.

A redirect map should record the old URL, the proposed new URL, the reason for the change, its business priority and its tested status. Where a page has strong search visibility or valuable inbound links, ask why its URL needs changing at all. Preserving a useful existing address may be simpler than attempting to repair the consequences.

Google advises keeping permanent migration redirects for as long as possible, generally at least one year; longer is often sensible for users who may follow older bookmarks or external links. It also recommends updating internal links to point directly to the new URLs.

A special WordPress and Elementor pre-launch review

WordPress redesigns introduce additional failure modes. New themes or Elementor templates may output different headings, breadcrumbs, canonical tags or duplicate page content. SEO plugin settings may not carry over as expected. A migration can also bring across outdated plugins, media URLs and incorrect WordPress Address settings.

• Check each priority page in the actual rendered output, not only the visual editor preview.
• Confirm that the SEO plugin is active and its title, canonical, sitemap and indexing settings are correct.
• Check that both mobile and desktop templates preserve meaningful content and accessible calls to action.
• Review caching, CDN, redirects and HTTPS rules for conflicts or redirect chains.
• Test form delivery, spam protection, transactional email, WhatsApp links and any CRM integrations.
• Validate that staging URLs are not referenced as canonical URLs or embedded in important image and internal links.
• Confirm the correct production domain and that temporary site-wide indexing restrictions have been lifted.
• Retain a working backup and document plugin, theme, PHP and database changes.

Avoid publishing the new design and changing the entire domain, navigation hierarchy, URL structure and content strategy at once unless the project genuinely requires it. Sequencing changes can make failures easier to identify and resolve.

What to monitor after the redesigned website goes live

Do not judge the launch on first-day rankings. A short-term fluctuation can occur as Google discovers and processes changed URLs. Instead, separate immediate operational checks from longer-term search results.

These review intervals are practical planning suggestions, not a timetable Google guarantees. Some sites process URL migrations in weeks, while larger or more complex sites may need longer. Search Console and Analytics data also have different collection and reporting properties, so compare like with like.

What should a rollback plan actually contain?

Before changing production, document how to recover both the website and its customer-facing functions. Identify who can restore application files and databases, who controls DNS, where backups are stored, what configuration will be restored and how new submissions or orders created after launch will be protected. Reverting a database blindly can erase legitimate post-launch enquiries or transactions.

A rollback is not always the safest response to every SEO fluctuation. If the new site is functioning and only a few redirects are wrong, correcting those redirects may be less disruptive than reverting the entire project. Escalate decisions based on severity and evidence, not anxiety about a single chart.

An original project handover test: can the business operate without the developer?

A redesign is operationally complete when its owner can manage essential content, receive enquiries, access analytics and recover from common failures. Ask for an approved document listing administrator roles, hosting and domain ownership, backup procedures, redirect records, live forms, analytics accounts, important subscriptions and ongoing maintenance responsibilities.

For many Kenyan SMEs, the greatest hidden risk is dependence on a single developer account or an undocumented hosting arrangement. An attractive website is not a durable business asset if the owner cannot access it, maintain it or respond to an urgent problem.

Frequently asked questions

Will a website redesign make my Google rankings drop?

Not necessarily. Visual changes that preserve URLs, useful content and technical access may have limited SEO disruption. A major site migration can cause temporary fluctuations, and preventable technical errors can cause larger losses. No provider can honestly guarantee zero ranking movement.

Do I need 301 redirects if the URLs stay the same?

Usually not just because the design changes. Redirects are needed when an old address permanently moves to a different one. A hosting change that retains URLs requires infrastructure validation but does not inherently require URL redirects.

Should staging pages be indexed by Google?

Generally no: a staging copy should be restricted from public discovery or indexing while it is being developed. After launch, verify that intended production pages are accessible and not accidentally blocked. Password-protected staging is often safer than relying on a robots.txt rule alone.

How long does Google take to recover after a website migration?

There is no guaranteed recovery date. Google says small-to-medium URL moves can take weeks for many pages to be processed, and larger websites can take longer. Monitor whether changed pages are being discovered and indexed instead of measuring only a single ranking.

Can I redesign my WordPress site without losing content?

Yes, with appropriate planning and backups, but it should be verified rather than assumed. Audit pages, posts, downloads, images, metadata, Elementor templates, forms and integrations before replacing or migrating the site.

A successful redesign preserves the business behind the website

The strongest website redesign projects improve visual design and user experience without discarding the search visibility, customer journeys and operational knowledge already built into the old site. Give each important risk a named owner, require proof before launch and monitor the customer experience after the design goes live.

If your business is considering a redesign, explore SEO Consulting Kenya’s web design services and discuss your project before any major URL or platform changes. You can also begin with our free preliminary SEO audit for public page-level checks; a complete migration review requires a deeper crawl, performance baseline and access to site systems.

Sources and further reading

• Google Search Central: Site moves with URL changes
• Google Search Central: Hosting changes without URL changes
• Google Search Central: Redirects and Google Search
• Google Search Central: Debugging search traffic drops
• Related guide: Website Traffic but No Leads?