Introduction
A useful website audit checklist is ordered by how close each problem sits to a lead. Start with whether a visitor can complete the main task, then whether the enquiry actually reaches a person, then performance, indexing and accessibility. Each finding needs three things: evidence, a severity, and a named owner. A hundred unranked items give a team nothing to act on, while twelve ranked findings with screenshots and owners get fixed. The sections below show how to run that kind of review on a business site, what to record, and how to decide what to repair first.
Start the audit with the lead path, not the homepage
Most audits begin with a crawler report and end with a long list of minor warnings. A better starting point is the route a prospect takes: arrive from search or an ad, find the relevant page, understand the offer, and submit an enquiry, call or booking. Walk that route yourself on a phone and a desktop, in a private browser window, as someone who has never seen the site.
This is the core of a business website audit. It asks whether the site does its job, which is a different question from whether the code is tidy. A site can score well on automated tools and still hide its phone number behind a menu or send form submissions to an inbox nobody reads.
Record every finding with evidence, severity and an owner
Before testing anything, agree on how findings are written down. Each row in the audit sheet should carry:
- What happened: one plain sentence, such as the form shows a success message but no email arrives.
- Evidence: a screenshot, screen recording, URL, device and browser, and the date tested.
- Severity: blocks a lead, slows a lead, or is a hygiene issue.
- Owner: a person or team, such as marketing, the developer, or whoever manages email.
- Status: open, in progress, fixed and retested.
Evidence matters because it ends arguments. Without it, a finding like the site feels slow is an opinion. With a recorded test on a mid-range phone over a throttled connection, it is a defect someone can reproduce. The owner field matters just as much, since a problem assigned to everyone is usually fixed by no one.
Check task completion and lead delivery first
These are the highest-severity checks because a failure here means leads are lost outright.
Forms, calls and bookings
Submit every form with realistic data, including one entry with a long name or an apostrophe. Confirm three things: the visitor sees a clear confirmation, the notification reaches the right inbox, and the lead lands in the CRM or spreadsheet if one is connected. Check spam folders, since mail sent from a website to a business address is often filtered. Tap every phone and WhatsApp link on a real phone. Try submitting with a required field empty and read the error message: does it say what to fix?
Calls to action and page intent
For each key service page, ask whether a stranger could say what is offered, for whom, and what to do next within a few seconds. Look for a call to action that appears only in the footer, buttons that look identical but lead to different places, and pop-ups that cover the form on small screens.
Review performance where visitors actually feel it
Run lab tools for a baseline, but weigh them against what you see on a real mid-range phone. Look at the pages that receive paid or search traffic, not only the homepage. Typical culprits are oversized hero images, several font files, chat widgets and tag-manager scripts that nobody has reviewed in years, and sliders that load full-size images for every slide.
The tradeoff is rarely speed against everything else. Removing a heavy script may cost you a tracking feature or a design flourish, so record what each third-party script is for and who relies on it. If no one can answer, that is itself a finding. Fix the changes that improve the lead path first, such as the form page and top landing pages, before trimming the rest of the site.
Run a technical website audit for indexing and crawl problems
A technical website audit checks whether search engines can find, read and index the pages you want found. Confirm the following with your search console account and a crawl:
- Important pages return a normal status and are not blocked by robots rules or a stray noindex tag left from development.
- Each page has a self-consistent canonical URL, and the www, non-www, http and https versions resolve to one version.
- The XML sitemap lists live pages you want indexed and excludes redirected or removed ones.
- Old URLs redirect to relevant replacements rather than the homepage or a dead end.
- Titles and descriptions are not duplicated across service pages.
Indexing problems are easy to misread. A page missing from the index may be low quality, new, duplicated or blocked, and each has a different fix. Record the exact status reported by the tool as your evidence, and avoid promising that a fix will change rankings or traffic, since that depends on factors outside your site.
Free quote · reply within 24 hours
Want us to look at your rankings?
Send your site and the searches you want to win. You get a written plan and a fixed quote within 24 hours.
Spot-check accessibility on the pages that matter
Automated checkers find only some accessibility issues, so combine one with manual checks. Navigate the lead path using only the keyboard: can you reach the menu, see where focus is, and submit the form? Check that form fields have visible labels rather than placeholder text alone, that error messages are readable and not conveyed by colour alone, that images carrying meaning have useful alternative text, and that text contrast is sufficient on buttons. These checks improve usability for everyone, but a checklist alone cannot establish legal or regulatory conformance. If your sector has specific obligations, ask a qualified professional to review them.
Hypothetical example: a services firm with a quiet inbox
Illustrative scenario, not a real client. A small consultancy notices fewer enquiries after a redesign. The audit starts with the lead path. Testing shows the contact form displays a success message, but notifications go to a former employee's mailbox. That is a severity one finding with a screenshot and an owner: the person who manages email settings. Next, the service pages load a large background video on mobile, a severity two item owned by the developer. The crawl then shows the sitemap still lists the old URLs, which redirect to the homepage, a severity two item for whoever handles SEO. Accessibility checks find placeholder-only labels, a severity three item. The order of repair follows the severity, not the order in which the tools produced warnings.
Budgeting the audit effort
An audit has a cost in hours, and it helps to scope it before starting. ALL figures in the table below, including the hourly rate and totals, are hypothetical assumptions for arithmetic only, not quotes, market averages or vendor fees.
| Audit area | Assumed hours | Assumed rate per hour (INR) | Illustrative cost (INR) |
|---|---|---|---|
| Task, form and lead delivery testing | 4 | 1,500 | 6,000 |
| Performance and mobile checks | 3 | 1,500 | 4,500 |
| Indexing and crawl review | 3 | 1,500 | 4,500 |
| Accessibility spot checks | 3 | 1,500 | 4,500 |
| Findings report and prioritisation | 2 | 1,500 | 3,000 |
| Total | 15 | 1,500 | 22,500 |
The arithmetic is 15 hours multiplied by the assumed rate. The total excludes applicable taxes, which must be confirmed separately, as well as any paid tool subscriptions, the work of fixing the findings, content rewriting, migration work and ongoing maintenance. Staff hours spent on an audit are not automatically cash saved or cash spent, so treat the figure as a way to compare scopes rather than a forecast of return.
Decide what to fix first
Sort the sheet by severity, then by effort. Anything that blocks a lead, such as a broken form or misrouted notification, is fixed immediately. Quick wins with clear evidence come next, followed by larger items that need design or development time. Retest each fix on the same device and record the result, so the sheet shows what changed. Repeat the lead path tests after any release, plugin update or hosting change, because those are common moments for quiet breakage.
Conclusion
Begin with a single hour: submit every form on the site, confirm who receives each one, and write the result in a sheet with evidence and an owner. That one test often reveals the most expensive problem on the site and costs nothing beyond your time.
If you would like a second pair of eyes on the findings or help prioritising the fixes, you can contact NextGen Fusion to talk through your site, with no obligation.
Free quote · reply within 24 hours
Want a fixed price for your project?
Send your site and the searches you want to win. You get a written plan and a fixed quote within 24 hours.
Keep reading on SEO
- How to Redesign Your Website Without Losing SEO TrafficPlan a website redesign without losing SEO: inventory URLs, keep key content, map one-to-one redirects, and check indexing after launch.
- Core Web Vitals Explained for Business OwnersCore Web Vitals explained for business owners: what LCP, INP and CLS measure, the pass thresholds, field versus lab data, and fixes to prioritise.
- How to get your business mentioned in ChatGPT, Perplexity and Google AI answersHow to get your business mentioned in ChatGPT, Perplexity and Google AI answers: be easy to find, easy to understand, easy to quote and mentioned by others.

