Marketing website redesign and SEO: what to preserve, improve, and measure

A marketing website redesign should help the right visitor understand your offer and complete a useful next step. Search visibility, page clarity, mobile usability, and enquiry handling belong in the same scope. A new visual design cannot compensate for missing service information or a form that never reaches its owner.

Before choosing a template or commissioning a rebuild, identify what the existing site already does well. Preserve useful URLs and content, inspect measurable problems, and define the business outcome you want to observe after launch.

Establish a baseline and a buyer journey

Inventory service pages, articles, contact paths, and downloadable resources. Use available analytics, Search Console, server responses, and actual enquiries to identify important entry pages. When data is missing, document the gap instead of treating assumed traffic or conversion rates as facts.

Choose the audience and decision each priority page should serve. A buyer comparing implementation partners needs to understand the problem you handle, scope boundaries, evidence, engagement process, and next step. A visitor researching a specific question may need a useful explanation before considering a service.

Define a qualified enquiry in terms your team can apply consistently. A form submission and a viable project are different measurements. Record changes to tracking or qualification so you can interpret before-and-after results honestly.

Separate content, usability, and technical problems

Content work clarifies who a service is for, what it includes, what the buyer must provide, and how an engagement starts. Use specific examples and verified evidence. Label demonstrations as illustrative and avoid turning unsupported performance claims into testimonials.

Usability work makes that information easy to find and act on. Test the page on a small screen, with a keyboard, and with a person unfamiliar with the business. Forms need useful labels, understandable errors, confirmation, and a recovery path if a scheduling widget fails.

Technical work checks that each important URL returns the intended page, has a clear identity, links to related content, and is accessible to crawlers. Google's SEO Starter Guide explains how accessible content and understandable site organization support search discovery. These practices do not guarantee indexing or rankings.

An illustrative service-company redesign

Consider an illustrative consulting company whose home page leads with a large animation, while its service pages contain only broad promises. Mobile visitors must scroll a long way to learn what the company delivers. Its enquiry form sends email but provides no durable handoff record. This is a design scenario, not a customer result.

A useful scope could rewrite three core service pages around buyer questions, put a concise offer and next step near the top, simplify the form, and connect accepted submissions to a tracked CRM enquiry. The existing useful article URLs remain available.

The launch acceptance test would cover page responses, navigation, mobile forms, tracking, and enquiry delivery. The business would then review qualified enquiries over a meaningful observation period. The redesign can remove obstacles; it cannot promise a particular number of new customers.

Protect search access during the transition

Keep useful URLs where possible. If a page must move, map its old URL to the closest relevant replacement before launch. Do not send every removed page to the home page simply to avoid visible errors.

Google's site-move documentation recommends URL mapping, permanent server redirects, updated internal links, and checking canonical and indexing rules. Apply those instructions to actual changes in your migration rather than assuming every redesign requires a new URL structure.

Check representative pages as direct requests, not only through clicks within the application. Verify that article links, service pages, images, and contact URLs work after a refresh. Confirm that production does not retain staging restrictions. Make rollback and post-launch monitoring part of the delivery agreement.

Choose a platform that supports the work

Configure the current content system when it can deliver usable pages, sound metadata, reliable forms, and manageable editing. A purchased theme can be sufficient when it fits your content and performance needs without extensive workarounds.

A rebuild may be justified when the existing system prevents reliable delivery or necessary user journeys. Custom development is more relevant for unusual interactions, integrations, or product functions than for reproducing ordinary page layouts. Compare editing access, hosting, dependency maintenance, and ownership alongside initial design effort.

Ask who will publish articles, update services, review form failures, and maintain integrations. A technically flexible site can still become expensive if every text correction requires a developer. The software ownership guide provides a broader decision framework.

Measure performance and enquiry completion

Assess loading, responsiveness, and layout movement on representative devices. Google's Web Vitals documentation explains these experience measures and distinguishes field measurement from development checks. A high lab score is useful diagnostic evidence, but it does not establish that visitors understand the offer or become qualified leads.

Track the enquiry journey through successful delivery, not just a button click. A form can report success while an integration fails downstream. For connected lead handling, use the controls described in the CRM integration guide.

Compare relevant search impressions and clicks, meaningful form completions, qualified enquiries, and sales follow-through. Allow for seasonality, traffic mix, campaign changes, and low sample sizes when interpreting results.

Checklist for comparing redesign proposals

List priority audiences, pages, and conversion actions.
Record existing URLs, baseline measurements, and tracking gaps.
Include copy and information architecture alongside visual design.
Define redirects and content preservation before migration.
Require mobile, keyboard, form, and direct-URL checks.
Verify enquiry delivery, failure alerts, and a manual contact alternative.
Confirm editing ownership, hosting access, maintenance, and recurring costs.
Specify launch acceptance, rollback responsibilities, and post-launch review.

Cost depends on content volume, research, visual complexity, migration, integrations, accessibility work, and the condition of the existing site. A marketing website assessment can separate urgent repairs from changes that need a larger redesign.

Frequently asked questions

Do we need to change every URL for SEO?

No. Preserve useful URLs unless there is a clear reason to change them. Where changes are necessary, create relevant mappings, implement redirects, and update internal references. URL changes add migration work and should solve an actual problem.

Should we publish more articles before redesigning?

First check whether existing pages are accessible, understandable, and connected to a useful next step. New content can support specific buyer questions, but increasing volume does not resolve broken delivery or unclear services.

How will we know whether the redesign worked?

Agree on business and technical measures before implementation. Verify delivery at launch, then review qualified enquiry behavior with enough context and observation time. Report uncertainty when traffic is limited or other business changes affect the comparison.