Programmatic SEO audit
What this page covers
Programmatic SEO audit
A programmatic SEO audit checks whether a large page set has a clear hub-and-leaf structure, useful templates, and crawl paths that can be measured before more pages are added.
Radar benchmarks page counts, hubs, leaves, depth, and scores for sites such as Lyft.com, Truecar.com, and Cornell.edu, so teams can compare structure instead of judging scale alone.
In brief
- Start with structure. Page count, hubs, leaves, leaf-to-hub ratio, depth, and score show whether a programmatic layer is organized or overloaded.
- Compare patterns carefully. Lyft.com is shown with 10,007 pages and 46 hubs, while Truecar.com is shown with 10,003 pages and 2 hubs.
- Do not treat page volume as value by itself. A safer programmatic SEO plan avoids thin, duplicate, doorway, or low-value pages.
What to do
A useful audit starts with the hub-and-leaf map. Truecar.com is shown with 10,003 pages, 2 hubs, 10,000 leaves, and a 5,000.0 leaf-to-hub ratio. Lyft.com is shown with 10,007 pages, 46 hubs, and 9,960 leaves.
Those numbers frame the main question: does the structure support useful navigation and crawl paths, or do too many leaves depend on too few meaningful hubs? Depth, hub count, leaf count, and score should be reviewed together.
The content layer also needs a quality check. For programmatic SEO, the safer path is to define evidence-backed templates, reduce duplication risk, and avoid creating pages only because a dataset can generate them.
What to keep in mind
This audit is most useful when a team is scaling pages across many locations, segments, or categories and wants a controlled search layer. It is not a shortcut for publishing large page sets without checking whether the pages are useful.
Benchmarks can raise different questions at different site sizes. Cornell.edu is shown with 21 pages, 3 hubs, 17 leaves, a 5.7 leaf-to-hub ratio, depth p90 of 2, and a 27/E score.
Internal linking should follow an approved map, not invented URLs or changed anchor text. If a name is not available in the link source, it should stay as plain text, and repeated anchors should be limited.