# How can a contractor redesign a website without losing search rankings?

By Dee, Summit AI Solutions. Updated 2026-11-14.
Canonical: https://summitaiautomations.com/blog/redesign-contractor-website-without-losing-rankings/

## Why do redesigns so often hurt rankings?

Redesigns hurt rankings when old pages disappear or move without a redirect, when helpful content gets trimmed to make things look cleaner, or when the new site is slower or harder for Google to read. Most of the damage is avoidable.

A search engine builds its picture of your site over time. Each page has an address, content and links pointing to it. If a redesign changes addresses, removes pages or rewrites copy, Google has to relearn all of it, and during that period your positions can slip.

Timing also matters. If your busy season is close, a rushed launch can put calls at risk when you can least afford it. Some owners plan a redesign for a slower stretch, which leaves room to fix problems before the next wave of work arrives.

The riskiest moments are the ones nobody sees. A designer rebuilds the site on a fresh platform, and the old service pages quietly vanish. Customers who bookmarked a page or clicked an old search result land on an error. Google sees the same error and may eventually drop the page.

None of this means you should avoid a redesign. A tired, slow or confusing site costs you leads too. It means the project needs a plan that treats your existing pages as assets, not clutter.

## What should you do before the redesign starts?

Make a full inventory of your current pages, note which ones bring visitors and calls, and save a copy of everything. This list becomes the map you use to decide what stays, what moves and what gets redirected.

Export a list of every page on the site. Add what you know about each: whether it gets traffic in Search Console, whether it earns calls or form leads, and whether other sites link to it. Your pages that already rank deserve the most protection.

Ask your designer to show you the plan for page addresses, redirects and content in writing before work begins. A good professional will have a process for this and will not be offended by the question. If they say rankings are not their concern, consider whether they are the right fit.

Take screenshots or save the text of the existing pages. If anything goes wrong later, you will have a record of what was there. Save your title tags and descriptions too, since these are easy to lose when moving platforms.

Record a baseline from Search Console and your call tracking before you change anything. Without a before picture, you cannot tell afterward whether the redesign helped or hurt.

- Full list of current page addresses
- Notes on which pages bring traffic, calls or links
- Copy of titles, descriptions and page text
- Baseline numbers from Search Console and call tracking

## How should URLs and redirects be handled?

Keep your existing page addresses wherever you can. When an address must change, set up a permanent redirect from the old address to the closest matching new page, and test every one before launch.

The best redirect is the one you never need. If your roof repair page lives at one address today and still makes sense, leave the address alone, even if the design around it changes. A new look does not require new addresses.

Also keep a note of any pages that other websites link to, such as a local news mention, an association listing or a supplier page. Those links carry value, and breaking the address they point to wastes it. Permanent redirects help carry that value over when a move is needed.

When a change is unavoidable, such as moving to a new platform with a different structure, map each old address to its new equivalent in a spreadsheet. Use permanent redirects, not temporary ones, and point each old page to the most relevant new page. Google advises against sending many old pages to the homepage, since it can confuse visitors and may be treated as a soft 404.

Test the list. Click through old addresses on a staging copy and after launch, and avoid chains where one redirect leads to another, since Google advises redirecting directly to the final page. Your developer should be comfortable with this task. If they are not, that is worth knowing before the project begins.

## What content should you protect?

Protect the pages and sections that already rank and earn calls, especially service pages, city pages and any detailed answers to customer questions. Improve them, but avoid cutting them down just to fit a cleaner layout.

Designers like short pages with big images. Search engines and customers often prefer pages that fully answer the question. If a service page currently has useful detail about how the work is done, what affects timing and what to expect, keep that detail even if it needs to be reorganized.

Do not forget the pieces that run in the background, such as your analytics tracking, call tracking numbers and form connections. These are easy to drop during a rebuild and hard to notice until weeks later, when you realize the data has a gap.

Keep the signals that tell Google where you work: your business name, address, phone, service areas and license details. Keep your reviews, project photos and blog posts. Replace weak or outdated content with better content, but do not delete a page that earns visitors without a reason.

Check that the new site keeps page titles and headings that reflect what people search for. A fresh headline like 'Your Home, Our Craft' looks nice but gives Google and visitors nothing to hold onto.

## What should you check after launch?

After launch, check that old addresses redirect properly, that Search Console shows your pages as indexed, and that calls and forms still arrive. Monitor closely for several weeks and fix problems quickly.

Submit your updated sitemap in Search Console and look for new errors in the days after launch. Watch for pages that Google cannot find or that return an error. Fix those first, since they are the ones with the most direct effect.

Keep the old site accessible in a safe way for a short period, if your platform allows, so you can compare pages side by side. When something looks wrong, having the original to check against makes the fix much faster.

Compare Performance numbers against your baseline, but allow time. Movement after a redesign is common for a while, and a small dip does not mean failure. A steep, lasting drop on key pages is the signal to investigate redirects and content.

Test the practical stuff yourself: tap the phone number on a phone, submit the form, load the site on a slow connection. A website that ranks but fails a customer at the final step does not help you. If you want a second pair of eyes on a redesign plan, Summit AI Solutions can talk it through with you.

## Sources

- [Google Search Central: Redirects and Google Search](https://developers.google.com/search/docs/crawling-indexing/301-redirects)
- [Google Search Central: Site moves and migrations](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes)