Website Redesign Checklist for Service Businesses: Do It Without Losing Your Google Traffic

A new website feels exciting and risky at the same time. The owner who has spent years collecting calls from Google fears that a prettier site will quietly lose them. That fear is justified: most traffic losses after a redesign are not caused by the design. They come from avoidable steps such as deleted pages, changed addresses without redirects, a leftover noindex setting or tracking that stopped firing. This checklist walks through the decision and the safe sequence, using Google Search Central's site move documentation as the technical backbone.

Should you redesign at all?

Not every weak website needs a rebuild. Use the table to match the symptom with the smallest fix that could work.

Google measures page experience with Core Web Vitals, and its web.dev guidance defines a good Largest Contentful Paint as within 2.5 seconds, a good Interaction to Next Paint as 200 milliseconds or less, and a good Cumulative Layout Shift as 0.1 or less, at the 75th percentile of page loads. See Web Vitals on web.dev. If your site fails these on mobile and cannot be repaired, that is a strong argument for a rebuild. Our Quality Score guide explains why landing page experience also matters for ads.

Phase 1: Record where you are today

1. Export your baseline. Save 12 months of Search Console data, your top landing pages, the queries that bring calls and your analytics reports.
2. List enquiry sources. Which pages produce calls, WhatsApp clicks and forms? Those pages are untouchable until proven replaceable.
3. Crawl the old site. Record every URL, title, heading, status code and internal link count. Include images, PDFs and scripts that other sites link to.
4. Gather old URLs from several sources. Google suggests sitemaps, the Search Console links report, high-traffic pages, CMS listings and server logs.
5. Screenshot the key pages so you can compare layout and content later.

Phase 2: Audit the content, page by page

A redesign is the best moment to decide what deserves to survive. Give each page one label.

Google's guidance says to return HTTP 404 or 410 for old content you are not carrying over, and warns against redirecting many unrelated old URLs to the home page. Redirect consolidated content to the matching consolidated page instead.

Phase 3: Plan the new structure around customers

Service-business sites win when structure mirrors how customers decide: services, areas, proof, prices in general terms, how to book. For each service create one page that explains who it is for, what is included, how the job works, what affects the price, photos of real work and a clear way to contact you. Add area pages only where you really work. Read our checklist for medical sites in clinic website essentials if you run a clinic; the principles of trust and clarity carry over to other sectors.

• Phone and WhatsApp buttons visible on every page on mobile without scrolling.
• One main action per page, repeated at natural points.
• Real photos and named proof where you have permission to use them.
• Both languages where needed, with matching pages and correct language annotations. Google's guidance says to update hreflang annotations to the new URLs.
• Fast templates that keep images compressed and scripts few.

Phase 4: Build the URL map

This table is the most important document in the project. Every old URL gets a destination. The examples are illustrative.

On each new page add a self-referencing canonical, update hreflang annotations and change internal links so they point to the new addresses directly. Save a sitemap of the new URLs. These are the preparation steps Google's documentation lists; read them in full at Google Search Central: site move with URL changes.

Phase 5: Redirect rules that protect traffic

• Use server-side permanent redirects, 301 or 308. Treat client-side redirects as a last resort.
• Redirect straight to the final destination; avoid chains. Google says to keep chains ideally under five hops.
• Redirect to the closest equivalent, not to the home page for everything.
• Small and medium sites should move all URLs at once.
• Keep redirects for at least a year, and longer if old links still bring visitors.
• Google states that permanent redirects do not cause a loss of PageRank, which is why they are central to the plan.

Phase 6: Tracking and conversions before launch

A site can rank well and still look broken if you cannot see its calls and chats. Before launch install and test the analytics tag, ad conversion tags, phone-call tracking and WhatsApp click events on the staging site. Keep the same phone numbers and verification tags for Search Console. Our conversion tracking service and guide to tracking calls and WhatsApp leads cover how to count real enquiries. If you run ads, update their final URLs the day the new pages go live and compare with your plan for landing pages.

Phase 7: Launch-day checklist

• Remove any noindex tag or password protection used on staging; Google also says to remove development-only robots.txt blocks.
• Confirm HTTPS is working and certificates are valid.
• Test a sample of old URLs and confirm they reach the right new URL in one hop.
• Check canonicals point to new URLs, and forms, buttons and call tracking work on real phones.
• Submit the new sitemap in Search Console and remove the old one. Warnings about redirecting URLs in the old sitemap are expected.
• Update your Google Business Profile website link, social profiles and ad campaigns.
• If the domain itself changed, submit Change of Address; it is not needed for HTTP to HTTPS, www switches or path-only changes.

Phase 8: The first 30 days after launch

Google says a medium-sized site can take a few weeks or more for new URLs to gradually replace old ones, that temporary fluctuations are normal, and that old-site traffic should fall as new-site traffic rises. Check Search Console daily in week one: crawl errors, indexed pages, sitemap status and top queries. Compare calls and WhatsApp enquiries with your baseline and look at server logs for unexpected error codes. Fix patterns, not single pages: if a whole folder returns errors, the rule is wrong.

A hypothetical example

The numbers are invented to show the process, not results. A cleaning company has 40 pages. The audit finds 12 pages that bring most calls, 14 thin or duplicate pages, 8 obsolete posts and 6 average pages. The team keeps the 12, rewrites 6, merges the 14 into 5 stronger pages and removes the 8 with 410 responses. The URL map shows 31 redirects. At launch two redirects point to a retired page and a form tracking tag is missing. Because the checklist included testing sample redirects and form events, both are fixed on day one. In a rushed project, the same two errors might run for weeks.

Mistakes that cause the biggest losses

• Deleting pages that still bring enquiries.
• Redirecting everything to the home page.
• Forgetting to remove noindex after staging.
• Changing domain, design and URLs together.
• Launching with untested forms or WhatsApp buttons.
• Losing Search Console and analytics access.
• Judging success only by rankings instead of calls and bookings.

What affects the cost and timeline

We do not quote prices here because they depend on scope. The main drivers are the number of pages and languages, the amount of new content and photography, integrations such as booking or CRM, the platform you build on, and the testing and migration work. A project with clear content and a fast approver is quicker and cheaper than one that stalls waiting for text. For a sense of how we approach builds, see web design in Dubai and our website service.

How we work at ZED

ZED Marketing describes the website as part of a system rather than a decoration: a fast, persuasive, conversion-ready site built to support advertising and mobile visibility on Google, connected to content, ads, SEO and tracking. Our approach is to start from the outcome you want, such as calls, WhatsApp messages and bookings, and build the pages and tracking around it. If you want to see how we present proof for a service sector, read our furniture showrooms case study, and for search visibility see our SEO service.

Website redesign FAQs

When should a service business redesign its website?

Redesign when the site actively blocks enquiries: it is hard to use on mobile, loads slowly, cannot be edited, hides your services or contact options, or no longer matches the business. If the site mainly needs new content, a fixed form or better tracking, a targeted fix is cheaper and safer than a full rebuild.

Will a redesign hurt my Google rankings?

It can if URLs change without redirects, content is removed, or pages are blocked from indexing. Google states that temporary ranking fluctuations are normal during a site move, and that permanent server-side redirects do not cause a loss of PageRank. A careful URL map and redirects reduce the risk, but nobody can promise that rankings will be unchanged.

Do I need 301 redirects if only the design changes?

If every URL stays exactly the same, no redirects are needed for those pages. You need redirects whenever a URL changes, for example when you switch from .html addresses to clean addresses, rename a service or merge pages. Google recommends server-side permanent redirects (301 or 308) from each old URL to its new equivalent.

How long should I keep redirects?

Google's site move guidance says to keep redirects for at least one year in general, and keeping them indefinitely is also an option. Do not remove them as soon as traffic looks normal, because old links and bookmarks still point to the old addresses.

Do I need the Change of Address tool?

Google says the tool is for moves to a different domain or subdomain. It is not needed for HTTP to HTTPS moves, www and non-www switches or changes that only affect paths. Check the current documentation for your case.

How long does a redesign take?

It depends on the number of pages, the content you already have, approvals and integrations. Waiting for text, photos and decisions usually takes longer than building. Plan separate phases for audit, structure, content, build, testing and launch rather than one date.

Should I redesign and change my domain at the same time?

Avoid it if you can. Changing design, structure and domain together makes it harder to find the cause of any drop in traffic. If the domain must change, follow Google's site move guidance for domain changes and document every step.

What should I check on launch day?

Confirm the site is not set to noindex, robots.txt allows crawling, redirects work, canonical tags point to the new URLs, forms and WhatsApp buttons work, tracking fires, and the new sitemap is submitted in Search Console. Then monitor crawl errors and enquiries daily for the first weeks.