The method in the open
The similarity part of the score is simple enough to check by hand: lowercase the text, remove the town and service names, split it into words, take every run of five words, and divide the runs two pages share by all the different runs across both (Jaccard similarity). The free duplicate content checker runs exactly this in your browser, so you can see the number the plugin would see. We used the same method to measure how alike real UK location pages are in our location page similarity study.
The quality score
Every generated page carries a score out of 100, computed before publishing — not after. The maths is deliberately simple enough to explain to a sceptical client in one sentence per part.
Short answer
Every generated page is scored out of 100 before it is published: 45 points for how distinct it is from its most similar sibling, measured on five-word shingles; 35 for local substance such as filled local content slots; and 20 for a thin-content floor of original words, one H1 and a meta description.
45 points — sibling similarity
The score’s largest part measures how much a page reads like the other pages generated from the same blueprint — the doorway-page signature search engines penalise. The page’s visible text is broken into five-word shingles and compared against each sibling using Jaccard overlap, with your merge-token values stripped first so swapping “Rye” for “Lewes” earns nothing. The worst sibling drives the result: below 55% similarity the page keeps all 45 points, above 85% it keeps none, with a straight line between. The Quality screen names the closest sibling and its percentage, so “89% similar to Boiler Installation in Lewes” is a finding, not a feeling.
35 points — local substance
- 20 points for filled local content slots, pro-rated against a forty-word target per slot.
- 10 points for a written area descriptor of at least fifty words — editable inline from the Quality screen.
- 5 points for something genuinely of the place: a unique image, an embedded map, or an answered area-specific FAQ (a details block with the question as its summary). In a blueprint built as one custom HTML template these go in as shortcodes, and they count the same way: Pro’s
[townsmith_map], and[townsmith_service_faqs]once the service has FAQs.
20 points — the thin-content floor
Ten points for enough original, non-template words to be worth indexing; five for exactly one H1; five for a meta description — through your SEO plugin if one is active, through Townsmith’s own field if not.
The gate
The publishing threshold defaults to 60 and is adjustable in Settings. On the free plugin the gate is advisory: publishing a below-threshold page shows a clear warning and a fix list, but the decision stays yours. Pro adds the enforced mode, which keeps below-threshold pages as drafts until they earn their way out — useful when several people publish. The pre-publish panel re-checks the live content the moment the publish flow opens, lists what to fix, and jumps to the offending block. Scores recompute in the background on every save, never inline, so editing stays fast; the Quality screen shows each page’s trend since its last check.
Raising scores page by page (Pro)
Most of what lifts a generated page is not in its template: its own local text in the Local Content Slot, its area’s description, and a meta description. Pro’s Local content screen (Local Pages > Local content) lists every generated page lowest score first and edits those three in place, one page after another with Save and next. Saving re-scores the page straight away, along with the pages it was closest to.
Each page shows how its score splits across the three parts, which page it is closest to, and roughly how many more words of its own would start earning the similarity points. The Local Content Assistant drafts from notes you type about the area and never adds facts of its own. Wording a page shares with its siblings is listed but not edited there: it comes from the blueprint, so change it there once and every page changes when you sync.
Next: Updating pages when the blueprint changes — without ever touching your edits.