The smallest site in my audit folder has 189 pages. It’s a medical education provider.
The largest is a classic car marketplace with 9,220 pages indexed.
The most recent is a chiropractic clinic with a couple of dozen pages, a Google Business Profile and a blog.
Different platforms, different decades, different industries, different money. I went back through all eleven audits expecting the findings to sort themselves by size: technical problems on the big sites, content problems on the small ones, roughly what everyone assumes.
They didn’t sort at all. The same three findings appear at every scale. What changes is the number attached to them, and what the fix costs.
The three that don’t care how big you are
Internal linking. Eleven of eleven. Every audit, every size. On the clinic it was a home page that linked to its services only through the menu. On the marketplace it was 8,317 pages that nothing linked to at all. Same finding, four orders of magnitude apart.
Schema markup. Ten of eleven, missing or incomplete. Absent entirely on a clinic; absent entirely on an ecommerce catalogue turning over real money.
Thin content. Ten of eleven. The clinic had service pages with a paragraph on them. The marketplace had 7,353 pages under 500 words. One is an afternoon of writing. The other is not a writing problem at all. It’s a template producing pages that were never going to have anything to say.
Nothing else came close to those three. Not speed, not links, not the things that get written about.
Why scale doesn’t change the diagnosis
Because these aren’t really content problems or technical problems. They’re all the same problem wearing different clothes: the site doesn’t say what it is.
Internal linking is how a site tells search engines which of its pages matter. Schema is how it states plainly who and what it is. Thin content is what happens when a page exists without having anything to say. A site failing all three has published a lot of material without ever making a claim about itself.
A two-person clinic can fail that and so can a marketplace with nine thousand pages, because the failure is architectural, not proportional. You don’t grow out of it. You grow it.
There is a mundane reason the failures rhyme across sizes, and it is worth saying out loud. HTTP Archive’s 2025 Web Almanac has 54% of the web running on a CMS, WordPress at 64.3% of those, and the distribution barely shifts with scale, with WordPress still around 58% of CMS usage inside the top 10,000 sites. The chiropractor and the marketplace are running the same software, configured by people who learned it the same way, inheriting the same defaults. Most of why the findings repeat is that the sites were built out of the same parts.
What scale actually changes
Three things, and they’re all about method rather than diagnosis.
Whether you can look at everything. On the clinic I opened every page. That took an afternoon and I saw things no crawler reports: copy that describes a mood rather than a service, a testimonial section with no testimonials in it, a header that renders differently on the blog.
On the marketplace that’s impossible, so you work from exports and samples, and you lose the things only a human notices. Big-site audits are more rigorous and less perceptive. That’s a real trade and nobody talks about it.
Whether the fix is editing or engineering. The clinic’s thin service pages get fixed by someone sitting down and writing them. The marketplace’s 7,353 thin pages don’t get fixed by writing. They get fixed by changing what the system generates, or by deciding those pages shouldn’t exist.
This is the difference that actually matters commercially. On a small site the recommendation is work somebody can do. On a large one it’s a change to a system, which means a developer, a test environment and someone with authority to approve it. Plenty of large-site recommendations are correct and never get implemented for exactly this reason. One of mine never did, and I think the client was right.
Whether the numbers mislead you. On a small site every finding is countable and every count is meaningful. On a large site the counts are enormous and mostly describe the same handful of causes. 8,317 orphan pages, 8,317 missing canonicals and 7,353 thin pages on one site were one template, not three problems, but a report lists them as three, and a spreadsheet with 400 rows in it is how a technical audit becomes something nobody implements.
Small sites: read every page. Large sites: find the template.
Which is harder to fix
Large sites are harder to fix and easier to diagnose. Small sites are the reverse.
On a large site the problems are usually systematic, which means they’re visible in any export and hard to change. Ten thousand pages have no canonical because one template doesn’t emit one. You’ll find that in ten minutes and it may take six months to ship.
On a small site the problems are usually specific, which means they’re easy to change and easy to miss. The home page doesn’t mention two of the four services. The About page has one internal link. There’s no map embed. None of that appears in a crawl report as an issue, because none of it is technically wrong. It’s just a site that hasn’t been thought about. Someone has to read it and form a judgement.
That’s why I don’t have a different process for large and small sites. I have the same process, and on the small ones more of the work is reading.
What this means if you’re choosing who to hire
I’ll declare the interest: this is an argument for what I do, so weigh it accordingly.
The industry sorts itself by vertical, into ecommerce specialists, local specialists and SaaS specialists, and there are good reasons for that. Vertical knowledge is real. Somebody who has audited forty Shopify stores knows where the bodies are buried.
But the diagnosis mostly isn’t vertical. Across eleven audits spanning chiropractic clinics, a homeware store, a car marketplace, three continuing-education platforms and an ad agency, the top three findings were identical. What differed was the fix, and the fix is the easier half. Once you know what’s wrong, the remedy is usually not mysterious.
If a site should be ranking and isn’t, the useful question is not “who knows my industry” but “who is going to work out what’s actually wrong before recommending anything.” Those are different skills and only one of them is scarce.
The short version
- Internal linking, schema and thin content appear at every scale. Eleven, ten and ten out of eleven audits.
- They’re one problem: the site never says what it is.
- Small sites: read every page. You’ll see things no crawler reports.
- Large sites: find the template. The big numbers usually describe one cause.
- Small-site fixes are editing. Large-site fixes are engineering. That’s what decides whether they get done.
- Large sites are easier to diagnose and harder to fix. Small sites are the reverse.
- The diagnosis travels across industries. The remedy is the part that needs local knowledge.
If a site should be ranking and it isn’t, that’s the work I do, at whatever size. If you’re not sure which of several plausible problems is the one costing you, that’s what an SEO audit is for, and if I look and there’s nothing worth fixing, I’ll tell you that.
