Key takeaways
- A website audit checklist works through four layers in order: crawlability, on-page elements, content quality, then conversion, because a fault in an earlier layer makes every measurement in a later one unreliable.
- You can run a website audit yourself with a crawler, Search Console access and a spreadsheet; the part that takes practice is deciding which crawler warnings are worth fixing and which are noise.
- A website audit report is built by recording each finding with the pages it affects, the traffic or revenue at stake, and the effort to fix, then sorting by impact so the top of the list is the work that moves numbers.
- The tools a website audit needs are a crawler, Google Search Console, a Core Web Vitals check such as PageSpeed Insights or Lighthouse, your analytics platform, and a spreadsheet to hold the backlog.
- The two findings that recur on almost every site are index bloat, where a crawl turns up far more URLs than anyone meant to publish, and broken conversion tracking, which makes every other number in the audit suspect.
A website audit checks four layers in order: crawlability, on-page, content, and conversion. Crawl the site first, confirm search engines can reach and render every page you want indexed, then fix the issues that block traffic or revenue before the cosmetic ones. This guide gives you the checklist, the tools, and a way to rank fixes so you work on the 20 items that move numbers instead of the 200 that do not.
Start every audit against a business goal, not a score. A crawler will hand you hundreds of warnings and only a fraction of them change rankings or conversions. Sites that would rather have this process run for them than run it themselves are what our SEO audit services cover.
1. Crawl the site and map what exists
Run a full crawl before you touch anything. Use Screaming Frog for sites under 500,000 URLs and a cloud crawler for larger ones. Match the crawl against three reference lists:
- Your XML sitemap
- Google Search Console indexed pages
- Your CMS page count
When these three numbers disagree, you have orphan pages, index bloat, or a broken sitemap. Say the sitemap lists 12,000 URLs, the crawl finds 18,400, and Search Console reports 9,100 indexed: the crawler is turning up thousands of URLs nobody meant to publish, and Search Console is ignoring thousands more that somebody did. Faceted navigation and paginated archives generate most of that gap.
Record these numbers first:
- Total URLs crawled
- URLs returning 200 vs 3xx vs 4xx vs 5xx
- Indexable vs non-indexable count
- Average response time in milliseconds
- Pages more than 3 clicks from the homepage
Anything slower than 600 ms server response or deeper than 4 clicks goes on the fix list.
2. Check technical foundations
Technical problems suppress everything downstream, so clear them before you judge content. The technical layer has its own deeper SEO audit checklist, and this pass only needs the items that block traffic outright:
- Robots.txt does not block CSS, JS, or any indexable directory
- Canonical tags are self-referencing on primary pages and point correctly on duplicates
- One H1 per page, no accidental noindex on money pages
- HTTPS on every URL with no mixed-content warnings
- 301 redirects resolve in a single hop, no chains longer than 2
- Core Web Vitals pass on mobile: LCP under 2.5 s, INP under 200 ms, CLS under 0.1
Render a sample of 20 template pages with the URL inspection tool. If content that matters appears only after JavaScript runs and the rendered HTML omits it, you have a rendering gap that hides copy and links from indexing.
Status code triage
| Code | Meaning | Action |
|---|---|---|
| 200 | OK | Confirm indexable pages return this |
| 301 | Permanent redirect | Fix chains, update internal links to final URL |
| 302 | Temporary redirect | Change to 301 unless genuinely temporary |
| 404 | Not found | Redirect if it had links or traffic, else leave |
| 5xx | Server error | Escalate to engineering same day |
A page returning 5xx during a crawl is losing every crawl attempt. These get worked first.
3. Audit on-page elements at scale
Export titles, meta descriptions, headings, and word counts, then sort by what is missing or duplicated. On a 2,000-page site you can usually clear 300 issues in a day of templated fixes.
Check these in priority order:
- Title tags: unique, under 60 characters, primary keyword near the front
- Missing or duplicate titles: these are the fastest CTR wins
- Meta descriptions: present on template pages, under 155 characters
- Heading structure: logical H1 to H2 to H3, no skipped levels
- Internal links: every important page has at least 3 internal links pointing in
- Image alt text: descriptive on content images, empty on decorative ones
Sort titles by impressions from Search Console. A page with 40,000 impressions and a 1.2 percent click rate is a bigger prize than a page with 200 impressions and a perfect title.
4. Review content quality and coverage
Pull the last 16 months of organic sessions per URL and split pages into four buckets:
- Growing: rising clicks, leave alone
- Stable performers: protect, refresh yearly
- Decaying: falling clicks, refresh or consolidate
- Zero-traffic: 0 to 5 clicks in 6 months, prune or merge
On most sites 20 to 40 percent of pages sit in the zero-traffic bucket. Merging thin pages into stronger ones and redirecting the old URLs concentrates authority and often lifts the survivor within weeks.
For each decaying page, compare it against the top 3 ranking results and note what they cover that you do not. Add the missing subtopics rather than rewriting from scratch.
5. Test conversion and analytics
Traffic without conversion is a vanity number, so audit the path from landing page to action. Confirm the tracking works before you trust any of it:
- Conversion events fire once per action, not zero times or three
- Key templates have a visible primary call to action above the fold
- Forms submit cleanly on mobile and desktop
- Page speed on top landing pages stays under 2.5 s LCP
- Thank-you or confirmation pages are excluded from indexing
Sort landing pages by sessions and multiply traffic by conversion rate to find the leaks. A page with 8,000 monthly sessions converting at 0.4 percent is worth more attention than one with 300 sessions converting at 6 percent, because the ceiling is higher.
6. Prioritize fixes by impact and effort
Score every issue on two axes: impact on traffic or revenue, and effort to fix. A simple grid sorts the backlog:
| Impact | Effort | Priority |
|---|---|---|
| High | Low | Do this week |
| High | High | Plan and schedule |
| Low | Low | Batch when convenient |
| Low | High | Skip unless forced |
Put the quantified estimate next to each item. Fixing 300 duplicate titles on pages with 500,000 combined impressions at a realistic 0.5 point CTR gain projects to roughly 2,500 extra monthly clicks. That number beats vague notes like improve titles, and it tells stakeholders why the work matters.
Tie the whole audit back to measurement so you can prove the fixes landed. Record baseline clicks, impressions, rankings and conversions for the affected pages before anything ships, then recheck the same figures 60 and 90 days later.
7. Check internal linking and site architecture
Internal links move authority and tell search engines which pages matter, and most sites leak both. The crawl already recorded click depth and inbound link counts, so use them to find the pages that are starved.
- List pages more than 3 clicks from the homepage. Anything important that sits deep is hard for crawlers and users to reach, and it earns less authority than its content deserves.
- Find pages with fewer than 3 internal links pointing in. Your best content is often the most orphaned, because it was published and never linked from anywhere new.
- Check that high-authority pages link down to the pages you want to rank. A strong page passes value only through the links it carries.
- Confirm the main navigation and footer do not bury money pages under menus that dilute their weight.
Fixing internal links is cheap and fast, and it often lifts rankings without any new content at all. Add three or four contextual links from strong pages to a starved one and it can climb within a crawl cycle or two. Architecture is the layer owners skip because no crawler flags it in red, yet it decides how the authority you already have flows through the site.
8. Audit off-page signals and backlinks
A site audit that stops at the domain misses half the ranking picture, because links from other sites still carry weight. You do not need a full backlink campaign to audit the basics, and the checks take under an hour.
- Pull the referring domains and scan for a sudden drop. A lost batch of links can explain a ranking decline that on-page checks never reveal.
- Look for toxic or spam links pointing at money pages. A handful rarely matters, but a flood from a link scheme can drag the whole domain.
- Check that the pages earning the most links are the ones you want to rank. If links point at a blog post instead of the service page, an internal link from the post can pass some of that authority on.
- Compare your referring domain count against the top 3 competitors for a target term. A large gap tells you rankings are held back by authority, not by the page itself.
Off-page signals are slower to change than on-page ones, so treat this layer as a diagnosis of why rankings sit where they do rather than a same-week fix. When the gap is authority, the plan is earned links over months, and knowing that stops you from rewriting a page that was never the problem.
Tools you actually need
- A crawler: Screaming Frog or a cloud equivalent
- Google Search Console for index and query data
- PageSpeed Insights or Lighthouse for Core Web Vitals
- Your analytics platform for sessions and conversions
- A spreadsheet to hold the backlog and priority scores
You do not need a dozen paid platforms. Five tools cover 95 percent of a thorough audit.
Related terms
You may see this topic described with related searches like audit website checklist, seo audit checklist, seo site audit checklist, web audit checklist, and website design audit checklist. Those phrases are useful when they clarify what the reader needs next, but they should still point back to one clear plan.
Related searches such as website technical audit checklist are useful when they clarify what the reader needs next. They should support the same plan rather than pulling the page in several directions at once.
Frequently asked questions
How long does a website audit take?
A focused audit of a 5,000-page site takes 2 to 4 days: half a day to crawl and pull data, 2 days to analyze the four layers, and half a day to write the prioritized backlog. Larger sites with custom rendering can run a week. The analysis is faster than the fixes, which unfold over the following quarter.
How often should I audit my site?
Run a full audit twice a year, and a light technical check monthly using Search Console coverage reports and Core Web Vitals. Any time you migrate a domain, replatform, or redesign a template, audit before and after so you catch regressions while they are cheap to fix.
What is the difference between a technical audit and a full website audit?
A technical audit stops at crawlability, indexing, and site speed. A full website audit adds on-page elements, content quality, and conversion. The technical layer is a subset. You can run it alone when you suspect an indexing problem, but a full audit tells you whether the traffic you earn actually converts.
Which issues should I fix first?
Fix anything blocking indexing or returning server errors first, because those pages earn nothing until resolved. Next take high-impact, low-effort items like duplicate titles and broken internal links. Save cosmetic warnings and low-traffic pages for last. Rank by projected clicks or revenue, not by the crawler's severity color.
Can I run a website audit myself or should I hire an agency?
You can run this checklist yourself with a crawler and Search Console access. The judgment calls, how aggressively to prune content and how to weigh one fix against another, come with reps. Many owners run the checklist to find the red flags, then bring in help for the structural fixes and the content decisions that carry more risk.
What is the most common issue a website audit finds?
Index bloat and thin content top the list on most sites: a crawler finds thousands more URLs than anyone meant to publish, and 20 to 40 percent of pages earn almost no traffic. Broken or duplicate conversion tracking is the second, because it hides which pages actually produce revenue and makes every other number suspect.
How do I create a website audit report?
Group findings by impact, not by tool output. Show the issue, the affected URLs, the evidence, the recommended fix, the priority, and the owner so the report can turn into work instead of another PDF.
What is the tool for website audit?
In this guide, what is the tool for website audit points back to the practical work behind website audit checklist: what matters, what changes first, and how the result should be measured.
Can I do a website audit myself?
Usually, yes, if the work supports a real business goal and someone checks the result after it goes live. If it does not help people find, trust, or convert through the site, it is probably not worth doing.
How much does a website audit cost?
The right budget depends on the amount of research, implementation, QA, reporting, and follow-through required. A useful quote should name the first fixes, the timeline, and the result the work is expected to improve.
How to do a website audit for free?
You can run a basic audit with Search Console, PageSpeed Insights, Analytics, a crawl tool, and manual page checks. Look for indexation issues, broken links, slow templates, tracking gaps, thin pages, and conversion problems before paying for deeper work.