A website redesign can feel like the fun part of running a business online: new colors, sharper typography, better photos, and that satisfying “before-and-after” moment. But the truth is, most redesigns don’t fail because the design is bad—they fail because the team jumps into visuals before auditing what’s actually happening on the site today.
If you’re planning a redesign for a business site (whether you’re a brewery, a restaurant, a service provider, or an eCommerce brand), the smartest first step is a thorough audit. It’s like taking inventory before renovating a kitchen: you want to know what’s working, what’s broken, and what you absolutely can’t afford to toss out by accident.
This checklist walks through what to audit before you touch the design. It’s written to be practical, a little opinionated (in a helpful way), and detailed enough that you can hand it to a teammate or agency and say, “Start here.”
Clarify what “redesign” really means for your business
People use the word “redesign” to mean wildly different things. For one company, it’s a fresh coat of paint—new brand colors, updated templates, and a few new pages. For another, it’s a full rebuild: new CMS, new navigation, new content strategy, new integrations, and new conversion paths.
Before you audit anything, decide what kind of redesign you’re actually doing. Are you keeping your platform (like WordPress, Shopify, Squarespace) and improving layouts? Or are you migrating? Are you changing your brand positioning? Are you adding new revenue streams (online ordering, memberships, booking, wholesale inquiries)? The scope changes what you need to measure and protect.
A helpful framing is: what business outcome must improve after this redesign? More reservations? More online orders? More newsletter signups? Better wholesale leads? Faster load times? Lower support emails? If you can’t name the “win,” you’ll end up making decisions based on taste instead of impact.
Inventory every page, asset, and “hidden” workflow
Most websites are bigger than they look. The top navigation might show 6–8 pages, but there are often dozens (or hundreds) of URLs behind the scenes: old campaign pages, seasonal menus, blog posts, event listings, media pages, and landing pages that still get search traffic.
Start with a full URL inventory. Tools like Screaming Frog, Sitebulb, Ahrefs, or even a combination of Google Search Console exports and sitemap crawling can help. You’re looking for: indexable pages, redirected pages, 404s, canonicalized pages, and anything blocked by robots.txt or noindex.
While you’re doing this, list non-page assets and workflows too. Think: PDF menus, downloadable forms, embedded event calendars, online ordering widgets, mailing list forms, gift card systems, job application forms, and any “glue” integrations (like Zapier, CRM connections, POS integrations, or email automations). Redesigns often break these quietly, and you only notice after customers start emailing.
What to document in your page inventory
Create a spreadsheet and include at least: URL, page title, page type (blog, product, event, landing page), primary purpose (inform, convert, support), traffic (last 3–6 months), conversions (if tracked), backlinks (if any), and notes about what must be preserved.
Also note which pages are “must keep” for operational reasons. For example, if you’re a brewery site, you might have pages that staff regularly share (tap list, events, hours, private bookings). Those pages may not be top SEO performers, but they’re crucial for day-to-day operations.
Finally, flag anything that’s outdated but still ranking. Those are prime candidates for content refreshes rather than deletion. Removing a page that ranks—even if it’s old—can create a traffic drop that takes months to recover from.
Audit analytics setup before you trust any numbers
It’s hard to make good redesign decisions with messy data. Before you start pulling reports, confirm your analytics are actually measuring what you think they’re measuring.
Check whether you’re on GA4, whether events are configured, whether conversions are defined properly, and whether internal traffic is filtered (or at least identifiable). If you run ads, confirm that UTMs are consistent and that cross-domain tracking is working if you send users to a third-party ordering platform.
If your analytics are incomplete, don’t panic—just treat it as part of the audit. The redesign is a great moment to fix measurement so you can compare “before” and “after” in a meaningful way.
Key measurement questions to answer now
What actions matter most on your site? Common examples: online orders, table reservations, event ticket clicks, contact form submissions, newsletter signups, gift card purchases, and “get directions” clicks. Make sure each one is tracked as an event and, ideally, a conversion.
Next, confirm you can segment performance by device. Many local businesses see the majority of traffic from mobile, and if your mobile experience is clunky, a redesign that only looks good on desktop won’t move the needle.
Finally, check attribution basics. If you rely on Instagram, Google Business Profile, or email campaigns, confirm that those channels show up cleanly in reports. Otherwise, you’ll underestimate the value of the pages those audiences land on.
Find your highest-value pages (and protect them)
Not all pages are equal. Some pages quietly generate most of your organic traffic, backlinks, and conversions. A redesign that changes URLs, headings, or content structure without a plan can crush performance—even if the new site “looks” better.
Use a mix of GA4 and Google Search Console to identify pages that drive: (1) organic sessions, (2) engaged sessions, (3) conversions, (4) assisted conversions, and (5) high-intent queries. Then add backlink data (Ahrefs/Majestic/SEMrush) to see which pages have authority you don’t want to lose.
Once you know your “money pages,” you can redesign around them instead of accidentally dismantling them.
How to evaluate whether a page should be redesigned, refreshed, or replaced
If a page ranks well and converts, your job is mostly to preserve intent and improve clarity. You can modernize layout and visuals, but keep the core topic, headings, and on-page signals aligned with what Google and users already respond to.
If a page ranks well but doesn’t convert, it’s a perfect redesign target. Often the content matches search intent, but the page lacks a clear next step, has confusing navigation, or buries key details (hours, pricing, booking info) too far down.
If a page doesn’t rank and doesn’t convert, you have options: consolidate it into a stronger page, rewrite it to target a better query, or retire it with a proper redirect if it’s no longer needed.
Map user journeys instead of just pages
Websites aren’t just collections of pages—they’re paths people take to accomplish something. A redesign should make those paths shorter, clearer, and more forgiving.
Start by listing your top user intents. For a local business, these are often: “What are your hours?”, “Where are you located?”, “What’s on the menu/tap list?”, “Can I book an event?”, “Do you have gift cards?”, “Are you hiring?”, and “How do I contact you?” For eCommerce, it’s: browse, compare, trust, buy, track.
Then map the steps from entry point to completion. Where do people land? What do they click next? Where do they drop off? Your analytics can help, but so can basic empathy and a few quick user tests with real people.
Common journey friction points to look for
One frequent issue is “dead-end pages”—pages that answer a question but don’t offer a logical next step. For example, an events page that lists dates but doesn’t make it easy to RSVP, buy tickets, or add to calendar.
Another is “choice overload,” especially in navigation. If your menu has 12 items with vague labels, users hesitate. Your redesign should reduce cognitive load, not add new categories because they sound nice.
Also watch for mobile-specific friction: sticky headers that take up half the screen, popups that are hard to close, forms with tiny fields, and buttons that are too close together. These are small details that can have a big conversion impact.
Check mobile performance like it’s your main website (because it is)
For many businesses, mobile traffic is the majority. Even when people “discover” you on desktop, they often come back on mobile when they’re ready to act—like checking hours on the way over or finding your address in a parking lot.
Audit your site on real devices, not just a browser resize. Test iOS Safari and Android Chrome. Tap through key flows: call, directions, booking, ordering, and forms. Look for slow loads, layout shifts, unreadable text, and anything that feels fiddly.
It’s also worth reviewing your broader digital ecosystem. If your redesign includes new interactive elements, account creation, loyalty programs, or ordering experiences, you may eventually need support from specialists like mobile app developers to make the experience seamless across web and mobile. Even if you’re not building an app today, thinking “mobile-first” will keep your redesign grounded in how people actually use your site.
Mobile-specific items to audit before redesign
Start with tap targets. Buttons should be large enough and spaced well. Links in paragraphs should be easy to tap without accidentally hitting the wrong one. If your site has a sticky bar (like “Order Now”), make sure it doesn’t block content or cover form fields.
Next, evaluate your above-the-fold content on key pages. On mobile, you have less space to communicate trust and next steps. If your hero section is a huge image with no clear action, you’re wasting valuable attention.
Finally, test forms. If your contact form is painful on mobile, you’ll lose leads. Use the right input types (email, tel), minimize required fields, and confirm error messages are clear.
Speed and Core Web Vitals: measure before you change anything
Performance is one of the easiest things to accidentally make worse during a redesign. Bigger images, heavier fonts, more scripts, and fancy animations can slow a site down—especially on mobile networks.
Audit your current performance so you have a baseline. Use PageSpeed Insights (field data + lab data), Lighthouse, and Chrome’s performance tools. Record your Core Web Vitals (LCP, INP, CLS) and note which templates are the slowest.
Then identify what’s causing slowness: unoptimized images, render-blocking scripts, too many third-party tags, heavy sliders, or a theme that’s doing too much. The goal isn’t perfection—it’s improvement without sacrificing functionality.
Performance pitfalls that show up during redesigns
Hero videos and full-screen carousels are common culprits. They look impressive in a mockup but can tank LCP and distract users from the action you actually want them to take.
Another issue is plugin overload (especially on WordPress). Redesigns often add new features via plugins, but each one can add scripts, styles, and database queries. Part of your audit should be deciding what you can remove or replace with lighter solutions.
Also pay attention to third-party embeds: maps, ordering widgets, chat tools, review badges, and social feeds. They can be valuable, but they should be used intentionally and loaded in a way that doesn’t block the main content.
SEO audit: preserve what Google already understands
Redesigns and SEO are tightly linked. Even small structural changes—like altering headings, removing internal links, or changing URL paths—can change how search engines interpret your site.
Before any design work begins, audit your current SEO foundation: index coverage, sitemap health, robots directives, canonical tags, internal linking, schema markup, and on-page elements like titles and meta descriptions.
Then, align your redesign plan with SEO realities. If a page ranks for a valuable query, you don’t want to “simplify” it into a thin page just because the new design looks cleaner with less text.
URL strategy and redirects: decide early
If you can keep URLs the same, do it. Stable URLs reduce risk. If you must change them (new CMS, new structure, better naming), create a redirect map from every old URL to the most relevant new URL.
Avoid redirecting everything to the homepage. That’s a common mistake and it frustrates users and search engines. Each redirect should preserve intent: old events page to new events page, old menu PDF to new menu page, old blog post to updated blog post.
After launch, monitor 404s in Search Console and server logs. Some missed URLs are inevitable, but you want to fix them quickly before they become a long-term traffic leak.
On-page signals to capture before redesign
Export your current title tags, meta descriptions, H1s, and key headings for important pages. This doesn’t mean you can’t improve them—but you should know what you’re replacing.
Also capture internal links. If your blog posts link to your booking page or private events page, make sure those links still exist and still point correctly after the redesign. Internal linking is a quiet ranking factor, and redesigns often break it unintentionally.
If you use structured data (like LocalBusiness, Organization, Product, Event), document what’s currently implemented. A redesign is a great time to improve schema, but you don’t want to accidentally remove it.
Content audit: what to keep, what to rewrite, what to consolidate
Design can’t fix unclear messaging. If your content is outdated, repetitive, or missing key details, a redesign that focuses only on visuals will still feel “off.”
Do a content audit alongside your page inventory. Look for pages that are thin, pages that overlap, and pages that don’t match how people talk about your business today. Pay attention to tone, readability, and whether the content answers real questions.
For businesses with seasonal updates (like rotating menus, events, releases), consider how content will be maintained. A redesign should make it easier for your team to keep information current, not harder.
Rewrite triggers that are easy to miss
If customers regularly call to ask questions that your site should answer (parking, accessibility, dietary options, private bookings, shipping policies), that’s a content gap. Add or improve those sections before you worry about visual polish.
If your site has multiple pages that each mention private events, but none clearly explain capacity, pricing ranges, or how to inquire, consolidate into one strong hub page and link to it from everywhere relevant.
Also look at readability on mobile. Long paragraphs can be fine, but they need scannable formatting: short blocks, clear subheadings, bullet lists, and obvious calls to action.
Brand and design audit: identify what’s dated vs. what’s recognizable
Here’s the fun part—but it still benefits from structure. A brand/design audit helps you separate personal preference from what your audience actually needs.
Gather examples of your current site and note what feels inconsistent: colors, button styles, photography, iconography, spacing, and voice. If your site has grown over time, you may have multiple “mini-design systems” competing with each other.
Also identify what’s recognizable about your brand. Maybe it’s a certain color, illustration style, or photography vibe. The goal isn’t to erase your identity—it’s to make it more coherent.
Practical checks for visual consistency
Audit your typography: how many fonts are you using, and do they load efficiently? Are headings consistent? Is body text comfortable to read on mobile?
Audit your imagery: are photos high quality, current, and representative? If you’re using stock photos that don’t match your real space or product, the redesign is a chance to rebuild trust with authentic visuals.
Audit your UI components: buttons, forms, cards, banners, and alerts. If every page uses a slightly different button style, users may hesitate. Consistency improves usability and makes the site feel more “intentional.”
Navigation and information architecture: make it easier to find the good stuff
Navigation is one of the highest-impact parts of a redesign. A gorgeous homepage won’t help if visitors can’t quickly find the page they need.
Audit your current navigation by looking at: top menu, footer links, mobile menu, and internal links within pages. Then compare that to what users actually do. Analytics can show which pages are most visited, but you can also learn a lot by watching session recordings (if you use Hotjar or similar) or running a simple card sort exercise.
Good information architecture is often boring in the best way: clear labels, predictable grouping, and minimal clutter.
Navigation patterns that work well for local businesses
Use labels people expect: “Menu,” “Events,” “Private Bookings,” “Contact,” “About,” “Shop,” “Order Online.” Clever labels can be fun, but they can also slow people down.
Put high-intent actions in obvious places. If “Order Online” is a primary revenue driver, it should be prominent in the header and repeated in key pages, not buried in a dropdown.
Don’t neglect the footer. Many users scroll down looking for hours, address, accessibility info, and social links. A strong footer can reduce frustration and improve conversions without adding clutter to the top navigation.
Conversion audit: identify where people hesitate
Conversion doesn’t have to mean “buy now.” For many sites, conversions include calls, direction clicks, reservations, inquiries, signups, and downloads. A redesign should reduce hesitation and make next steps feel natural.
Audit your CTAs across the site. Are they consistent? Do they match user intent on each page? Are they visible without being pushy? Do they work on mobile?
Also audit trust signals: reviews, testimonials, press mentions, awards, policies, and clear pricing where relevant. People often need reassurance before they commit, especially for bookings or higher-value purchases.
CTA clarity: small copy changes that matter
Replace vague CTAs like “Learn More” with specific actions like “View Tap List,” “Book a Table,” “Request a Private Event Quote,” or “Order for Pickup.” Specific CTAs reduce uncertainty.
Make sure each key page has one primary action. Secondary actions are fine, but if you give equal weight to five different buttons, users may do nothing.
Finally, test your forms and confirmation states. After someone submits a form, do they see a clear success message? Do they know what happens next? A redesign is a great time to improve these micro-moments.
Accessibility audit: build a site more people can use
Accessibility is about making your site usable for people with different abilities—and it often improves usability for everyone. It’s also increasingly important from a legal and brand reputation standpoint.
Audit color contrast, heading structure, alt text, focus states, keyboard navigation, and form labels. Tools like WAVE, Axe, and Lighthouse can catch many issues, but manual testing is still important.
Accessibility shouldn’t be bolted on after the design is done. If you audit now, you can bake accessibility into your design system and templates from the start.
Accessibility checks that often get overlooked
Make sure interactive elements are reachable and usable with a keyboard. Dropdown menus, sliders, and modals are common trouble spots.
Ensure forms have labels (not just placeholders). Placeholders disappear when users type, and they’re not a replacement for accessible labeling.
Also audit your PDFs. If you rely on PDF menus or documents, consider converting key information into HTML pages that are easier to read on mobile and more accessible to screen readers.
Technical audit: hosting, CMS, plugins, and security
Design changes often trigger technical changes. Even if you’re “just redesigning,” you might switch themes, add plugins, change caching, or move hosts. Audit your current technical setup so you don’t inherit problems—or create new ones.
Document your hosting environment, CMS version, plugin list, theme dependencies, and any custom code. Check whether your site is regularly updated, whether backups are automated, and whether you have a staging environment.
Also audit security basics: SSL, admin access controls, spam protection, and vulnerability monitoring. A redesign is a perfect time to tighten things up.
CMS and plugin sanity checks
List every plugin and what it does. You’ll often find duplicates (two SEO plugins, multiple form plugins, several performance plugins fighting each other). Reducing complexity makes the site faster and easier to maintain.
Check whether your theme or builder locks you into a specific approach. Some page builders make it easy to design but hard to optimize for performance and accessibility. If you’re seeing chronic issues, consider whether a leaner build is worth it.
Plan for maintainability. The best redesign is one your team can update without fear of breaking layouts or needing a developer for every text change.
Local SEO audit: make sure nearby customers can find you
If your business depends on local traffic, a redesign should strengthen local signals—not dilute them. Your website and your Google Business Profile should tell the same story: name, address, phone number, hours, and categories.
Audit your NAP consistency (name/address/phone) across the site, especially in the footer and contact page. Ensure hours are accurate and easy to find. Add location context naturally in key pages, especially if you serve multiple areas.
Also consider adding or improving location-focused content: parking info, accessibility notes, nearby landmarks, and FAQs that locals actually search for.
Schema and on-page local trust builders
Add or validate LocalBusiness schema with correct address, hours, and social profiles. If you host events, consider Event schema for key listings.
Include embedded maps thoughtfully. They’re helpful, but they can slow down pages. If performance is a concern, consider a static map image that links out to Google Maps instead of a heavy embed on every page.
Show real-world trust: reviews, press, community involvement, and photos that match what customers will experience when they visit.
Content governance: who updates what after launch?
One of the most overlooked parts of a redesign is what happens after it goes live. If nobody owns updates, your shiny new site will drift into “outdated” territory within months.
Audit your current content workflow. Who updates hours? Who posts events? Who uploads new menus? Is it one person with login access, or a shared responsibility? Does anyone have a checklist for seasonal updates?
Use the redesign to simplify publishing. Build templates that make it easy to add new events, update menus, and publish news without breaking design consistency.
Simple governance tools that prevent chaos
Create a short style guide: voice, capitalization, how to write dates and times, how to format prices, and what images are acceptable. This keeps the site consistent even when multiple people update it.
Set recurring reminders for key updates: holiday hours, seasonal menus, annual events, and expired promotions. These are the details customers notice most.
Limit the number of content types if you can. It’s better to have a well-maintained “Events” system than three different places where events appear inconsistently.
Audit your “digital ecosystem,” not just the website
Your website doesn’t live alone. It connects to email marketing, social platforms, ordering systems, reservation tools, POS, inventory tools, and sometimes membership or loyalty programs.
Audit every external tool that touches the website. Where do forms send data? Where do booking buttons go? What happens after someone buys a gift card? If the redesign changes URLs or embeds, you’ll want to update those tools too.
If you’re planning broader improvements beyond the site—like integrating ordering, building a customer portal, or connecting systems—this is also the moment to think holistically and start your digital project with a clear plan. A redesign can be the front door to bigger operational wins if you line up the pieces.
Integration checks to run before design begins
List every third-party script and embed. Identify which ones are essential and which ones are “nice to have.” Each one affects performance, privacy compliance, and maintenance.
Confirm where customer data flows. If you collect emails, where do they go? Are you tagging subscribers correctly? Are you complying with consent requirements? A redesign is a good time to clean up forms and permissions.
Test critical flows end-to-end. Don’t just click the button—complete an order, submit a form, book a reservation, and confirm you receive notifications and confirmation emails properly.
Plan your redesign deliverables: sitemap, wireframes, content, then visuals
If you want a redesign to go smoothly, sequence matters. The best projects typically move from structure to clarity to polish: sitemap and information architecture, then wireframes, then content, then visual design, then development.
Audit findings should directly shape these deliverables. For example, if your audit shows that your “Private Events” page is a top lead driver, you might create a wireframe that prioritizes capacity info, photo gallery, FAQs, and a short inquiry form.
This approach also helps teams collaborate. Stakeholders can agree on structure and content before debating button colors.
What to lock in before you open Figma
Decide which pages exist, what each page’s purpose is, and what the primary CTA is. If you can’t answer those, design will be guesswork.
Write or outline key content early. Designs that look great with placeholder text often struggle with real content, especially on mobile.
Set performance and accessibility requirements upfront. For example: “All pages should pass Core Web Vitals,” “No autoplay video,” “All forms must be usable by keyboard,” and “Images must be compressed and properly sized.”
Launch planning: QA, redirects, and post-launch monitoring
Even the best redesign can stumble at launch if QA is rushed. Your audit should feed into a launch checklist that covers functionality, SEO, analytics, performance, and content accuracy.
Plan a thorough QA pass on staging and again after launch. Test on multiple devices and browsers. Check forms, checkout/ordering, booking, navigation, search (if you have it), and all key CTAs.
Then monitor closely after launch: Search Console for indexing and errors, analytics for conversion changes, and performance tools for any regressions.
Post-launch checks that prevent long-term headaches
Verify redirects are working as intended and that there aren’t redirect chains. A clean redirect map protects SEO and improves user experience.
Re-submit your sitemap in Google Search Console and check coverage reports. Watch for spikes in 404s, soft 404s, or pages marked “Duplicate without user-selected canonical.”
Track conversions daily for the first couple of weeks. If form submissions suddenly drop, you want to catch it immediately, not after a month of lost leads.
Choosing the right build partner (and what to ask them)
If you’re working with an agency or developer, your audit becomes your shared source of truth. It helps you avoid vague promises and keeps the project tied to outcomes.
Ask potential partners how they handle SEO during redesigns, what their performance standards are, and how they approach accessibility. Ask for examples of redesigns where traffic and conversions improved, not just where the visuals changed.
If you want a reference point for a team that builds with a practical, business-first mindset, take a look at Grand Apps custom websites in Grandville and note the kinds of questions they encourage you to answer before design begins. The best partners will push you to clarify goals, content, and measurement—not just pick a theme.
Questions that reveal whether a partner is prepared
“How will you protect our current SEO performance during the redesign?” Listen for specifics: redirect mapping, content preservation, technical SEO checks, and post-launch monitoring.
“How will we measure success?” A strong answer includes conversion tracking, baselines, and a plan for comparing before/after performance.
“How will our team update the site after launch?” If the answer is “email us and we’ll do it,” that may be fine—but it should be a deliberate choice, not an accidental dependency.
A practical audit checklist you can copy into your project plan
To make this actionable, here’s a quick checklist summary you can copy into a doc or task manager. The goal is to complete these audits before visual design begins.
Site inventory: crawl all URLs, identify top pages, list assets (PDFs, images), document integrations and embeds.
Analytics: confirm GA4 setup, conversions, event tracking, cross-domain tracking, channel attribution, and device segmentation.
SEO: export titles/meta/H1s, review Search Console performance, identify backlink pages, plan URL strategy and redirect map, validate schema.
Performance: baseline Core Web Vitals, identify heavy scripts and images, evaluate plugin bloat, plan caching/CDN/image optimization.
Content: identify outdated pages, consolidate overlaps, fill gaps from customer questions, plan seasonal update workflow.
UX and conversion: map top user journeys, audit CTAs, test forms, evaluate trust signals, fix mobile friction points.
Accessibility: contrast, headings, keyboard navigation, labels, alt text, PDF strategy.
Technical: hosting, backups, updates, security, staging environment, plugin/theme dependencies.
When you complete these audits first, the design phase becomes much easier—and the finished site is far more likely to perform better, not just look better.
