Guides

Small-business SEO audit: three checks to start with

Check the pages that matter using Search Console, PageSpeed Insights and a phone.

Updated on 4 min
A laptop showing a chart, a phone displaying a web page and a checklist on paper.

For a first SEO audit on a small site, choose the pages that should attract customers or inquiries. Start with the home page, one service page and a guide or contact page that matters to the business. For each, check whether Google can index it, what search it should answer and how it works on a phone.

1. Check access, indexing and the sitemap

Open the exact URL in a browser without signing in. If it returns a 404, check whether the page is missing or you have the wrong address. If it redirects, note its destination and decide which address you want to appear in search. Then use URL Inspection in Google Search Console to compare Google's indexed status with the live URL test.

For a page you want people to find, the live test should be able to fetch it and report that indexing is allowed. Check for crawl blocks, noindex and the declared canonical URL. The canonical tells Google which address you prefer. If Google has already indexed the page, the report may show which canonical Google selected.

Open the sitemap and check that it contains the final URL you want people to find. For a redirected URL, list the canonical destination in the sitemap. If Search Console already knows the sitemap, check when Google last read it. The sitemap helps Google discover the address. Check the individual URL report for its indexing status. Google’s sitemap guide.

2. Compare what people search for with what they see

In the Search Console Performance report, filter search traffic by the URL you are reviewing. Look at queries with impressions and how they changed over the selected period. If there is little data, start from questions your customers actually ask and return to the report as the page gathers more data.

Review the SEO title, main heading, opening copy and next action. For example, someone searching for “business software maintenance” should quickly see which systems you cover, what work you assess and how to describe a problem. Link to the page from a relevant section with text that tells people what they will find.

If a page has impressions and few clicks, read the queries and review the results Google shows for them. Before rewriting the title, check whether the content answers what people are looking for. Consider clicks alongside position, device and the other search results.

3. Try the mobile page and use PageSpeed Insights

Open the page on a real phone. Read the opening, try the navigation and reach the main button or form. Then test that page in PageSpeed Insights using the mobile view. Google distinguishes real-user data from lab measurements. If page-level data is missing or the report shows site-wide data, use the lab test to identify issues to investigate.

  • LCP measures when the largest visible content element appears. If the opening image is slow, check how it loads.
  • INP describes how responsive the page is to interactions. If a menu or form responds slowly, repeat the action on a phone and have the relevant scripts examined.
  • CLS measures unexpected movement on the page. If a button shifts while the page loads, check whether images and components reserve enough space.

Record the issue that affects using the page and how you will verify the fix. If you optimize the opening image, repeat the test on the same URL and check that the image still communicates clearly, including on the connection your audience is likely to use.

Turn the findings into a list of fixes

Hypothetical examples of priorities and verification
SignalFirst fixHow to verify it
A service page returns 404 but is listed in the sitemapRestore it or update the reference to the appropriate final URL.Open the correct URL, check the sitemap and repeat the live test in Search Console.
The title describes general services but the page answers a specific queryMake the offer clear in the title and opening. Check links from related pages.Confirm that the page quickly explains who it serves, then review queries over a comparable period.
The form moves while the page loadsFind the late-loading element and reserve enough space for it.Repeat the journey on a phone and confirm the form stays in place.

Assign an owner to each fix and record when to check it again. To extend the audit to metadata, structured data and other technical areas, use the technical SEO checklist for a business website.

Sources

Tags

#technical SEO#Search Console#Core Web Vitals

Written by

Matteo Lucrezio

Matteo Lucrezio

Startupper | Lead Software Engineer

Book 30 minutes with Matteo

Leave your contact details, then choose a day and time for a free 30-minute initial conversation. Any technical assessment and subsequent work are agreed separately.

How can we help?

Enter your contact details to continue to the calendar.

We use it to follow up on your request and manage the booking. This does not subscribe you to promotional messages.

We save your details immediately to handle your request. They also stay in this browser for 24 hours, so you do not have to type them again if you reload the page.

No suitable time or prefer to write? Email me at matteo.lucrezio@lucz.dev.