Measured 2026-08-01 against the two standards you set: 65 to 75 characters per line, and body type at least 20px.

The headline

Eleven of those fourteen are Verity Agentic article pages, changed an hour before this ran. The other three are hub pages. Every other page on every other site fails at least one rule, and most fail both.

34 pages run over 90 characters a line. That is roughly a third past the readable maximum. 34 pages set body text under 16px.

Three properties could not be measured (33 pages): the CRM app screen, a gated audit page, and the menopause practice site, which had no prose the script could sample.

By site, worst first

Two encouraging rows. MedSpasBoulder gets line length right on 41 of 49 pages, and testosteroneinwomen on 11 of 13. Both fail only on size, which is the easier of the two to fix.

The ten worst pages for line length

Every SEO Believer location page sits in this band, and they are entry points from search. At 137 characters the eye loses the start of the next line on the return sweep, which is the specific thing an over-long measure breaks.

There is an awkward angle worth naming: SEO Believer sells search and content expertise, and its own location pages are the least readable thing you own.

The smallest type, one page per site

What is causing it

Two independent faults. Most sites have both.

No reading-width cap on the prose container. A paragraph inside a 900 to 1,100px container fills it. That is why the worst offenders are content pages on wide layouts. Capping the prose column is close to a one-line change per template.

A base font size of 16 or 17px. Reasonable a decade ago on smaller screens. On a current display it reads small, and it compounds the first fault, because small type in a wide container is exactly how a page reaches 137 characters a line.

One trap worth naming, because it already cost time on verityagentic.ai: the CSS ch unit will not solve this. One ch is the width of the digit zero in the current font, so a 65ch cap means something different in a condensed face than a normal one. An about page capped at 64ch rendered as 467px, far narrower than intended, because that site uses Arial Narrow. Set the cap in pixels, then verify the rendered character count.

The order I would fix them in

1. Pages where someone decides whether to hire you. Verity Agentic pricing at 112 characters and 16px is the sharpest example, because it carries the decision. The SEO Believer about and location pages come next, since that is where search traffic lands.

2. Sites whose entire job is reading at length. Cure Canine Disease at 104, Boulder Things To Do guides at 117, Taste Boulder at 14.4px.

3. The two near-misses. MedSpasBoulder and testosteroneinwomen already have line length right almost everywhere. Bumping the base size alone moves them close to fully compliant, which is a large win for a small change.

4. Everything else, template by template. These 19 sites share a handful of layouts, so the real work is far smaller than 321 pages implies.

I would not change 19 sites in one pass. Each needs its rendered result re-checked afterward, since neither number can be read off a stylesheet.

Re-running it

py -3.13 C:\Users\annet\ClaudeProjects\MyExecAssistant\scripts\audit_typography.py

Add --site SEOBeliever for one site, --limit 3 for a quick pass, or --json out.json for per-page detail. It takes its target list from each project's validator config, so anything the validator already covers is covered here.

How it measures. For every substantial paragraph: lines are the rendered height divided by the line height, and characters per line is the text length divided by lines. The median is taken across all paragraphs on a page, so one pull quote cannot skew the result. Headless Chromium at 1440px wide. It has to be measured on the rendered page, because glyph widths differ per font and neither figure is readable from the CSS.