Page count is how many crawlable URLs Crawlinx reached from the homepage within the crawl budget, following internal links only. It is a rough proxy for site size and internal-link reach: a thin count often means orphaned pages, a robots wall, or a JavaScript-rendered navigation the crawler could not follow.
Across 630 Next.js sites the median page count is 19, with the middle half falling between 10 (25th percentile) and 50 (75th percentile). The full range runs from 5 to 60.
Because these sites share the Next.js platform, they inherit the same defaults — its templating, URL structure, sitemap and meta handling — which is why they cluster. The remaining variance is down to theme, plugins and how each team configured them, so the most common issues below are the ones Next.js does not solve out of the box and every Next.js site owner should verify.
The single most common problem here is “Missing recommended security headers”, present on 89% of the sample, followed by “Low text-to-HTML ratio” and “Thin content (low word count)”. The full ranking is in the table above — fix the top of that list first, since it is the fault most likely to be dragging this segment's median down.