What a Site Scan Finds on a Small Business Website

Most small business sites get built once and then grow sideways. Somebody copies a service page to make the next one, a photo goes up straight off a phone because it was the only shot on hand, and at some point the form plugin gets swapped and the confirmation setting lands back on its default. That's what happens when a site is maintained by people who have other jobs to do. A crawler reads what's on the page today, which is why the same items show up across sites that look nothing alike. Our Indianapolis SEO and AEO work starts from this list, and you can pull your own version of it with the free site audit before you decide what deserves an afternoon. For turning a list of findings into an order of work, which website audit fixes to do first covers the ground.

This one is the cheapest finding on the list to clear, and it turns up on sites of every size. Google's snippet documentation says it “sometimes uses the meta description HTML element if it might give users a more accurate description of the page than content taken directly from the page.” With the field empty, the snippet gets built from whatever text the page happens to have near the top, which on a service page is often a headline and a menu.

The fix is one sentence per page that says what the page is for and who it's for, written for the person reading the result. Google's own advice on triage is worth following if the list is long: “If you don't have time to create a description for every single page, try to prioritize your content; at the very least, create a description for the critical URLs like your home page and popular pages.” Watch the other half of that page too, because copying one description across twenty pages trades an empty field for a duplicate one, and Google says identical descriptions aren't helpful when individual pages appear in results. Either way the work sits with an owner or a marketer in the CMS, five minutes a page, with no developer involved.

Scans flag this whenever a site has four or five service pages spun off the same original. The title field carries the same phrase with the business name tacked on, so every page competes with a headline that says nothing specific. Google is blunt about the standard: “It's important to have distinct text that describes the content of the page in the <title> element for each page on your site.” The documentation also warns against boilerplate titles that vary by only a single piece of information, and notes that Google may rewrite a title link when the page title doesn't reflect the page content.

The fix takes about an hour on a small site. Write each title around the one job that page does and the area it serves, then read the set top to bottom and check that no two could be swapped without anyone noticing. Who does it depends on where the text comes from. If the title is a field in the page editor, you do it. If every page is pulling a pattern from a template, a developer changes the pattern once and all the pages follow.

A scan reports heading structure as a sequence, so it catches a page that goes from a main heading to a third level heading with nothing in between, or a page carrying four top level headings because someone wanted big text four times. The W3C accessibility tutorial states the rule plainly: “Nest headings by their rank (or level). The most important heading has the rank 1, the least important heading rank 6.” It adds that “skipping heading ranks can be confusing and should be avoided where possible.” Screen readers build their page menu from those ranks, and so does anything else that tries to understand how a page is organized.

Fixing it means choosing the level by what the section is, then letting the theme handle how big it looks. Most of the time that's a five minute job in the page editor. When the same jump appears on every page in the report, the level is coming from the template and it's a developer ticket, so send the page URL, the heading text and the level you expect, and nobody has to guess at what you meant.

An image at camera resolution still looks correct on screen, which is how this finding survives one redesign after another. The web.dev guidance puts it well: “The image looks fine, but it is wasting users' data and hurting page performance.” Say a photo comes off the camera 4,000 pixels wide and your layout displays it at 800. That's five times the width, so roughly twenty five times the pixels, and those extra pixels ride along in the file someone downloads on a phone over a truck's hotspot.

The fix at the owner level is to resize before upload, which the free image converter does in the browser with no design software involved. Resize to the width the layout uses, keep the proportions, and save as WebP or JPEG at a quality setting around 80. The developer version of the same fix is responsive images, using srcset and sizes so the browser picks a file that suits the screen, plus width and height attributes so the layout doesn't shift while images load.

A scan can tell you a form exists and where it posts. Finding out that it says nothing after a submit takes a test submission, which is worth doing on every form you own, including the ones on old landing pages. The W3C forms tutorial treats this as basic: “Provide feedback to users about the results of their form submission, whether successful or not.” The same page adds that “success messages are also important to confirm task completion.”

Silence costs real money here. Someone fills the form, sees the page sit there, and either submits again or gives up and calls a competitor. You get a duplicate lead or no lead, and you have no way to tell which. The fix is usually a setting in the form tool: turn on the confirmation message or send the submit to a thank you page, which also gives you something to count as a conversion. Then send yourself a test and confirm the email actually arrives, because a quiet form and a broken delivery look identical from the outside. Custom coded forms need a developer for the same work. Auditing contact friction covers the rest of the path a lead takes.

Scans pull the number from the footer and the contact page, and comparing that to your Google Business Profile is a manual check worth two minutes. Mismatches happen for ordinary reasons: a call tracking number went on the site and never reached the profile, an old line stayed in a footer nobody edits, or a second location page kept a number that's since been disconnected.

Google's guidelines say the profile number “must be under the direct control of the business” and should “connect to your individual business location.” The same page asks you to represent the business the way it's already recognized across signage, stationery and other branding, and it prefers a local number over a central call center line. So pick the number you answer, put it on the profile, and make the footer, the contact page and every location page agree with it. That's an owner job unless the footer number is written into code, and then a developer replaces it once. If the profile itself needs attention beyond the number, profile optimization is its own piece of work.

Take the findings in the order of what a searcher sees and what a lead touches. Titles and descriptions change the result people read before they ever reach you, so they go first. Forms come next because a silent form loses jobs you already paid to get. Images follow, since weight hurts every visit on a phone. The phone number check is last only because it takes two minutes, and it's the one most likely to be costing you calls today. Pace it as a couple of hours a week and a small site clears in a month, which is roughly how fix priority plays out in practice. Then run the crawl again, because a scan that reads a whole site in seconds is quick to repeat and tells you which findings actually cleared.

When you want the current list for your own site, run the free audit and work down what it returns; a scan is useful mostly because it stops the argument about what's actually on the site. If you'd rather hand the whole list to someone who does this every week, that's what our Indianapolis SEO and AEO team works through with local service businesses, and the scan report makes a fine scope document either way.