For most small business sites, the audit worth running is narrow. Check the handful of pages that are supposed to bring you work. Save the full site-wide crawl for once or twice a year, when something might be broken everywhere at once — a bad robots rule after a rebuild, a stray noindex left on by a developer. The rest of the time a crawl hands you a color-coded list of warnings that nobody works through.
That’s not how a typical SEO audit checklist reads. Fourteen steps get listed, each with its own heading, and the layout implies all fourteen deserve the same afternoon. They don’t. Not on a thirty-page site in Port St. Lucie run by two people who also answer the phone.
Two Audits, Two Different Jobs
The two approaches share vocabulary and almost nothing else. One is a machine reading your whole site and grading it against a generic rule set. The other is a person opening the five or six pages your business depends on and asking whether each one earns the call.
| What you’re weighing. | Site-wide crawl. | Money-page audit. |
|---|---|---|
| What it finds. | Breakage that repeats across many URLs. | Gaps between what a page says and what a buyer needs. |
| How long it takes. | A few hours, mostly waiting on the crawler. | About an hour per page if you’re honest about it. |
| Who can run it. | Someone with crawler access and search data. | Anyone who knows the business and the customer. |
| What the customer notices. | Usually nothing, unless something was badly broken. | The page answers the question they arrived with. |
| When it goes first. | After a rebuild, a move, or a sudden drop. | When traffic exists but the phone stays quiet. |
What a Site-Wide Crawl Is Good At
A crawler sees your site the way a machine does, all at once. That’s the whole value. You can’t spot a canonical tag pointing at the wrong URL by looking at a page in your browser, and you can’t tell how many parameter URLs are sitting in the index by scrolling your own menu.
So when something systemic breaks, the crawl is the only tool that catches it. A rebuild that left the staging noindex in place. A redirect chain three hops deep. A sitemap still listing pages you deleted in the spring. One fix, and every page it touched comes back.
Sequence matters more than coverage here, and where an SEO audit should start is not with page speed. Can Google reach the page, is Google allowed to keep it, then everything a human would notice.
Why Most Audit Reports Never Get Fixed
Severity grading is the problem. An audit tool doesn’t know your business, so it grades every site against the same standard — the one written for publishers with enormous catalogs. Crawl budget is the clearest example of that mismatch.
Google’s crawl budget documentation says out loud who it was written for: “Large sites (1 million+ unique pages) with content that changes moderately often (once a week).” If your site has forty pages, crawl budget isn’t your problem, whatever color the report paints it.
An SEO audit checklist can’t know which of its items apply to you, so it flags all of them. Then the report lands, the warning count is intimidating, and the whole thing gets filed. Nothing moves.
The findings that do matter on a small site tend to be dull. Thin service pages. Two location pages built from one paragraph with the city name swapped, which is how near-duplicate city pages quietly split your own rankings.
What a Crawler Can’t Grade on Your Best Pages
Open your main service page and read it as a stranger who needs the work done today. Does it say what you do, where you do it, and what happens after they call? A crawler passes that page if the title tag is short enough. It holds no opinion about whether the page is convincing.
Google’s own guidance for content quality reads like a self-assessment rather than a scorecard. Its content quality questions are ones you have to answer about your own page. The first one is blunt: Does the content provide original information, reporting, research, or analysis? No crawler answers that for you.
Owners make poor judges of their own pages and worse judges of their own rankings. Typing your own business name into Google returns a result shaped by your location, your history, and the account you’re signed into. Ask someone across town what they see.
Then work through the things a tool never checks. This is the short list worth running on every page that’s supposed to produce a call.
- Does the first screen name the service and the area, before any scrolling?
- Is the phone number tappable on a phone, and does the form send somewhere a person reads?
- Is there proof on the page — photos of real work, a real address, the name of someone who did it?
- Does the page answer the objection a buyer raises on the phone, or does it dodge it?
- If a competitor’s page sat beside it, would a stranger pick yours, and could you say why?
None of that is technical. All of it decides whether a visit turns into work. And every item is something you can judge in a few minutes without a single tool, which is why it tends to get skipped in favor of the parts that produce a satisfying report.
Which Audit Should You Run First?
Run the site-wide crawl first if something changed recently — a rebuild, a move to a new domain, a platform switch, or a drop you can point to on a calendar. Otherwise start with your money pages. Traffic that arrives and leaves without calling is a page problem, not a crawl problem.
You just rebuilt or moved the site
Crawl first, and do it this week. Rebuilds are where sitewide mistakes get born. A staging robots file, a redirect map nobody finished, a URL structure that changed without anyone mapping the old paths — none of it shows on the page, and all of it shows in rankings long after you’d want to know.
Traffic looks fine but nobody calls
Money pages, every time. The crawl comes back clean and tells you nothing. Read the page, then watch what a visitor has to do to reach you. Count the taps. It also helps to settle in advance which numbers should move if the fix works, because “more traffic” isn’t a result you can act on.
Rankings slid and you can’t say when
Do both, in that order. Crawl to rule out breakage, then read the pages that lost ground. Most slides turn out to be content rather than code. But the cheap check goes first.
The site is brand new
Neither, yet. A new site needs pages that exist and a sitemap that lists them. Come back in ninety days, once there’s enough search data to audit against.
If reading your own pages that way sounds like a job you’d rather hand off, a search engagement that starts with your revenue pages is how we scope it.
Where the Money-Page Audit Falls Short
Reading six pages closely will miss the thing that’s capping all of them. A sitewide canonical pointing every page at the homepage. A theme update that stripped headings out of the template. Six perfect pages sitting behind a bad robots rule are still six invisible pages.
Spilt Media has worked with Treasure Coast businesses since 2015, and our scoping habit exists because of that gap. Before a crawler runs, we name the pages that are supposed to produce a call. Crawl findings then get sorted by whether they touch one of those pages. Everything else goes on a list we come back to.
That only works because the finding and the fix live in the same building. Search work, site builds, and content sit under one roof here, so “this page doesn’t answer the question” becomes a rewritten page instead of a ticket handed to a stranger. In Stuart and Fort Pierce that’s usually the difference between an audit and an improvement.
The full crawl still happens. It belongs in the ongoing monthly scope, alongside the work that changes pages rather than in place of it. Once a year on a stable site, and immediately after anything structural.
Frequently Asked Questions
How many pages belong on the audit list?
Usually four to eight. Your top service pages, the location page if you run one, the contact page, and whichever blog post pulls the most search traffic. If the list runs past ten, you’ve drifted back into auditing the whole site.
Do you need Search Console access to do this?
Not for the page-reading part. You do need it to see which queries a page already shows up for, and that context changes what you’d rewrite. Set it up before the audit rather than after.
Is a checklist still worth having if you hire someone?
An SEO audit checklist is useful as a scope document. It tells you what you’re paying for and gives you something to hold the deliverable against. Ask which items were run and which were skipped on purpose.
What Should You Audit This Week?
Pick the one page you’d send a serious prospect to right now. Read it as a stranger. Check whether it answers the question they’d arrive with, whether the next step is obvious, and whether the phone number works on a phone. That page is your audit.
If you’d rather someone else read them and come back with a short list of what to change, that’s the work. Start with an SEO plan scoped to the pages that bring you work.