Website audit checklist: a practical first pass for founders

Set the audit scope before checking boxes

Choose the public domain and the main action a visitor should complete. Include the homepage, one important offer page, and one representative page for each key template, such as pricing or an article. Check while signed out and record the date, device, browser, and pages you could not access.

Keep evidence next to each finding. An unchecked item is not a pass; mark it as not checked when the required access or data is unavailable.

Run the checklist in the order a visitor experiences the site

Open the important public pages in a clean browser session. Follow the link you plan to share and note the final URL after redirects. A page that works only while signed in does not prove a new visitor can reach it.

Complete the main action on desktop and a real phone: submit a contact form, start signup, book a call, or use a safe checkout test route. Look for clear field labels, useful error messages, and a visible success state. Do not place a paid order outside an approved test mode.

Check mobile navigation and layout for sideways scrolling, clipped text, overlapping buttons, inaccessible menus, and hidden primary actions. A responsive preview can help, but does not replace trying the actual page on a phone.

• Open the homepage, main offer, and important page templates while signed out.
• Follow the main action and confirm that errors and success states are understandable.
• Test navigation and the primary action on a phone.
• Record the exact URL, browser, device, date, and result for each check.

Check search access, page signals, and performance separately

Open robots.txt and the sitemap URL directly, then inspect the response and body. A sitemap being readable does not mean every listed page is indexed; check important URLs separately in Search Console. Use the startup SEO launch checklist for a deeper crawlability and metadata pass, and the sitemap troubleshooting guide when the XML endpoint fails.

For key pages, check the title, description, visible heading, canonical URL, and noindex directives. Use PageSpeed Insights for diagnostics and distinguish a lab run from field data about real visits. The current Core Web Vitals guidance covers loading, interaction, and visual stability; write down the page, device category, date, and data type instead of turning one result into a site-wide claim.

• Startup SEO launch checklist
• Sitemap troubleshooting guide
• PageSpeed Insights
• Core Web Vitals guidance
• Google URL Inspection

Review trust, accessibility, and measurement

At the decision point, a visitor should be able to find who the service is for, how it works, what it costs or how access works, and where to get help. Check contact, privacy, terms, and refund information against the actual product and data collection. Remove outdated prices and claims you cannot support.

Make a basic keyboard pass through the important path: focus should be visible, controls reachable, and forms labeled. WAVE can surface issues, but an automated report is not a complete accessibility evaluation. If analytics informs a launch decision, verify the events you rely on in a labeled test session; otherwise mark the item not measured.

• WAVE accessibility evaluation
• W3C evaluation tools

Prioritize findings and know what an audit can prove

Fix blockers on important paths first: a broken route, an inaccessible form, a wrong price, an accidental noindex directive, or a public page returning an error. Then group repeated template issues. For every finding, keep the page or flow, evidence and date, smallest useful fix, and the check that will prove the fix worked.

A manual checklist helps a small team find visible problems; it cannot prove every URL was crawled, guarantee indexing, assess site security, or certify accessibility. Launcholio’s public website analyzer checks public HTML and samples sitemap data. It does not crawl every URL, run a browser-based Lighthouse test, inspect Search Console or analytics, or certify accessibility. Use it as one input, then choose the relevant source or test for the other checks.

• Run the public website analyzer
• SaaS launch checklist

Frequently asked questions

How often should I audit a small website? Run a focused review before a launch, redesign, migration, or pricing change. Retest immediately after changes to routing, forms, checkout, or crawl settings.

Is a website audit the same as an SEO audit? No. SEO reviews focus on search discovery and page signals. A broader website audit also checks visitor flows, mobile usability, content clarity, accessibility, and behavior.

Does a checklist guarantee more traffic or signups? No. It helps find and prioritize issues; measure rankings, visits, and conversions in the relevant Search Console and analytics reports.