How to Outsource Website Redesigns Without Losing SEO Rankings

Your agency has won a website redesign project.

The client wants a more modern website, better mobile usability and a design that reflects where their business is today.

Your design team is ready. You've started planning the new pages and you're considering outsourcing development to a technical partner.

But there's something important to check before anyone starts rebuilding the website.

What happens to the client's existing Google rankings and organic traffic?

If the website already receives enquiries from search engines, a redesign needs more planning than a completely new website.

Changing URLs, removing useful content, restructuring navigation or accidentally blocking search engines can affect organic visibility.

That doesn't mean agencies should avoid redesigning established websites.

It means SEO needs to be considered from the beginning, not added to the launch checklist at the last minute.

In this guide, we'll explain how agencies can outsource website redesigns while reducing avoidable SEO risks, from the initial audit to redirects, staging, launch and post-launch monitoring.

Can a Website Redesign Affect SEO Rankings?

Yes.

A website redesign can affect search performance, even when the new website looks better and offers an improved user experience.

The impact depends on what changes.

For example, updating colours, typography and visual layouts while preserving important content and URLs may involve less SEO risk than changing the entire website structure.

A redesign that also changes the platform, URL structure, content and navigation introduces more variables.

Common SEO risks include:

• Removing pages that receive organic traffic
• Changing URLs without appropriate redirects
• Replacing useful content with shorter, less relevant copy
• Changing important page headings
• Removing internal links
• Accidentally applying noindex directives
• Blocking search engine crawlers
• Incorrect canonical tags
• Missing structured data
• Poor mobile usability
• Significant performance problems

Not every change causes a ranking decline.

Some redesigns can improve technical quality and user experience.

The objective is to understand which existing elements contribute to search visibility and plan changes carefully.

Why SEO Agencies Outsource Website Redesign Development

SEO agencies often identify website problems but don't always have the internal development capacity to fix them.

A client may need a redesigned WordPress website, a new Shopify storefront or a migration to another platform.

The SEO agency can provide the search strategy and technical requirements, while a development partner handles implementation.

This arrangement can also work for creative agencies that manage website design but need technical support.

Examples of outsourced redesign work include:

• WordPress website rebuilding
• Shopify theme redesigns
• Figma to website development
• CMS migrations
• Responsive frontend development
• Navigation restructuring
• Technical SEO implementation
• Redirect implementation
• Website testing and deployment

However, the development partner needs to understand which SEO requirements must be preserved.

A visually successful redesign isn't necessarily a successful migration.

1. Audit the Existing Website Before Development

The first step is to understand the website you're replacing.

Before creating a new structure, your agency should identify which pages currently attract visitors, generate enquiries and appear in search results.

Review Google Search Console

Where access is available, examine:

• Organic search clicks
• Search impressions
• Queries associated with important pages
• Pages receiving search traffic
• Indexing information
• Existing technical issues

Look beyond the homepage.

A service page or blog article may attract valuable traffic even if it isn't prominent in the current navigation.

Review Website Analytics

Analytics data may help identify pages associated with:

• Enquiries
• Purchases
• Form submissions
• Engagement
• Other business outcomes

Search Console and analytics answer different questions.

Search Console helps explain Google Search visibility, while analytics can provide information about what visitors do on the website.

Crawl the Existing Website

A website crawl can help identify:

• Existing URLs
• Page titles
• Meta descriptions
• Heading structures
• Canonical tags
• Internal links
• Redirects
• Indexing directives

The results provide a reference point for comparing the old and new websites.

Identify Important Pages

Create a list of pages that should receive particular attention during the redesign.

These might include:

• Main service pages
• Product categories
• Location pages
• High-performing blog posts
• Important landing pages
• Pages generating organic enquiries

The purpose is not to preserve every page unchanged.

It's to make informed decisions about what should remain, change, merge or be removed.

2. Preserve Existing URLs Where Practical

One of the simplest ways to reduce migration complexity is to retain existing URLs when they still make sense.

For example, suppose the current website has:

example.com/services/website-design

If the redesigned website still offers the same service, there may be no reason to change the URL.

Keeping it can avoid the need for a redirect and reduce unnecessary changes.

When URL Changes May Be Appropriate

Sometimes URLs need to change because:

• The website structure is being reorganised
• The existing URLs are unclear
• The business has changed its services
• Pages are being consolidated
• The platform imposes different URL requirements
• The content has moved to a more appropriate location

When a change is necessary, document it.

Avoid changing URLs simply because a different version looks slightly cleaner.

3. Create a URL Mapping Document

If URLs will change, prepare a mapping document before launch. For guidance on site structure migrations, review the official Google Search Central: Site moves with URL changes documentation.

A URL map connects each relevant old URL with its intended destination.

For example:

These URLs are illustrative.

The destination should be relevant to the content and user intent of the original page.

Avoid Redirecting Everything to the Homepage

Redirecting unrelated pages to the homepage is generally not a good migration strategy.

It may create a poor user experience and may not preserve the value associated with the original content.

If a page has a suitable replacement, redirect it there.

If it has no relevant replacement, evaluate whether it should remain available, be consolidated or return an appropriate HTTP status.

Use Appropriate Permanent Redirects

For permanent URL changes, server-side 301 or 308 redirects are commonly appropriate. Consult Google Search Central: Redirects and Google Search for technical specifications.

The implementation depends on the platform and hosting environment.

Your development partner should test the redirects before or during launch.

4. Preserve Valuable Content

A redesign often involves rewriting website copy.

That can be beneficial when the existing content is inaccurate, outdated or poorly organised.

However, replacing useful content without reviewing its search performance can create unnecessary risk.

For example, a service page may currently explain:

• Services offered
• Industries served
• Common customer questions
• Technical details
• Pricing considerations
• Service areas

If the redesigned page removes most of that information and replaces it with a short marketing paragraph, it may no longer address the same search queries.

What Agencies Should Do

Before approving new content:

• Identify the page's main purpose.
• Review relevant search queries.
• Understand the existing content.
• Decide what should be retained.
• Identify what needs updating.
• Review internal links.
• Ensure the new page still addresses the intended topic.

You don't need to preserve every sentence.

You do need to consider why the page was useful in the first place.

5. Review Website Navigation and Internal Linking

Website redesigns frequently change menus, page hierarchy and footer links.

These changes can affect how visitors and search engines discover content.

For example, a service page that previously received links from the homepage and several other pages might become difficult to find after the redesign.

Internal Linking Checklist

Review:

• Main navigation
• Footer links
• Service page links
• Related content links
• Blog-to-service links
• Breadcrumb navigation
• Links to important location pages

Important pages should remain discoverable through relevant internal links.

Avoid creating pages that can only be accessed through the XML sitemap.

The development brief should include navigation requirements and any important internal linking instructions.

6. Include SEO Requirements in the Development Brief

When outsourcing a redesign, don't assume the developer knows which existing SEO elements must be retained.

Provide a clear technical brief. You can follow our website development brief guide to document these requirements thoroughly.

Essential Requirements to Discuss

• Page titles and meta descriptions: Specify which metadata should be retained, updated or made editable.
• Heading structure: Ensure the implemented page structure reflects the intended content hierarchy.
• Canonical tags: Confirm that canonical URLs point to the appropriate versions of pages.
• Indexing directives: Identify pages that should be indexable and pages that should remain excluded.
• Structured data: Review any relevant existing structured data and determine what should be implemented on the new website.
• XML sitemap: Confirm the sitemap reflects the intended indexable URLs.
• Internal linking: Provide important linking requirements.
• Redirects: Share the approved URL mapping document.
• Mobile usability: Define responsive requirements.
• Performance: Include reasonable performance requirements based on the project's scope.

A developer can implement these requirements more reliably when they're documented before development begins.

7. Use a Staging Website Carefully

A staging environment allows your agency and development partner to review the redesigned website before replacing the live version.

It can be used for:

• Design review
• Responsive testing
• Functionality testing
• Content review
• SEO checks
• Integration testing
• Client approval

However, staging environments need appropriate access and indexing controls.

Prevent Unintended Indexing

A publicly accessible staging site can create problems if search engines discover and index its pages.

Suitable protection may include authentication or other access restrictions.

A noindex directive can be useful in some circumstances, but it shouldn't be treated as a complete security measure.

Check Before Launch

Ensure staging-specific settings don't accidentally carry over to the live website.

Common problems include:

• Noindex directives
• Incorrect canonical URLs
• Links pointing to staging
• Staging URLs in sitemaps
• Incorrect asset paths
• Test forms or integrations
• Placeholder content

These checks should be part of the launch process.

8. Handle WordPress Redesigns Carefully

WordPress is widely used for agency website projects, but redesigns can involve different technical approaches.

An agency might:

• Replace an existing theme
• Rebuild templates
• Move from a page builder to another approach
• Introduce custom blocks
• Reorganise content
• Change hosting
• Migrate to a new WordPress installation

Each approach can affect the website differently.

WordPress SEO Considerations

Check:

• Permalink settings
• SEO plugin configuration
• Canonical output
• XML sitemap
• Redirect rules
• Page and post URLs
• Taxonomy pages
• Image URLs
• Internal links
• Indexing settings

If the project involves replacing plugins or changing how content is stored, review what information needs to be transferred.

A WordPress redesign should include a clear plan for content and SEO settings, not just theme implementation.

9. Plan Shopify Redesigns Around Existing Store Structure

Shopify redesigns may involve changes to:

• Theme templates
• Product pages
• Collection pages
• Navigation
• Content pages
• Apps
• Structured data
• Internal links

A theme redesign doesn't necessarily require changing existing product and collection URLs.

Where URLs or content do change, review the SEO implications.

Ecommerce Pages to Review

• Important product pages
• Collection pages
• Product descriptions
• Category content
• Blog articles
• Internal links
• Product structured data
• Canonical settings

Also test the customer journey.

A redesigned ecommerce website needs to function correctly, not just preserve search visibility.

10. Test the Website Before Launch

Your agency should review the new website against the existing site and the approved development requirements.

Technical SEO Checks

• Important pages return the expected HTTP status
• Canonical tags are correct
• Indexing directives are appropriate
• Internal links work
• Redirects are configured
• XML sitemap is correct
• Robots directives are reviewed
• Structured data is valid where implemented
• No unintended staging URLs remain
• Important content is present

Website Functionality Checks

• Forms work
• Navigation works
• Mobile layouts are usable
• Required integrations work
• Buttons and interactive elements behave correctly
• Important images load
• Contact details are correct

Analytics Checks

• Required analytics implementation is present
• Important events are configured as agreed
• Form or conversion tracking is tested
• Relevant consent requirements are considered

Testing responsibilities should be agreed before the project reaches the launch stage.

11. Prepare a Website Redesign Launch Plan

A website launch should be treated as a coordinated process.

Your agency and development partner should know who is responsible for each task.

Before Launch

• Approve final content and designs
• Complete functional testing
• Review technical SEO requirements
• Confirm redirect mapping
• Prepare appropriate backups or recovery options
• Confirm analytics requirements
• Agree on launch responsibilities

During Launch

• Deploy the approved website
• Verify important pages
• Test redirects
• Confirm indexing settings
• Check canonical tags
• Test forms and integrations
• Verify important navigation links
• Check live analytics implementation

After Launch

• Crawl the live website
• Review important URLs
• Submit or update the sitemap where appropriate
• Monitor Search Console
• Review analytics
• Investigate unexpected errors
• Confirm redirects continue working

The exact launch plan will depend on the website platform and hosting environment.

12. Monitor SEO Performance After the Redesign

A redesign project shouldn't end immediately after the website goes live.

Your agency should monitor search visibility and technical issues.

Google Search Console

Review:

• Search clicks
• Impressions
• Important queries
• Important landing pages
• Indexing reports
• Crawl-related issues

Website Analytics

Review:

• Organic landing pages
• Enquiries or purchases
• Relevant conversion events
• Changes in visitor behaviour

Technical Monitoring

Check for:

• Broken internal links
• Unexpected 404 responses
• Redirect errors
• Incorrect canonical tags
• Indexing problems
• Missing content
• Important performance issues

Compare Equivalent Periods

When reviewing performance, account for factors such as:

• Seasonality
• Changes in demand
• Marketing campaigns
• Search engine updates
• Changes in the website's content
• Differences in measurement

A short-term ranking movement doesn't always indicate that the redesign caused a lasting problem.

Investigate changes using the available evidence rather than assuming every movement has the same cause.

13. What If Rankings Drop After Launch?

If organic visibility declines, begin with a structured investigation. For diagnostic steps, see Google Search Central: Debugging drops in Google Search traffic.

Check Indexability

Make sure important pages can be crawled and indexed as intended.

Check Redirects

Confirm that changed URLs redirect to appropriate destinations.

Compare Old and New Content

Review whether important topics or sections were removed.

Review Canonicals

Make sure the canonical tags reference the intended URLs.

Inspect Internal Linking

Check whether important pages have lost relevant internal links.

Review Search Console

Look for indexing problems, affected pages and changes in query visibility.

Check Technical Changes

Investigate server responses, rendering problems and other implementation issues.

Avoid making large numbers of speculative changes at once.

Identify likely causes, prioritise confirmed problems and monitor the results of corrections.

14. How to Work With a White Label Development Partner on SEO-Sensitive Redesigns

If your agency provides white label SEO services or design but outsources development to a technical partner, define the responsibilities clearly.

For example:

This is an example allocation, not a mandatory division of work.

The important point is that each task has a clear owner.

A good development brief should make these responsibilities visible before the project begins.

Website Redesign SEO Checklist for Agencies

Use this checklist before outsourcing a client redesign.

Common Website Redesign SEO Mistakes

Changing Every URL Without a Clear Reason

Unnecessary URL changes add migration work and risk.

Removing Content Without Reviewing Its Performance

Useful pages may support important search queries and enquiries.

Redirecting All Old Pages to the Homepage

Redirect destinations should be relevant to the original content.

Forgetting Internal Links

Important pages may become harder to discover after navigation changes.

Leaving Noindex on the Live Website

Staging-related settings should be reviewed before launch.

Launching Without Testing Redirects

Incorrect redirects can affect both visitors and search engines.

Ignoring Analytics

Without reliable measurement, it becomes harder to evaluate the redesign.

Treating Launch as the End of the Project

Post-launch monitoring is an important part of an SEO-sensitive redesign.

Frequently Asked Questions

Does redesigning a website affect SEO?

It can. The impact depends on changes to URLs, content, internal links, technical configuration and other factors.

Can a website be redesigned without losing Google rankings?

A careful redesign can reduce avoidable SEO risks, but no agency can guarantee that rankings will remain unchanged.

Should URLs stay the same during a redesign?

Where practical and relevant, retaining existing URLs can reduce migration complexity. Changes should be planned and redirected appropriately.

Are 301 redirects necessary during a website redesign?

Permanent redirects are generally appropriate when existing URLs move permanently to new, relevant destinations.

Can SEO agencies outsource website redesign development?

Yes. SEO agencies can manage the strategy and requirements while a development partner handles agreed technical implementation.

What should developers know before redesigning an SEO-performing website?

They should receive information about important URLs, content, redirects, internal linking, metadata, indexing requirements and launch responsibilities.

Does changing a WordPress theme affect SEO?

It can affect technical implementation, content presentation, performance and other elements. The actual impact depends on what changes.

Can a Shopify redesign affect organic traffic?

Yes. Changes to templates, content, navigation, internal links and technical settings can influence search performance.

How long should agencies monitor SEO after a redesign?

Monitoring should begin immediately after launch and continue long enough to evaluate technical issues and search performance trends. The appropriate period depends on the website and scope of changes.

Should the SEO agency or development partner handle redirects?

Either can be responsible, depending on the agreement. The important point is that redirect mapping, implementation and testing have clearly assigned owners.

Need a Development Partner for a Client Website Redesign?

If your agency has a website redesign project and needs technical delivery support, White Label Agency can review your requirements.

We work with agencies outsourcing WordPress, Shopify, WooCommerce and custom website development. Learn more about how our white label process works.

If your client already receives organic traffic, share the relevant SEO requirements alongside the approved designs and development brief.

We can discuss the technical scope, responsibilities and implementation process before work begins.

Our services are intended for agencies outsourcing development work for existing client projects, not freelancers seeking work or agencies looking for new customers.