Three pages is a sample, not an inventory
A homepage check is useful. A three-page crawl is still a sample. Neither is a font inventory.
The welcome scan on FontScanner covers up to three pages. That is enough to see whether the site has a font problem. It is not enough to prove it does not. The font that gets you a demand letter is often not on /. It is on /checkout, /blog/some-post, /lp/summer-sale, or a template the homepage never loads.
Foundries do not sample three URLs and stop. Their crawlers walk the public site the way a search engine does. If a commercial .woff2 is reachable, it is evidence. “We scanned the homepage” is not a defense. Background: legal risks of unlicensed fonts and the legal process.
This is informational, not legal advice.
Why inner pages load different fonts
A site is not one CSS file. It is a stack of templates, CMSs, tag managers, and leftover campaigns.
| Surface | Why it often differs from the homepage |
|---|---|
| Checkout / account | A payment plugin, Shopify checkout, or app shell with its own type kit |
| Blog / help center | A CMS theme, Gutenberg block, or Intercom/Help Scout embed |
| Campaign landing | A Unbounce / HubSpot / “just this quarter” page with a display face |
| Careers / legal | A third-party ATS or a PDF-style template with a serif the brand book never named |
| Locale / market | A regional microsite that swapped the body face for “local readability” |
| 404 / maintenance | The one template nobody redesigned — still shipping the old commercial family |
The homepage can be Inter and system UI. The pricing page can still @font-face Gotham. A three-page pass that happens to hit Home, About, and Contact will never see it.
WordPress makes this worse: the theme’s style.css is not the only kit. A page builder, a slider plugin, or a “premium” block can pull in a second family. See WordPress theme font licensing risks.
What a 3-page scan actually tells you
| 3-page / welcome scan | Full-site crawl | |
|---|---|---|
| What you learn | Whether some pages look clean | Which families the live site actually serves |
| What you miss | Every template you did not hit | Very little the public web can see |
| Commercial flags | Only on those three URLs | Site-wide, with page-level evidence |
| License match | Partial picture | The inventory you can hand to legal |
| Use it for | A first look, a demo, a homepage sniff | Launch QA, due diligence, a foundry letter |
A quick homepage check is even narrower — one URL, no account. Useful to decide. Useless as proof.
If those three pages already flag Helvetica, Proxima Nova, or Avenir, you already have a reason to crawl the rest. If they look clean, you still do not know the checkout template. How to read a report: how to audit fonts on a website.
The legal problem is the page you did not open
Copyright attaches to the font software you serve, not to the URL you remembered to check. Serving a commercial family through @font-face without a web grant is infringement on that page, even if the homepage is OFL.
Typical failure:
- Marketing licensed desktop seats for mockups.
- Engineering self-hosted the files “for the new landing.”
- The landing was unpublished. The
/fontsfolder was not. - A later campaign reused the folder. The homepage CSS never mentioned the family.
- A rights-holder crawl hit the campaign URL. The letter named the domain.
You cannot show a three-page report and say the rest of the site was out of scope. The foundry’s exhibit is the live CSS. First 48 hours if a letter arrives: font cease-and-desist.
Agencies inherit this. A client site with ten landing templates is ten chances to miss a kit. Agency audit guide.
What “every page” means in practice
You do not need a human to click 800 URLs. You need a crawler that follows the sitemap and the links a browser would follow.
- Scan production, not only staging.
- Include subdomains you actually serve (
shop.,app.,jobs.) — a license forbrand.comoften does not cover them. - Re-check after a redesign, a CMS migration, or an agency handoff.
- Pair the crawl with a license inventory so each commercial hit is Verified or Missing — how matching works.
A launch checklist that only ticks “fonts look fine on Home” is incomplete. Use the website launch font checklist, then crawl.
Scanning every page once is still a snapshot. The next deploy can add a family you never chose. That is the other half of this problem: why regular scans matter.
Conclusion
Three pages can be Inter. The fourth can be Gotham. Foundries will find the fourth.
A sample is for curiosity. A full-site crawl is for the record you may have to show later — or for the quiet week you still have to buy a license or swap the file.