Website Audit Checklist: What to Review Before a Redesign or a Campaign
A practical website audit checklist: access and indexing, content, structure, speed, accessibility, mobile, measurement, security and conversion, with a way to prioritise the findings.
02 / In this article
A website audit is a structured review of a site against a fixed list of checks, ending in a ranked list of problems to fix. The most useful audits are short on opinion and long on evidence: each finding names a page, a cause and a next step. This checklist covers nine areas, shows how to rank what you find, and explains when to audit, before a redesign or before you spend money on a campaign.
Key Takeaways
- An audit is a decision tool, not a report. It exists to tell you what to fix first, what to leave alone and what to rebuild.
- Work from the bottom up. If a page cannot be crawled, indexed or loaded, better copy and a better button will not help.
- Use the standards, not a hunch. Core Web Vitals thresholds come from web.dev, accessibility from WCAG 2.2, indexing rules from Google Search Central.
- Rank every finding by impact and effort. A short list of quick wins beats a 90-item spreadsheet nobody opens.
- Audit at two moments. Before a redesign, so you keep what works. Before a campaign, so paid traffic does not land on a broken page.
What is a website audit?
A website audit is a systematic check of how a site performs against defined criteria, such as whether search engines can reach it, whether people can use it and whether it measures what matters. The output is a prioritised list of findings, each with evidence and an owner.
An audit is not one thing. A marketer, a developer and an accessibility specialist would each look at different layers of the same site. That is why a good audit has a scope. Write down which pages, which devices and which goals it covers before you open a single tool. A small site with one service can be reviewed in full. A site with thousands of URLs needs a sample: the home page, the main service or product pages, a few blog posts, the contact page and the checkout or booking flow.
Treat the audit as a snapshot with a date on it. If you want a specialist to run the search side of it, our team offers a search-focused audit with a written action list.
When should you audit your website?
Audit before any large change and on a regular schedule, because both situations carry a cost if you skip it. The two moments that matter most are before a redesign and before a campaign.
Before a redesign. A redesign without an audit tends to throw away what works. Pages that earn search traffic get renamed, redirects are forgotten and the new design repeats the old problems in a nicer font. An audit tells you which URLs to keep, which content to carry over and which friction points to remove. If you are planning a rebuild, our guide to the AI-assisted website redesign process shows where the audit fits, and the website redesign service is where the findings turn into a build.
Before a campaign. Paid traffic amplifies whatever is on the landing page, including a slow load, a broken form or missing tracking. Auditing the destination first protects the budget. It also gives you a baseline, so you can tell later whether the campaign or the page made the difference.
On a rhythm. A lighter check every quarter and a full one each year is a reasonable habit. Add one after a migration, a theme change or a change of hosting.
How do you scope the audit and gather your tools?
Scope the audit around one goal, then collect a small set of free tools before you start. The goal might be "more booked calls", "more organic visits to service pages" or "a safe launch for the autumn campaign". Everything you check should link back to it.
You need little:
- Google Search Console for indexing, queries and Core Web Vitals field data on your own site. Google's starter guide recommends setting it up to monitor how the site performs in Search.
- An analytics tool (Google Analytics or Matomo, for example) to see what visitors do.
- A crawler that lists URLs, status codes, titles, headings and links. Some are free for small sites.
- A real phone and a real laptop. Open the site on both and complete the main task yourself.
- A shared sheet with one row per finding: page, issue, evidence, impact, effort, owner, status.
Before you check anything, list the site's key actions: buy, book, call, subscribe, download. You will test these paths in every section.
The nine-area audit checklist
The checklist below is arranged as layers. Each layer depends on the one beneath it, so you review them in order.
1. Access and indexing: can search engines reach the pages?
A page can only appear in search if a crawler can fetch it and Google chooses to index it. Start here.
- Open the Pages report in Search Console and note how many URLs are indexed and why others are not.
- Use the URL Inspection tool on your main pages. It shows how Google sees the page.
- Read
robots.txt. Google explains that it manages crawl traffic and is not a way to keep a page out of Google: a blocked URL can still appear in results if other sites link to it, without a description. - To keep a page out of the index, use
noindexas a meta tag or anX-Robots-Tagheader. Google also warns that the crawler must be able to fetch the page to see the rule, so a page blocked inrobots.txtnever shows itsnoindex. - Check that important pages return a
200status. Google does not index URLs that return a4xxcode, and persistent5xxerrors lead to URLs being dropped. - Check redirects. A
301is a strong signal that the target is the page to process, while a302is a weak one. Use301for permanent moves. - Look for soft 404s: pages that say "not found" but return a success code.
- Confirm that an XML sitemap exists and lists the pages you want indexed. Google says a sitemap does not guarantee crawling or indexing, and that a small, well-linked site may not need one, but it is cheap to provide.
2. Content and answers: does each page say what it is for?
Each important page should state clearly what it offers, to whom and what to do next. Google's guidance asks for helpful, reliable content written for people first, so judge pages as a visitor would.
- Does the first screen of each key page say what the page is and who it is for?
- Does each page have one main topic and a title that is unique, clear and accurate? Google describes a good title as unique to the page, clear, concise and accurate.
- Do two pages compete for the same question? If so, merge them or give each its own angle.
- Are there thin, outdated or duplicate pages? Decide for each: improve, merge, redirect or remove.
- Do pages answer the real questions customers ask? Our guide to answer engine optimization shows how.
Want a second pair of eyes on your site?
We review the pages that matter to your goal and send back a ranked list of what to fix first.
Explore the audit service3. Structure and links: can people and crawlers find their way?
Good structure means every important page is reachable in a few clicks, with link text that explains where it goes. Google notes that links connect users and search engines to other parts of a site and that link text should describe the destination.
- Can you reach every important page from at least one other page? Pages with no internal links are hard to find.
- Are URLs readable? Google suggests words that are useful to users, not random identifiers.
- Is anchor text descriptive, or does the site say "click here" everywhere?
- Do images have useful alt text? Google describes alt text as a short, descriptive text that explains the relationship between the image and the content.
- Is structured data present where it describes visible content, and does it validate? Our article on schema markup for small businesses explains what is worth adding.
For the wider plan behind this layer, see our guide to SEO for small businesses.
4. Performance: is the site fast enough to use?
Core Web Vitals are the three metrics web.dev uses to describe loading, interactivity and visual stability. A page meets the "good" level when it hits the targets at the 75th percentile of page loads, segmented across mobile and desktop.
| Metric | What it measures | "Good" threshold on web.dev |
|---|---|---|
| Largest Contentful Paint (LCP) | Loading | Within 2.5 seconds of when the page first starts loading |
| Interaction to Next Paint (INP) | Responsiveness | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | Visual stability | 0.1 or less |
How to check it: the Core Web Vitals report in Search Console and PageSpeed Insights show field data from real visitors where enough exists, and lab data from a test run. Field data tells you what visitors experience. Lab data helps you find the cause. Test the pages that carry the goal first (a landing page, a product page, the booking page), on mobile.
Common causes: large images, many third-party scripts and elements that appear late and push content down. If speed is the main problem, a dedicated website speed optimization pass is usually the next step.
5. Accessibility: can everyone use the site?
An accessible site can be perceived, operated and understood by people with a wide range of abilities, using a range of devices. The W3C's Web Content Accessibility Guidelines (WCAG) 2.2 organise this under four principles: perceivable, operable, understandable and robust. Success criteria are graded at levels A, AA and AAA.
A first pass you can do without a specialist:
- Use the keyboard only. Can you reach every link, button and form field with Tab, and see where the focus is?
- Check that text has enough contrast against its background and that meaning is never carried by colour alone.
- Check that every form field has a visible label and that errors are explained in text.
- Check headings: one
h1, and a logical order below it.
WCAG 2.2 added nine success criteria to 2.1, and removed 4.1.1 Parsing. Among the new AA ones are Focus Not Obscured (Minimum), Dragging Movements, Target Size (Minimum) and Accessible Authentication (Minimum). In practice: sticky headers should not hide the focused element, dragging needs a simple alternative and buttons need a reasonable tap target. Automated tools catch only part of the issues, so pair them with a manual pass. Legal requirements differ by country and sector, so ask a qualified adviser if you need to show compliance.
6. Mobile: does it work on a phone?
Google uses the mobile version of a site's content for indexing and ranking, crawled with its smartphone agent. So the phone version is the version that counts for search, and it must contain the same content as the desktop one.
- If the site is responsive, confirm that nothing is hidden or removed on small screens.
- If there are separate mobile and desktop versions, check that content, structured data, titles, meta descriptions and robots meta tags are equivalent.
- Complete the main action on a real phone, on mobile data, not only on office Wi-Fi.
- Check tap targets, text size and pop-ups that cover the page.
7. Measurement: do you know what is happening?
If tracking is wrong, every other decision rests on bad data. This layer is easy to skip and expensive to repair later.
- Is the analytics tag installed once, on every page, and firing only after the consent you require?
- Are the key actions recorded as events? Google Analytics 4 separates automatically collected events, enhanced measurement events, recommended events and custom events. Google notes that recommended events are not sent automatically and should be sent with their prescribed parameters.
- Do form submissions, calls, bookings and purchases each register once, not twice and not zero times? Submit a test and watch it arrive in real-time reports.
- Are campaign links tagged consistently, so traffic sources are readable?
- Is the setup documented, so a new person knows what each event means?
If your data is inconsistent, a tracking and analytics setup comes before any optimisation. If you already use an AI assistant to query your reports, our note on the Google Analytics MCP server covers how that works and what to be careful about.
8. Security basics: is the site safe to use?
A baseline security check confirms that visitors connect over HTTPS and that nothing obvious is exposed. It is not a penetration test.
- Does every page load over HTTPS, and does HTTP redirect to it?
- Does the server send the
Strict-Transport-Securityheader? MDN explains that it tells browsers to use HTTPS directly on later visits. - Are the CMS, plugins and dependencies up to date, and admin accounts limited with two-step sign-in?
9. Conversion: does the page help the visitor act?
Conversion is where the earlier layers pay off, or fail to. For each key page, ask what a visitor must do and what stands in the way.
- Is there one primary action per page, stated in a clear verb?
- Is the offer understandable in a few seconds, without scrolling?
- Are trust details present and true: contact details, policies, real reviews you are allowed to show?
- Where do visitors leave? Look at the paths in analytics and, if you can, at recordings or session replays that you have consent to collect.
When you have a hypothesis and enough traffic, test it rather than argue about it. Our conversion optimization work starts from this layer.
How do you prioritise what the audit finds?
Rank findings by two questions: how much does this block your goal, and how much work does it take to fix? Plot each finding on a simple grid and work through it in a set order.
Use these rules:
- Blockers first. A noindex tag on a service page, a form that fails, tracking that records nothing. These go to the top whatever their effort.
- Then the top-left of the grid in the figure: high impact, low effort. Examples include fixing a broken redirect, adding a missing title or compressing an oversized hero image.
- Plan the big jobs on a roadmap with an owner and a date, and batch the small ones into one session.
- Drop what does not serve the goal. Not every warning from a tool matters. If a finding does not affect your goal, record it and move on.
Judge impact against evidence, not against a tool's severity colour. A "high" warning on a page nobody visits ranks below a "medium" one on your booking page.
What should an audit deliverable contain?
A good audit deliverable lets someone who was not there understand each problem and act on it. The test is simple: can a developer fix the item without asking you a question?
Include in the document:
- Scope and date: pages, devices, tools and the goal.
- A short summary: the three to five things that matter most, in plain language.
- The findings table: page, issue, evidence (a screenshot, a report line, a URL), impact, effort, owner, status.
- The priority grid: the output of the previous section.
- What is working: the pages, content and settings to keep, which matters before a redesign.
- A re-check plan: when you will run the same checks again, and which numbers should have moved.
An audit shows what to fix and why. It cannot tell you how much traffic or revenue a fix will produce.
Planning a redesign after the audit?
Send us the audit and the goal. We reply with how we would rebuild the pages that matter.
See our website redesign workHow do you use the audit before a redesign?
Before a redesign, use the audit to build three lists: what to keep, what to change and what to remove. It stops the new site from losing the pages that already work.
- Keep: list the URLs that bring search visits or conversions. These need the same address, or a
301redirect to the closest new page. - Change: list pages with real content value but weak structure, speed or conversion. They are rewritten, not discarded.
- Remove: list thin, duplicate or outdated pages. Merge or redirect them, rather than carrying them over by habit.
- Record the baseline: save the current numbers for indexed pages, Core Web Vitals, key events and conversions, so you can compare after launch.
- Check after launch: run the access and indexing layer again right after going live.
How do you use the audit before a campaign?
Before a campaign, audit only the path the traffic will take: the ad, the landing page, the form or checkout and the confirmation. A short audit of this path is enough.
- Does the page match the promise of the ad, in words and in offer?
- Does the form work, and does the confirmation page fire a conversion event once?
- Are the campaign links tagged and the conversion imported into the ad platform?
- Is there a way to compare variants later, for example through an A/B test?
If something fails the check, fix it before the budget starts, not after the first week.
Frequently Asked Questions
What is a website audit?
A website audit is a structured review of a site against a fixed list of checks, covering areas such as indexing, content, speed, accessibility, tracking and conversion. It ends in a prioritised list of fixes with evidence for each.
How often should I audit my website?
Run a full audit when you plan a redesign, a migration or a large campaign, and a lighter check each quarter. Run an extra check after any technical change, such as a new theme, a plugin or a hosting move.
Can I do a website audit myself?
Yes, for most of the basics. Search Console, an analytics tool, a crawler and your own phone cover the first checks. Bring in a specialist for deeper technical SEO, accessibility conformance, security and tracking design.
What are Core Web Vitals and which thresholds count as good?
Core Web Vitals are three metrics: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness and Cumulative Layout Shift for visual stability. web.dev lists the good levels as within 2.5 seconds, 200 milliseconds or less, and 0.1 or less, measured at the 75th percentile of page loads.
What is the difference between a website audit and an SEO audit?
An SEO audit looks at how a site performs in search: crawling, indexing, content, links and technical health. A website audit is wider. It adds accessibility, measurement, security and conversion, because a site can be easy to find and still fail to turn visitors into customers.
Does a website audit guarantee more traffic or sales?
No. An audit finds problems and ranks them. Results depend on whether the fixes are made, on your market and on factors outside your control. Treat it as the way to decide what to do, not as a promise.
Next steps
Pick one goal, scope the pages that serve it and run the nine areas in order, writing each finding in the table format above. Fix the blockers first, then the quick wins, and set a date to re-check. If you want help running the audit or acting on it, see our conversion optimization work, the tracking and analytics service, or the search audit. Planning a rebuild? Start with the website redesign page. When you are ready, get in touch with your site address and your goal.
Sources
- web.dev, "Web Vitals": https://web.dev/articles/vitals
- W3C, "Web Content Accessibility Guidelines (WCAG) 2.2": https://www.w3.org/TR/WCAG22/
- Google Search Central, "Introduction to robots.txt": https://developers.google.com/search/docs/crawling-indexing/robots/intro
- Google Search Central, "Block search indexing with noindex": https://developers.google.com/search/docs/crawling-indexing/block-indexing
- Google Search Central, "Mobile-first indexing best practices": https://developers.google.com/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing
- Google Search Central, "How HTTP status codes, and network and DNS errors affect Google Search": https://developers.google.com/search/docs/crawling-indexing/http-network-errors
- Google Search Central, "Build and submit a sitemap": https://developers.google.com/search/docs/crawling-indexing/sitemaps/overview
- Google Search Central, "SEO Starter Guide": https://developers.google.com/search/docs/fundamentals/seo-starter-guide
- Google Analytics Help, "About events": https://support.google.com/analytics/answer/9267735
- MDN Web Docs, "Transport Layer Security": https://developer.mozilla.org/en-US/docs/Web/Security/Transport_Layer_Security
Newsletter
One short email when we publish
Notes on AI, image, video and brand work, from the people who do it. No spam.