Pick the audit by asking whether one page is acting up or the whole site might share the problem. A single page audit checks one URL, and a site sample checks a few pages for a repeated pattern. Neither is a full crawl, a browser usability test or a check of every indexed URL. Trojan Digital Marketing’s free website auditor reads public HTML only, so we treat its sample as a starting point. To go over a result with Jeff Clerisier, our founder, the first strategy call is free, and during business hours we aim to reply within five minutes.
The free website auditor supports a bounded sample of up to five pages on the same origin. The exact pages included and the evidence returned belong in the report. Use that sample to identify questions worth investigating, then expand the review deliberately when the business decision requires broader coverage.
Choose the scope around the question
- Fit
- Explain the service scope.
- Trust
- Show supporting evidence.
- Next step
- Give a clear contact route.
We use a single page when the issue is specific: a service description, a tool page or a recently changed landing page. It gives you a focused observation and a clear resource to recheck. A sample becomes useful when you suspect a shared template issue or want to compare several important customer paths.
We don’t widen the scope just to make a report sound bigger. If all five sampled pages use the same template, the result says little about a different template that was never included. The value comes from knowing what the sample represents and what remains outside it.
Understand what each review can establish
| Review type | Useful question | Important limit |
|---|---|---|
| One URL | What evidence is available on this page? | Does not describe other pages |
| Limited same origin sample | Does a pattern repeat in these pages? | Not a complete site inventory |
| Wider crawl with defined coverage | Which discovered URLs share a finding? | Discovery and access limits still apply |
| Rendered interaction review | Can a visitor complete a specific task? | Depends on tested devices and flows |
| Search Console review | What does the property’s search data show? | Separate from a page implementation check |
This comparison describes different methods rather than ranking them by sophistication. A precise single URL check can be more useful than an undefined “full audit” when the question is narrow. We match the method to the evidence you need.
Treat the selected pages as the actual scope
We read the report’s URL list first. A bounded sample may discover pages through available links and return fewer than five eligible responses. Access restrictions, unsupported content or request failures can limit the result. A page that was not inspected should remain outside the findings, even if its URL appears elsewhere on the site.
Same origin is also a technical boundary. A different subdomain or protocol can be a different origin even when it belongs to the same business. Do not describe an excluded property as checked. If the business operates several sites, each needs an explicit review scope.
Interpret repeated findings cautiously
Suppose three sampled service pages share an outdated footer description. That suggests a possible shared component. It does not prove that every page has the same text. We inspect the template or content source before guessing how far a fix reaches.
Suppose one page lacks a heading detected on the others. That may be an intentional design difference, a page specific content issue or content added during rendering. We keep the observation and look for the cause. Google’s JavaScript SEO guidance explains why source and rendered content can differ.
Watch for selection bias in a small sample
Pages easy to discover from the starting URL may not include deep articles, older campaigns or isolated resources. A clean sample therefore cannot establish that those areas are clean. Conversely, starting from an unusual page may overrepresent an old or specialized template.
We keep your known page list next to the report. List the homepage, core service templates, tools, articles and inquiry pages that matter to the review. We mark which types were observed and which weren’t. This is a planning record, not a claim that the free tool crawled the whole inventory.
Keep indexing questions in the right workflow
A successful HTML response does not prove a URL is indexed. A canonical declaration in the page does not prove Google selected it. Google’s URL Inspection documentation explains the separate indexed and live information available for a verified property.
If a business question concerns missing search visibility, combine implementation observations with the appropriate search records. Keep the evidence sources separate in the audit ledger. Do not turn a sample checklist into an unsupported statement that every page is eligible for every search or AI feature.
Decide when the sample justifies deeper work
We widen the review when the sample shows a shared failure, an important unknown or a key customer path outside the scope. Then we define which extra pages or behaviors need checking. A broader review should have a reason and a finish line rather than an unlimited list of optional tests.
The developer handoff guide helps turn a confirmed pattern into a scoped investigation or correction. The website performance playbook covers a separate performance improvement process with implementation evidence and measurement limits.
Explain the result in plain language
A useful summary says how many pages were inspected, what repeated, which important pages were excluded and what happens next. It can say “three of the five inspected pages showed the same outdated field.” It should not say “the entire website has this problem” unless another source establishes that reach.
For a business that needs a wider review, explore SEO, AEO and GEO services with the sample and page inventory. Our newsletter shares more examples of a free tool used as the first step of a fix.
Frequently asked questions
Does five pages mean five successful checks?
The cap describes the maximum sample size, not a promise that every requested page can be inspected. Read the returned URL list and statuses. Unavailable evidence and failed requests should remain visible rather than being counted as successful page reviews.
Can a sample identify every broken link?
No. The result is limited to the implemented checks and pages actually inspected. Links outside that evidence are not covered. A complete link inventory requires a separately defined crawl and verification process, with its own discovery and access limitations.
Is a site sample enough before a migration?
It can reveal useful issues, but it does not replace a migration inventory, URL preservation plan or verification of important customer flows. Use it as one input. Keep original URLs and content identities mapped so the migration can be checked against a concrete baseline.
