The short answer
A good Bountiful website redesign protects what already works, fixes what blocks leads, and gives Google cleaner facts about the business, services, service area, proof, and next step.
The mistake is treating redesign as decoration. For a local business, redesign is part technical cleanup, part positioning, part local SEO, and part lead-path repair.
Start with the business goal, not the theme
Most small-business redesigns go sideways because the first decision is visual. The better first question is: what kind of lead should this site produce?
A Bountiful contractor may need more estimate calls from Davis County. A clinic may need appointment requests for a specific service. A consultant may need qualified discovery calls. A shop or local brand may need people to understand the offer before visiting or ordering.
The new site should be planned around that path. A nice homepage that does not explain the service, location, proof, and next step is still a weak sales tool.
Check Search Console before changing URLs
Before rebuilding anything, look at Google Search Console. It tells you which queries and pages are already getting impressions and clicks. That matters because even a small amount of existing search visibility is worth protecting.
Look for:
- Queries: which search terms already show the business?
- Pages: which URLs are visible, and which important services are invisible?
- Click-through: are people seeing the result but skipping it?
- Indexing: are important pages indexed, discovered but not indexed, or missing?
If a page already gets impressions for a local service, do not casually delete it. Improve it, keep the URL if possible, or redirect it carefully to a better replacement.
Protect the URLs that matter
Local SEO damage often happens during launch. The new site goes live, old URLs disappear, and Google or customers hit dead ends. That is avoidable.
Make a simple URL map before launch:
- Keep strong URLs when they still make sense.
- Redirect old service pages to the most relevant new page.
- Do not redirect everything to the homepage.
- Remove only pages that truly should not exist.
- Submit a clean sitemap after launch.
For a small site, this can be a simple spreadsheet. The important part is that every meaningful old URL gets a destination.
Build real service pages, not one vague services page
A redesign is a chance to stop asking one page to do every job. If a business wants leads for several services, those services usually need their own useful pages.
A strong local service page should answer:
- What is the service?
- Who is it for?
- Where is it available?
- What does the process look like?
- What should the buyer know before calling?
- What proof supports the claim?
- What is the next step?
That kind of page helps buyers and search systems. It gives Google clearer local relevance, and it gives AI search systems better facts to summarize.
Make the Bountiful and Davis County context honest
Local relevance does not mean stuffing city names everywhere. It means explaining how the business actually serves the area.
For a service-area business, that may include:
- Based in or near Bountiful.
- Serving North Salt Lake, Woods Cross, Centerville, Farmington, Layton, Davis County, Salt Lake City, or the Wasatch Front.
- Local meetings by appointment when that is true.
- A hidden address in Google Business Profile if there is no staffed public storefront.
- Service pages that mention relevant local constraints, timing, buyers, neighborhoods, or examples without pretending every city needs a duplicate page.
Google does not need 20 thin city pages. It needs a real business, clear services, accurate service areas, reviews, links, and useful pages.
Fix the mobile lead path
Many local buyers find a business on their phone. The redesign should make action obvious without forcing people through a maze.
Before launch, test the mobile version and ask:
- Is the phone number visible and tappable?
- Does the first screen say what the business does and where it works?
- Is the quote or contact button easy to tap?
- Does the form ask only for what is needed?
- Does the form confirmation set a clear expectation?
- Do photos, headings, and buttons fit without awkward wrapping?
Design polish matters, but a clear phone path and short form often matter more for leads.
Put proof near the claims
Proof should not live only on a testimonials page. If a page says "fast," "local," "experienced," or "specialized," nearby proof should support it.
Useful local proof includes:
- Google reviews.
- Project photos.
- Before-and-after examples.
- Local client or service-area examples.
- Founder or team context.
- Certifications, insurance, warranties, or credentials when relevant.
- Clear pricing context or what affects price.
Search systems can read proof signals, but the real reason to add them is simpler: people hesitate less when the claim feels specific and believable.
Align the website with Google Business Profile
Your website and Google Business Profile should tell the same story. If the profile says one thing and the site says another, the local entity is weaker than it should be.
Check alignment on:
- Business name.
- Primary category.
- Phone number.
- Website URL.
- Hours.
- Service areas.
- Services.
- Appointment or storefront policy.
- Photos, reviews, and updates.
A complete profile will not save a bad website, and a good website will not fully replace profile work. They reinforce each other.
Use schema as confirmation, not magic
Structured data helps search systems understand the business and page, but it should match the visible content. Do not use schema to claim services, locations, reviews, or hours that the page and business profile do not support.
For a local redesign, useful schema can include:
- ProfessionalService or LocalBusiness details.
- Logo, phone, URL, hours, and service area.
- Article schema for useful guides.
- FAQ schema when the page includes real FAQs.
- Breadcrumbs for site structure.
Schema is not a ranking shortcut. It is a clarity layer. The page still needs useful content, strong internal links, and real-world proof.
Launch with a checklist
A redesign is not finished when the homepage looks right. Use a launch checklist so the new site does not quietly lose leads or crawl signals.
- Test every form.
- Tap every phone link on mobile.
- Check title tags and descriptions.
- Confirm canonical URLs.
- Generate and inspect the sitemap.
- Submit the sitemap in Search Console.
- Request indexing for the most important pages.
- Check redirects from old URLs.
- Make sure analytics and conversion tracking work.
- Compare the site to the Google Business Profile.
After launch, watch Search Console. Indexing and rankings do not always move immediately, but crawl errors, missing pages, and unexpected query changes should be caught early.
What to fix first if you are local to Bountiful
If you are deciding what to do this week, use this order:
- Confirm the site can receive leads. Test the phone and form.
- Check Search Console. Find the queries and pages already getting impressions.
- Clean up Google Business Profile. Logo, photos, services, service areas, hours, reviews, and website link.
- Improve the most important page. Usually the homepage, a top service page, or a local page.
- Add proof. Reviews, photos, examples, founder context, and clear service details.
- Plan redirects before launch. Do not break URLs that Google or customers already use.
Need a plain read before rebuilding?
Freehold Sites is based in Bountiful and reviews small-business websites for search visibility, local clarity, mobile lead paths, and rebuild risk. Send the current URL and the service area.
Get a free website teardownFAQ
How much does a small-business website redesign cost in Utah?
It depends on page count, content, platform, redirects, forms, photography, and SEO scope. For a lean local marketing site, the practical range is often much lower than a full agency build, especially when the site does not need complex application features. See the Utah website cost guide for more context.
Should I keep Wix or WordPress during a redesign?
Keep the platform if it is serving the business well. Move away if basic edits, speed, ownership, URL control, forms, or maintenance are creating drag. If moving platforms, protect URLs, metadata, content, redirects, analytics, Search Console, DNS, and email records.
Do I need a separate page for every city?
No. Thin duplicate city pages are usually weak. It is better to have strong service pages and one useful local/service-area page unless there is enough real distinction, proof, and demand to justify more local pages.
What is the biggest local SEO mistake during redesign?
Breaking useful URLs and replacing specific service pages with vague, prettier pages. A redesign should make the business clearer, not erase the signals that were already helping it get found.
Can a static website work for a local business?
Yes. Many local lead-generation sites are mostly static pages: homepage, service pages, local page, about page, proof, contact, and guides. If the pages are clear, fast, indexed, and easy to update through the owner-controlled workflow, static can be a strong fit.