Website Redesign

Website redesign checklist for Kansas City small businesses

Use this before redesign work begins to preserve what already earns trust, fix the parts that block leads, and relaunch without avoidable SEO or tracking problems.

12 min readKansas City metroUpdated August 28, 2026

Read the guide Get a Free Marketing Audit

The Short Answer

A redesign should improve business performance—not simply replace the colors.

Audit the current site, preserve valuable pages and data, define the new conversion path, map every changed URL, test the build on real devices, and verify analytics after launch. The safest redesign changes the things holding the business back while protecting the signals already working.

Define measurable goals before discussing style or platform.

Inventory current URLs, traffic, rankings, links, and conversions.

Map changed URLs one-to-one with permanent redirects.

Verify forms, calls, analytics, indexing, and sitemaps after launch.

Make the Right Call

Decide whether the site needs a redesign, rebuild, or focused refresh.

A site can feel old without being fundamentally broken. If the structure, platform, and conversion path still work, better copy, new proof, faster images, and cleaner calls to action may create more value than a full rebuild. A redesign becomes more reasonable when the business has changed, the site is hard to maintain, mobile use is poor, service pages are missing, or tracking cannot reliably show what visitors do.

Write down the business problem before choosing the solution. Useful goals include increasing qualified form submissions, reducing confusion about services, making the site easier to update, improving mobile calls, preserving search visibility during a rebrand, or supporting a new service line. Avoid goals such as 'make it modern' unless you can explain what modern presentation should help a customer understand or do.

Refresh when the structure works but copy or visuals are dated

Redesign when layout, messaging, and conversion paths need coordinated change

Rebuild when the platform or code blocks performance and maintenance

Set one primary outcome and several measurable supporting metrics

Protect What Works

Audit the current site before wireframes or mockups begin.

The existing site contains evidence you cannot reconstruct after it disappears. Export analytics and Search Console data, crawl every URL, record backlinks, test forms, and identify pages that already generate impressions, visits, calls, or leads. Save the metadata, headings, copy, files, and screenshots needed for comparison. Even an unattractive page may hold rankings or answer a customer question well.

Classify every page as keep, improve, merge, redirect, or remove. Keep pages that serve a clear purpose. Improve pages with useful intent but weak presentation or conversion. Merge overlapping pages only when the combined destination truly covers both needs. Remove content with no audience or business role, and redirect an old URL only to a genuinely relevant replacement.

Export at least 12 months of analytics and Search Console data

Crawl all URLs, status codes, titles, canonicals, and internal links

List backlinks, top landing pages, and conversion paths

Archive current copy, forms, integrations, and screenshots

Rebuild the Customer Path

Plan the message, page structure, and proof around real decisions.

The homepage should quickly identify the business, audience, service area, value, and next step. Service pages need enough detail to help a prospect understand fit. Proof should sit near claims: project examples near services, testimonials near objections, and process details near the point where a visitor decides whether contacting the business feels safe.

Design mobile-first because many local prospects arrive from a search result, map listing, referral text, or social profile on a phone. Keep navigation short, make phone and form paths obvious, and avoid forcing visitors through decorative screens. Accessibility, readable type, contrast, keyboard use, and clear form labels improve the experience for more customers and make the site easier to operate.

Write the offer and page outline before polishing visual design

Give important services clear, dedicated destinations

Place real proof beside the claims it supports

Design every important action for a phone-sized screen

Preserve Search Equity

Create the URL and SEO migration plan before development finishes.

Keep useful URLs unchanged when possible. When a URL must change, map the old address to the closest new equivalent and implement a permanent server-side redirect. Do not point every retired page to the homepage. Update internal links, canonicals, navigation, XML sitemaps, campaign destinations, and important external profiles so users and crawlers reach the final URL directly.

Carry forward the substance that made a page relevant: the customer question, service detail, proof, headings, and internal relationships. A redirect helps transfer signals, but it does not make a thin replacement equivalent to a useful old page. Review title and description changes against the page's intended query rather than rewriting every field for the sake of novelty.

Use a one-to-one old URL → new URL migration sheet

Implement and test permanent redirects without chains

Update canonicals, internal links, sitemaps, and ad destinations

Preserve useful content and backlinks—not only the URL

Launch Carefully

Test the production build, not only the design preview.

A polished staging preview can still launch with blocked indexing, broken forms, missing analytics, or incorrect redirects. Test the built site across common phones and browsers. Submit every form, tap every phone and email link, confirm thank-you behavior, and verify that lead-source fields and conversion events still fire. Check the 404 page and make sure removed URLs return the intended status.

Review titles, descriptions, canonical URLs, robots directives, structured data, Open Graph images, sitemap entries, and page status codes. Inspect important pages with Search Console after deployment and submit the relevant sitemap. Keep a rollback plan for material failures, but expect some normal search fluctuation while Google recrawls changed pages.

Test navigation, buttons, forms, calls, email, and bookings

Verify responsive layout, keyboard use, contrast, and performance

Confirm analytics, consent, conversion events, and attribution

Check indexing, schema, metadata, canonicals, redirects, and sitemaps

Measure the Outcome

Watch lead quality and search performance after launch.

Compare the new site with the baseline at seven, 28, and 90 days. Watch organic clicks, important query positions, form completion, phone actions, engagement on key pages, and qualified leads. A visually stronger site can still underperform if it attracts the wrong audience or adds friction to the contact path.

Fix critical issues immediately: failed forms, missing tracking, incorrect noindex rules, redirect loops, broken navigation, or a sharp loss tied to removed content. Treat ordinary ranking movement with more patience and evidence. The goal is not to preserve every number forever; it is to protect useful equity while creating a clearer, faster, more measurable customer experience.

Keep Going

Useful next steps for your Kansas City business.

These pages connect the guide to the service, local proof, and decision support behind it.

Kansas City website design View website work Website builder vs. custom Kansas City service areas

Frequently Asked Questions

Questions Kansas City owners ask before the next step.

How do I know if my small-business website needs a redesign?+

A redesign is worth considering when the site no longer reflects the business, is hard to use on mobile, cannot support clear service pages, loads slowly, is difficult to maintain, or fails to create measurable inquiries. An audit can distinguish those issues from smaller copy or design fixes.

Will a website redesign hurt SEO?+

It can if useful content disappears, URLs change without relevant redirects, internal links break, or indexing settings are wrong. A documented baseline, URL map, tested redirects, preserved content, and post-launch monitoring reduce avoidable risk.

Should all URLs stay the same during a redesign?+

Keep useful URLs when possible, but do not preserve a confusing structure at any cost. When an address changes, map it to the closest relevant new page, implement a permanent redirect, and update internal links and sitemaps.

What should we measure after the redesign?+

Track calls, form submissions, bookings, qualified leads, organic clicks, priority query movement, landing-page engagement, page speed, and form completion. Compare these with a saved pre-launch baseline.

Free · Practical · No-pressure

Not sure whether your website needs a refresh or a full redesign?

Hometown's free marketing audit identifies the messaging, mobile, SEO, tracking, and conversion issues that should shape the scope.

Explore Website Design