Small Business SEO Audit: A Practical Checklist

Choose five pages and one business goal

Pick your homepage, two important service or product pages, a helpful guide and your contact page. For a very small site, review every page. Write down the action each page should support: booking a repair, requesting a quote, buying a product or answering a customer question.

Create a simple audit sheet with columns for URL, purpose, finding, evidence, priority, owner and date checked. Keep screenshots or the exact error beside each finding. “SEO is bad” is not an actionable finding; “the repair page returns 404 from the main navigation” is.

Use your own Search Console data to choose additional pages. A page already appearing for a relevant search deserves attention, but impressions are appearances in search results, not visitors. Treat a few impressions as an early clue rather than proof of demand.

1. Fix access and indexing problems first

Open each selected URL on a phone and a computer. Check that it loads the intended page, uses HTTPS and shows the main content without requiring a login. Follow links from your navigation rather than testing only a saved bookmark. A broken route can leave a good page unreachable.

In Search Console, inspect the URL and review the indexing status, selected canonical and any exclusion reason. Check for an accidental noindex instruction. An indexable page can still be excluded, so do not label a page “indexed” just because its HTML permits indexing.

Review robots.txt before changing it. Robots.txt controls crawling; it is not a reliable way to remove a page from search. A crawler generally needs to access a page to see its noindex instruction. Keep private information behind proper access controls.

Check your XML sitemap for current, preferred URLs with the XML-Sitemap-Validator. A sitemap helps discovery but does not guarantee indexing. If an old page has a close replacement, redirect it permanently to that replacement. Do not send every removed URL to the homepage.

Benutzen Sie die Sitemap-URL-Extraktor to make an audit list from XML, then inspect supplied page HTML with the Canonical-Tag-Prüfer. For translated versions of the same page, the Hreflang-Tag-Generator prepares alternate-language tags; verify each live page and its return links separately.

2. Make each page answer a specific customer question

Read the main heading and opening paragraph as a first-time customer. Can you tell what the business offers, whom it serves and how to take the next step? Replace generic slogans with concrete information. Include a service area only when you actually serve it.

A service page may need scope, exclusions, how booking works and what a customer should prepare. A product page may need dimensions, compatibility and delivery details. Add those details from your actual operations rather than copying a competitor or inventing credentials.

Look for pages that repeat the same offer with only a town name changed. Decide whether they have distinct information worth keeping. One useful service page can be a better customer experience than several pages that all answer the same question incompletely.

Benutzen Sie die Prüfer der Überschriftenstruktur to inspect headings in supplied HTML. It can help you spot structural problems, but it cannot decide whether the advice is accurate or the page is useful. Read the page and test the customer journey yourself.

If your page includes structured data, inspect its syntax with the JSON-LD-Validator. The LocalBusiness-Schema-Generator and Breadcrumb-Schema-Generator create editable markup from your actual details. Match it to visible content and check Google’s type-specific requirements before publishing.

3. Review titles, descriptions and links together

Benutzen Sie die Meta-Tag-Analysator to inspect the published title, description and canonical. Give each important page a clear title that matches its content. Write a description that explains what a visitor can find or do, using details actually present on the page.

Google may generate a different title link or snippet. A preview and a character counter are editing aids, not a promise of the final search appearance. Avoid keyword lists and unsupported claims such as “number one” when an accurate service description would help more.

Check that your homepage links to important services and that relevant guides link to the next useful page. Use descriptive link text: “book a bike repair” tells someone more than “click here”. Confirm each destination works and does what the surrounding text promises.

Benutzen Sie die SERP-Snippet-Vorschau to review a sample result. Keep the page, its heading and its metadata consistent rather than rewriting only the search snippet to chase clicks.

4. Test mobile usability and the actual enquiry path

On your phone, read a service page, open the menu, tap the contact button and complete a test enquiry using clearly labelled test details. Confirm the expected confirmation appears and the business receives it. Remove the test record if your workflow permits it.

Look for text that needs zooming, buttons hidden by overlays, unreadable colour combinations and forms that lose entered data after an error. These observations belong in the audit even when an automated score looks good.

Use Seitenladezeit-Prüfer as one diagnostic signal and record the URL, device and test conditions. Inspect large images and unnecessary scripts when loading is slow. Test again after a meaningful change under comparable conditions; a single score is not a ranking forecast.

Check contact information, opening hours and service details against the business’s actual records. Give customers a clear way to reach you and keep evidence of experience specific: real examples with permission, genuine staff information or a transparent explanation of your process.

Worked example: auditing a local repair business

Example Cycles is a fictional bicycle workshop. Its goal is to get repair bookings. In this example, the homepage loads normally, but the navigation still points to /bike-service, which returns 404. The replacement /bike-repairs page exists and the booking form works.

Finding one: a customer cannot reach the repair page through the menu. Evidence: the menu destination returns 404. Action: update the menu to /bike-repairs and add a permanent redirect from /bike-service to the matching replacement. Verify both routes and record the result. This is the first priority because it interrupts a real task.

Finding two: the repair page title is “Services” and the page does not explain which repairs are offered. Action: list the actual repair types and booking steps, then use a specific title such as “Bike repairs in Bristol | Example Cycles” if Bristol is its true service area.

Finding three: a large workshop photo slows the first mobile view. Action: export an appropriately sized image, inspect its appearance and compare loading under the same conditions. Keep the original. These findings are illustrative, not measurements of a real business or promises of a traffic increase.

Turn the audit into a short action plan

Fix blockers first: broken important pages, accidental indexing restrictions and forms that cannot be completed. Next, improve unclear service information, missing useful links and misleading metadata. Put cosmetic refinements behind issues that stop a customer finishing a task.

For each action, name an owner and a way to verify completion. “Fix repair link” becomes “update the navigation URL, confirm the old URL redirects once to the replacement, and test booking from mobile”. Keep the original evidence so someone else can review the change.

Record the publication date of content changes. After Google has had time to recrawl and you have collected enough data, compare equal periods in Search Console using relevant queries and pages. Watch enquiries or sales separately. More impressions with no additional clicks is increased visibility, not increased visits.

Repeat the focused audit when you launch an important page, change navigation or move URLs. The aim is a maintained website and a useful record of decisions, not an impressive-looking report that nobody acts on.