How to Audit a Website: A Practical Small Business Checklist

Want a short starting point? Use the free website self-check to review eight basics and save your next steps. It uses your answers, not an automated crawl. Use the evidence-based workflow below for a technical review.

How do you audit a website?

List the pages that matter to your business, check whether search engines can access and index them, test the mobile experience and inquiry paths, then review content and search performance. Record the evidence for each issue and verify the fix on the live page.

For a service business, start with the homepage, your main service pages, the contact page, and the pages already receiving search impressions. A useful audit ends with a prioritized repair list, not just a tool score or a recommendation to rebuild everything.

A website audit checklist you can reuse

Add columns for URL, owner, planned fix, completion date, and verification result. Keep before-and-after evidence so you can distinguish a successful deployment from a suggested change.

Set your baseline before editing

Use Google Search Console to compare two complete periods. Keep the same search type, country, and device filters. Review pages and queries together, then separate brand searches from searches for your services.

A page with many impressions and a low CTR may rank too far down to earn many clicks. Review average position and the actual query intent before rewriting its title. Small samples and aggregate averages can mislead, so don't turn every zero-click query into a new page.

Also record qualified inquiries and booked work from your own lead records. Search clicks and revenue answer different questions. Our lead tracking guide explains how to connect the two.

Check crawlability, indexing, and canonical URLs

Inspect the actual URL in Search Console. Confirm whether Google could fetch it, whether indexing is allowed, and which canonical URL Google selected. Compare the selected URL with the page you intend to appear in search.

Check the XML sitemap and robots.txt, then look for accidental noindex directives, redirect loops, broken pages, and contradictory canonicals. Keep private account and checkout states out of search. A sitemap helps discovery; it does not guarantee indexing.

Not every excluded URL is a defect. Redirected URLs, deliberate duplicates, and private pages may be excluded correctly. Investigate important public pages rather than trying to make every URL indexable. Google's URL Inspection documentation explains the report's limits.

Test speed and the mobile experience

Run representative pages through PageSpeed Insights. Review real-user field data where available and use lab diagnostics to investigate likely causes. If a new or low-traffic page has no field data, record that limitation rather than treating it as a pass or failure.

Test a real phone as well. Open the menu, follow a service link, submit an authorized test inquiry, and return to the homepage. Check tables, images, sticky elements, keyboard focus, and error messages. Google retired its standalone Mobile-Friendly Test and Search Console Mobile Usability report; don't rely on those tools for a current audit.

Prioritize the largest observed problems, such as an oversized hero image or a script that blocks interaction. A CDN or a higher tool score doesn't automatically fix the user experience. See how to test website speed for more detail.

Review titles, descriptions, headings, and images

Each indexable page needs a distinct purpose and an accurate title. Use the words customers use when they fit the content. Write the description as a concise explanation of what the visitor will find and why it is useful.

Google has no fixed character requirement for a meta description and may choose a different excerpt for a query. Don't cut out useful meaning just to satisfy an arbitrary count. Its snippet guidance explains how descriptions can be used.

Keep the main heading clear and the heading structure logical. Use descriptive internal links to relevant services and supporting resources. For images, use filenames that describe the subject, useful alt text for meaningful images, and empty alt text for decorative images. Alt text belongs to images, not titles or descriptions.

Check social preview metadata and the favicon as well. They help identify the brand where supported, but don't force a search engine to show a particular icon, thumbnail, or title.

Review content and structured data together

Ask whether the page answers the buyer's actual questions: what you do, where you work, what is included, what affects price, what evidence supports your claims, and what happens after contact.

There is no required word count for ranking. Add details that help the reader, not paragraphs designed to reach a quota. Service-area pages should contain accurate local information, not copies with swapped city names. Google's helpful-content guidance is a useful reference.

Validate supported search features with the Rich Results Test and general schema syntax with the Schema.org validator. Valid markup does not guarantee a rich result. Keep organization, service, article, and image data consistent with what a visitor can actually see.

Verify forms and lead handling

With permission, submit a clearly labeled test inquiry. Confirm the success message, delivery destination, CRM record if applicable, and ownership of the response. Check required fields, invalid inputs, duplicate submissions, and the mobile keyboard experience.

Use test data rather than a customer's personal information. Verify analytics events without treating test submissions as real leads. If traffic is reasonable but qualified inquiries are weak, investigate the page's offer, trust signals, form friction, and follow-up process before spending more on acquisition.

Turn the findings into a repair plan

Fix blocked lead paths and important inaccessible pages before cosmetic issues. Then address the pages with relevant demand, realistic ranking opportunities, and a clear connection to the services you sell.

For each change, record what you expected to improve. After deployment, verify the live HTML, forms, redirects, and assets. Measure search results after recrawling over comparable periods, with clicks, impressions, CTR, and position together. Track conversions separately.

If the audit shows that the existing site is repairable, repair it. If the required changes span structure, content, performance, and lead handling, compare that work with a rebuild. Review webIQ's package scope, pricing, and website examples to make an informed comparison.

Frequently Asked Questions

Can I audit a small business website myself?

You can gather useful evidence with Search Console, PageSpeed Insights, a browser, and authorized form tests. Some fixes need development help, but the checklist lets you identify and prioritize them before hiring anyone.

Why do I have impressions but few clicks?

Possible reasons include low ranking positions, mismatched intent, weak snippets, competing search features, and a small sample. Filter by page and query, compare positions, and review the results before deciding which explanation fits.

How often should I audit the site?

Check inquiry delivery and important pages regularly, and repeat verification after changes to content, hosting, forms, or tracking. Schedule broader reviews around the site's update cycle and available performance data.