A site audit is a structured review of the technical, content, security, performance, and reliability issues that can affect a website. I recommend it to site owners, marketers, developers, and agencies that need a clear plan for protecting search visibility and user trust. The checklist below helps you identify problems, rank them by impact, and confirm that fixes work.
Key takeaways for a useful website audit
- Start with important user journeys and page templates, not an unfiltered list of warnings.
- Check crawlability, content, speed, security, resilience, and machine-readable signals.
- Prioritize by impact and reach, then give each fix an owner and a retest.
- Use recurring checks for issues that can change without a redesign or content release.
Define the audit scope before checking individual pages
A good audit begins with the website’s purpose. Choose the actions that matter, such as completing a purchase, submitting a lead form, reading a support article, or finding a local service. This keeps the review focused on real business outcomes rather than an arbitrary count of technical findings.
List the important page types and user journeys. For an online store, that could include the homepage, category pages, product pages, search results, cart, and checkout. For a service business, include location pages, service details, contact forms, and booking flows. Review representative templates as well as any high-value pages with unique layouts.
Set a baseline before changing anything. Record the date, pages checked, known issues, and current performance or search indicators available to your team. This makes it easier to distinguish a newly introduced problem from an existing one and to check whether a fix improved the situation.
Check crawling, indexing, and site structure first
Search engines need to discover and access the pages you want them to find. Start with the site’s robots directives, XML sitemap, status codes, redirects, canonical signals, and internal links. Confirm that important pages are available to crawlers and that pages intended to stay out of search are deliberately handled.
- Look for important URLs returning errors, redirecting through unnecessary hops, or resolving to the wrong destination.
- Compare sitemap entries with the pages you want indexed, and remove outdated or unintended URLs.
- Check that navigation and contextual links lead to key pages instead of leaving them isolated.
- Review canonical and noindex settings on page templates, especially after migrations or redesigns.
A sitemap review can help surface URLs that were omitted or left behind. I also check robots rules against the pages that matter, because a small template or configuration change can affect many URLs at once.
Review page content, metadata, and structure
Every important page should tell visitors what it offers and make its main topic easy to understand. Review page titles, descriptions, headings, image alternatives, and internal links on the pages in scope. Look for duplicate or missing titles, vague headings, outdated information, and content that no longer supports the page’s purpose.
Check whether each page answers the visitor’s likely question without forcing them to infer key details. For commercial pages, confirm that product or service information, pricing context, and next steps are clear. For informational pages, check accuracy, useful organization, and links to related resources. Use a page title review to catch missing or inconsistent titles, then assess the full page in context.
Structured data can help machines interpret eligible page details, but it must match visible, accurate content. Review markup after content or template changes, and do not add claims that a visitor cannot verify on the page. Clear headings, descriptive links, and useful image alt text also make content easier to interpret across different interfaces.
Test performance on real user journeys
Performance checks should focus on pages people actually use, not just a single homepage score. Test representative templates on mobile and desktop, and inspect the parts of the experience that can delay or disrupt action: large images, third-party scripts, slow server responses, and layout shifts.
Combine lab testing with field data when it is available to your team. Field measurements help show how pages behave for actual visitors, while a controlled test can help isolate a suspected cause. For a deeper review, use a page speed monitoring approach and compare the same key pages after changes.
Prioritize performance problems that affect a high-value path or appear across a shared template. An oversized hero image repeated across landing pages may deserve attention before a minor delay on a rarely visited page. Retest the journey from start to finish after optimizing, since a faster page is not useful if a form or checkout flow stops working.
Inspect security and reliability before they become user-facing failures
Security and resilience checks help protect visitor trust and keep important functions available. Review certificate validity, HTTPS redirects, mixed content, security headers, cookie behavior, and exposed software risks where applicable. Also check error pages, domain and DNS configuration, backups, and how the team detects an outage.
Make sure the secure version of each important page loads consistently and that outdated HTTP URLs redirect appropriately. A review of certificate expiration risks can help teams include renewal ownership in their routine. For transactional sites, test account access and payment or form flows without exposing real customer data.
Resilience means more than checking whether the homepage responds. Identify the pages and services that must remain available, decide who receives alerts, and document how to recover. Monitoring downtime can help reveal interruptions that a one-time review would miss.
Rank findings by impact, reach, and verification
Audit reports become useful when they guide decisions. I rank each issue by its likely effect on visitors or business goals, the number of pages affected, and the effort or risk involved in fixing it. A sitewide issue that blocks important pages should usually outrank a cosmetic defect on a single low-priority URL.
| Priority | Typical signal | Next action |
|---|---|---|
| Urgent | Critical journeys fail, key pages are inaccessible, or a broad configuration problem affects the site. | Assign an owner immediately and verify the fix across affected templates. |
| High | Several valuable pages have a shared content, indexing, security, or performance issue. | Schedule a near-term fix and check representative URLs after release. |
| Planned | A limited issue has low immediate impact or a reasonable workaround. | Add it to the backlog with a due date and a clear acceptance check. |
For example, if every product page inherits the same incorrect indexing directive, address the shared template before polishing one product description. A workflow board can help teams sort findings by urgency, assign responsibility, and track retests.
Turn one-time findings into ongoing website health checks
A one-time audit captures a moment; recurring checks help catch changes introduced later by deployments, plugins, content edits, DNS updates, or expiring certificates. Choose monitoring frequency based on the risk and volatility of each check. A critical checkout or security signal merits faster attention than a low-impact editorial detail.
37 Audits supports this ongoing approach with continuous auditing, alerts, and more than 60 specialized auditors covering areas such as certificates, content security policy, cookies, headings, HTTP, image alt text, sitemaps, schema, robots rules, DNS mail records, and page performance. I would use automated findings as a starting point, then confirm the context and user impact before assigning a fix.
Keep a short audit log with the finding, affected pages, priority, owner, date found, fix date, and retest result. That record helps teams recognize recurring problems and check whether a fix stayed effective after later releases. A consistent process turns technical checks into a practical maintenance routine.
Frequently asked questions
What is a site audit?
A site audit is a structured review of a website’s technical setup, content, security, performance, and reliability. It helps identify issues that can block crawling, confuse visitors, weaken trust, or interrupt service. A useful audit records each finding, its impact, who owns the fix, and how to confirm the issue is resolved.
What are the seven steps in a site audit?
I use seven steps: define the audit scope, review crawlability and indexing, inspect key pages and content, test performance and mobile usability, check security and reliability, validate structured data and machine readability, then assign fixes and verify them. Record an owner and a retest method for every issue that needs action.
Which areas should a website audit cover?
Review technical SEO, page content, performance, security, resilience, and machine readability. Check how search crawlers access important pages, whether visitors can use them on mobile, whether key templates load reliably, and whether content and structured data communicate accurate information. The emphasis should reflect your site’s goals and highest-value user journeys.
How often should I audit my website?
Run a full review before major launches or redesigns, and repeat it on a regular schedule that fits how often your site changes. I also recommend continuous monitoring for critical technical checks, because a certificate, redirect, or availability problem can appear between scheduled reviews. Recheck affected pages after each meaningful fix.
How should I prioritize website audit issues?
Prioritize issues by their likely impact, how many pages or users they affect, and how quickly they can be fixed. A broken checkout path or a sitewide indexing block usually deserves attention before a minor formatting issue on one page. Assign an owner, a deadline, and a clear verification step to each priority finding.
