Local SEO

A website audit you can turn into a useful work list

Audit search access, customer tasks, content and mobile performance. Record evidence and priorities instead of collecting scores without a plan.

RTRobert TicknerWeb designer, Melbourne
Updated 3 min read
Website audit illustration with a page layout and review points.
On this page
  1. Check search access separately from rankings
  2. Follow one customer task from beginning to end
  3. Review what each page actually answers
  4. Check mobile performance with context
  5. Prioritise by effect and confidence
  6. Check the result after the work

An audit is only useful if it helps you decide what to fix. A folder of screenshots and performance scores is not yet a plan.

Start with the pages that matter to the business: Home, main services and Contact. Check whether people can find them, understand them and complete the next step. Then record the evidence and the action each issue needs.

Check search access separately from rankings

Use Search Console to inspect important URLs. Look at the indexing state, the last crawl information and the canonical Google has selected where available. Check the live page when you need to test current access.

Google’s Page indexing report guidance distinguishes site-wide reports from individual URL inspection. An unindexed URL can have several causes; it is not, by itself, proof of a spam penalty.

Record the reason shown rather than replacing it with a guess. A redirect, noindex instruction, duplicate page and crawled-but-not-indexed page need different investigations. The SEO build guide explains the basic settings to review.

Follow one customer task from beginning to end

Choose a realistic task, such as requesting a quote for a main service. Start on Home, find the service details and open the contact route. Notice where you hesitate or need information that is missing.

Check calls and forms on a phone. If you test a deployed form, use an agreed test enquiry and confirm that the right person receives it. Preview appearance alone does not prove delivery.

The website diagnosis guide helps distinguish low visibility from an unclear page or broken contact route. Those findings should not all receive the same recommendation.

Review what each page actually answers

Write down the main question beside each page. Does the content answer it early? Does it explain the scope, process and next action? Do several pages repeat the same explanation without adding anything useful?

Check service claims, locations, prices and business details against current information. Mark anything the owner needs to confirm. A redesign plan can use this record to preserve useful content and replace the rest deliberately.

For local businesses, compare the website details with the Business Profile. The local search guide covers that connection. A mismatch in hours or phone numbers is a practical customer problem even before you consider search visibility.

Check mobile performance with context

Run PageSpeed Insights on important page types. Separate simulated test results from field data when the tool provides it. A low test score can point to work, but it does not tell you how many enquiries were lost.

Google’s Web Vitals guidance covers loading, responsiveness and visual stability. Look for the cause on the actual page: heavy images, added scripts or a layout that shifts while loading. The mobile website checks pair those measurements with real customer tasks.

Repeat a test when investigating a change, using comparable conditions. Avoid turning one unusually good run into a claim about all visitors.

Prioritise by effect and confidence

On a small screen, scroll the table to view every column.

Finding Evidence Next action Priority
Enquiries do not arrive Controlled test and delivery check Fix delivery configuration High
Main service is unclear Missing scope on service page Draft and approve the explanation High
A key URL is not indexed Search Console reason Investigate that specific reason Depends on cause
Optional animation is heavy Repeatable page test Simplify and compare again After essential tasks

Assign an owner and a review date. Separate a confirmed problem from an idea worth testing. This keeps the audit from becoming an expensive list of speculative fixes.

Check the result after the work

Use the launch checklist when fixes involve a new deployment. Confirm the customer tasks again and record which search or content issues still need review.

For a local business, our local SEO service can help turn the findings into a profile-and-website plan. Bring the recorded problems and available reports so the next conversation starts with evidence.

Filed under Local SEO
Robert Tickner, founder of Web Design Studio Melbourne.

Robert Tickner

Founder and web designer, Web Design Studio Melbourne

Robert works directly with small businesses on website design, content structure and local SEO. His approach starts with the business offer and the customer’s next step.

First published .

Prepared with AI assistance. Examples labelled illustrative are not client results.

Still have a question? Talk to an expert.

AI websites typically take 24–48 hours once your content is ready. A custom build takes about a week. Let’s work out which option fits your business.