Complete Website Renovation Audit Checklist

The short version #

A website renovation doesn't start with a kickoff about "a fresh new design." It starts with an audit. Walk the existing site through six lenses: brand and trust, content and structure, technical performance, SEO baseline, conversion paths, and data ownership. Score every item P0 (must fix), P1 (next phase), or P2 (defer). Bring that table to the decision meeting and leadership can finally tell whether this is a redesign, a rebuild, or a migration. Skip the audit, and three months after launch you'll find half the old URLs were never 301'd, case images are gone, nobody owns Search Console, and traffic is down 40% with no obvious cause. The copy-ready table is at the bottom.

A recent project: a 2018 PHP site with plugins nobody could name. Eighty-seven pages, SEO traffic sliding for a year, six-second mobile LCP, an inquiry form that lost messages. Marketing wanted "a refresh," tech wanted a full rewrite, the CEO wanted it live before the next trade show. Two hours of arguing got nowhere, so we paused for a two-week audit. By the end, all three agreed: the real problems were navigation logic, case-study layout, and unmaintained legacy URLs. A full rewrite would have been the riskiest path, not the safest.

Why audit first #

Skipping the audit costs more than running it.

• No baseline, no proof the renovation worked. Without pre-renovation numbers for traffic, bounce, and inquiries, a 30% drop after launch is impossible to attribute. Rebuild or seasonality? Nobody knows.
• No URL inventory, no SEO survival. Backlinks and rankings live on specific URLs. Skip the 301 plan and you wipe out years of compounding equity. How to Preserve SEO During a Website Rebuild covers the mechanics.
• No triage, no scope discipline. Without a written audit, every complaint gets stuffed into scope. Budget doubles, launch slips, the CEO loses patience by week six.

The real output of an audit is one sentence the team can say out loud: "These twelve things are in scope. These eight are not. Here's why."

Redesign, rebuild, or migrate #

The first job of the audit is telling you which kind of project this is. The full comparison is in Website Redesign vs Rebuild vs Migration: How to Choose; the short heuristic:

• Redesign: IA and backend stay; UI, type, color, hero sections change. Use this when branding is dated but the content still works.
• Rebuild: new CMS or front-end, new IA, new URLs. Use this when technical debt is heavy, SEO has been neglected for years, or you're adding multilingual or new business lines.
• Migration: keep content, switch platforms — custom PHP to WordPress, say. Pick this when the backend can't be maintained but the content itself is fine.

Once items are scored, the answer tends to fall out. 70% of P0 items as technical debt means rebuild. 70% as visual fatigue and confusing nav means redesign is probably enough.

1. Brand and trust #

What a buyer sees in the first three seconds.

• "Who are we" header: can a buyer tell what the company does, who it sells to, and where it's based, in three seconds? Hero with one big image and "Empowering the Future" is P0.
• About page: founding year, team size, office address, leadership names. A real name with a real contact beats ten English adjectives.
• Case studies: client name, industry, problem, action, outcome — all five. Anonymous "Fortune 500 client" cases barely register.
• Credentials and third-party proof: certifications, press mentions, partner logos placed sensibly. A wall of fifty logos reads as insecure. Six to eight relevant ones is the right density.
• Contact details: phone, email, address, WhatsApp — present and working. We frequently find footer phone numbers disconnected three years ago.

If this section fails, SEO traffic won't convert.

2. Content structure #

Information architecture.

• Navigation: 5–7 items in main nav. More than nine usually means "everything at the top level." Dropdowns should group, not dump.
• Service pages: every page answers "who is this for, how does it work, what does pricing or delivery look like, what's the next step." "We provide professional service" is a P0 deduction.
• Case study pages: cases and services link both ways. Organize by industry or problem, not reverse chronology.
• FAQ: blocks on service pages and homepage footer. FAQs are the format AI summaries love most. Skipping them leaves free GEO visibility on the table.
• Blog: is it being updated? If the most recent post is a 2022 holiday note, P0 — revive or remove.

For service-page structure that holds up to search and AI summaries, see How to Write Answer-Ready Service Pages for Search and AI Summaries.

3. Technical performance #

Invisible to executives, felt by every visitor.

• First paint and interaction: PageSpeed Insights on homepage, one service page, one case page. LCP over 2.5 s or INP over 200 ms is P0. Mobile matters more than desktop.
• Mobile usability: tap through it on a real phone, not an emulator. Watch nav, forms, CTA buttons. Half the time the primary CTA on the homepage is half-covered by the iOS tab bar and nobody noticed.
• HTTPS and certificates: SSL valid? HTTPS enforced everywhere? Mixed-content warnings (HTTP image on an HTTPS page) are quiet but common.
• 404s and dead links: crawl with Screaming Frog or similar. List every 4xx and 5xx. Each one needs a decision: 301, soft-404, or leave alone.
• Redirect chains: existing 301s already two or three hops deep? Multi-hop chains slow the site and dilute SEO.
• Forms: test every form. Confirm where it lands, whether it hits the CRM, whether anyone has a backup. We've seen forms that stopped working three months earlier with nobody noticing.

For a more systematic baseline, Technical SEO Baseline for a New or Rebuilt Website covers the rest.

4. SEO baseline #

The asset most often destroyed during a rebuild.

• Current traffic distribution: export 12 months of Search Console. Sort by page and by query. Top 50 traffic-driving pages must keep their URLs or get a clean 301.
• Titles and meta descriptions: sample 20 pages. Each title unique, 50–60 characters, no duplicates. Descriptions 120–160 characters.
• Structured data: run the Google Rich Results Test on homepage and service pages. Missing Organization, Service, or FAQ schema is one P0 each.
• Sitemap and robots: is sitemap.xml current? Is robots.txt accidentally blocking important paths?
• Internal linking: do service pages and case studies link to each other with natural anchors? Or does every page only link to "Contact Us" in the footer?
• Backlinks: pull top referring domains from Ahrefs or the free Search Console Links report. Lose those in a rebuild and you're throwing away years of work.

This is where we most often see a 50% traffic drop three months after launch.

5. Conversion paths #

Whether the site generates business.

• CTA consistency: every service page, homepage, and case study with a clear next step. Not one page "Contact Now," another "Get a Quote," a third with nothing.
• WhatsApp button: sensible position. Click actually opens a chat. Prefilled message useful. See How to Add WhatsApp to a Company Website and Track Inquiries.
• Form fields: more than five and conversion drops noticeably. Count what you have. Cut anything redundant or optional.
• CRM and routing: where do submissions go? Anyone replying within 24 hours? Backup if the primary inbox fails?
• UTM and attribution: every external entry point (social, email, ads) carries UTM tags. Without them, you can't tell which channel drives inquiries.

The full conversion list is in Corporate Website Conversion Checklist for More Inquiries.

6. Data and ownership #

The most overlooked lens, and the most likely to blow up mid-renovation.

• GA4 / Search Console / Bing: whose accounts? Where are the credentials? Did anyone take handover from the previous marketing lead?
• Domain and DNS: which registrar holds the domain? When does it renew? Backup of the DNS zone? We had a client discover two weeks before launch that their domain was under the old vendor's account.
• CMS admin list: current list of admin accounts? Departed employees removed?
• Source code and design files: which Git repo? Where are Figma or Sketch files? Where are full-resolution images?
• Server and backups: who hosts now? Backup policy? Can you roll back during cutover?

About 30% of clients discover during this section that one critical account is held by someone they can't reach anymore. The hidden value of an audit is making those landmines visible early.

P0/P1/P2 triage #

The hardest part of an audit isn't finding problems. It's deciding what not to fix. Three tiers:

• P0: blocking. Site can't launch, or fails on launch. Legacy URL 301s, SSL, forms not reaching the CRM, six-second LCP.
• P1: next phase. Ship within 4–8 weeks of launch. Blog relaunch, FAQ expansion, schema coverage, case-page redesign.
• P2: defer. Multilingual, knowledge base, AI chat.

Executives push P2 items into P0 territory. The audit table is what holds the priority line. Simple test: if we don't fix this, will a buyer fail to find, evaluate, or contact us in the next three months? If no, it's P1 or P2.

12 Signs Your Old Company Website Is Losing Leads lists the typical symptoms in more vivid detail.

Audit template #

Copy this into Notion, Lark, or Google Sheets. A week of filling and you have a meeting-ready document.

References: the Google Search Central SEO Starter Guide, Google's structured data introduction, and Google Helpful Content guidance.

FAQ #

How long does the audit take? #

For a 50–100 page company site, two people working together need five to eight working days. Larger sites get batched: automated layer first (PageSpeed, Screaming Frog, Search Console export), then two or three days of manual sampling. Tight on budget? Run only the P0 lenses — brand, technical, SEO — and pick up the rest after launch.

Do we have to audit before renovating? #

Technically no, but the risk is entirely yours. The most expensive version we've watched: client skipped the audit, rewrote everything, three months in discovered 80% of backlinks pointed to eight specific old URLs, the 301s were wrong, SEO traffic dropped by half, recovery took nine months. An audit usually costs 5–10% of the renovation budget and prevents 30–40% of the hidden losses.

Can our vendor do the audit for free? #

You can ask, but be cautious. Free audits cover what the vendor is good at — a design agency looks at visuals, a dev shop looks at code — and conclusions favor whatever they want to sell. An independent audit is the only way to keep the diagnosis honest.

The audit found too many problems. How do we pick what to fix first? #

Use the three-tier scoring to force a sort. Then ask: if we don't fix this, how many inquiries do we lose next quarter? Anything you can put a number on goes first. Anything you can't, becomes P1. Better to ship the P0s at 95% than to ship everything at 60%.

Book a diagnosis #

If you're preparing to renovate, or already in flight and worried the direction is off, bring your domain, your target markets, and current GA4 / Search Console access. We'll run this audit table with you in a free first review and tell you which items are P0, which can wait, and which probably don't need to happen at all. More on our website rebuild service.