The median is undoubtably the more useful number for understanding a typical site in each group, since a handful of very large sites pull the average upward. Even then, we're looking at roughly nine times as many pages for the top-traffic cohort.
That doesn't mean agencies should start recommending one-hundred-page websites to every client.
It does suggest that we should think about SEO beyond optimizing the pages a site already has.
Say a client has a twelve-page site. Those pages might be well designed, technically sound, and optimized around their primary services. But there are only so many distinct search intents twelve pages can reasonably cover.
If the business has more relevant topics, services, questions, locations, or other areas of expertise to address, there's potentially a much larger organic footprint available.
That changes the SEO conversation from "How do we get these pages to rank better?" to "Are we giving the site enough useful things to rank for in the first place?"
Blogs are another clear difference
Blog content shows a similar pattern.
Among the top one hundred sites by organic search sessions, 51 percent had blog posts, compared with 30.6 percent of other published sites.
The difference in volume was even larger. The top one hundred averaged 105 blog posts, while other published sites averaged 3.7.
A blog by itself obviously isn't an SEO strategy. Neither is hitting an arbitrary publishing cadence.
What's more useful is to think about what those additional posts allow a site to do.
Core site pages usually need to stay focused. A service page needs to explain the service. An about page has a particular job. A contact page isn't the place to answer every question a potential customer might type into Google.
Blog content gives agencies more room to address those narrower and more specific searches without overloading the site's core pages.
That might mean answering detailed questions, explaining a process, comparing approaches, covering use cases, or digging into issues that matter to prospective customers but don't warrant a permanent place in the main navigation.
Over time, that creates a broader library of pages that can each compete for their own set of relevant searches.
Dynamic pages can make larger content strategies more practical
The data also shows a smaller difference in dynamic-page usage.
13% of the top 100 sites used Dynamic Pages, compared with 9.2% of other published sites.
It's not as large a gap as we see with overall page count or blog volume, so we shouldn't overstate it. But it makes sense in the context of content scale.
Once an agency identifies an opportunity for dozens or hundreds of similarly structured pages, building each one manually can become the limiting factor.
Think about sites with multiple locations, team members, services, listings, resources, or other repeatable content types. The information on each page may be different, but the underlying structure often doesn't need to be.
Dynamic Pages let agencies separate that structure from the content.
That's useful for SEO because it can make broader coverage operationally realistic. Instead of treating every new page as a miniature web project, an agency can establish the template and content model, then manage the information at scale.
If anything, it strikes us as a missed opportunity that so few of the top ranking sites are leveraging Dynamic Pages, despite building digital tomes. Savvy agencies could easily compete, while expending less effort, by simply structuring their client data ahead of time.
Editor 2.0 is more common among the top 100
There's another difference worth noting: 27 percent of the top one hundred sites were on Editor 2.0, compared with 15 percent of other published sites.
For agencies, there's a broader operational point here. SEO strategies that depend on substantial content footprints also depend on being able to build and manage those sites efficiently.
Content strategy and site production can't really be separated once you're working at scale. A plan for one hundred useful pages isn't especially helpful if producing and maintaining those pages is too cumbersome for the agency or client.
Beyond the ease of use, sites built on Editor 2.0 perform better, often earning higher Core Web Vital scores than those built on Duda’s Classic Editor. With
new AI site generation features launching constantly, combined with this data, there’s never been a better time to pitch a rebuild to your clients.
More pages isn't the strategy
There's an obvious way to misread this data: top-performing sites have more pages, therefore everyone should publish more pages.
That's not the takeaway. Page count is an output, but the underlying strategy is coverage.
If a client has ten meaningful topics to address, turning them into one hundred thin pages isn't going to make the site ten times better. It may make the experience worse.
On the other hand, if a client has hundreds of legitimate topics, questions, services, locations, or other search intents that its audience cares about, trying to squeeze everything into ten pages leaves a lot of potential coverage on the table.
That’s where agencies can bring judgment to the process.
Start with the search opportunity. Map the topics and intents that matter. Decide which deserve dedicated pages. Work out which content types can share a structure and which require something more bespoke. Then determine what the appropriate site footprint looks like.
What this means for agency SEO strategy
For agencies, the most useful part of this analysis may be the way it reframes an SEO conversation with clients.
It's common to inherit a relatively small site and focus immediately on improving what's there: titles, descriptions, headings, internal links, copy, structured data, performance, and other on-page or technical work. And, genuinely, all of that can be worthwhile.
But there's another question to ask earlier in the process: How much of the client's potential search demand does this website actually cover?
A content-gap analysis can reveal opportunities that an optimization-only approach won't. For one client, that could mean developing a deeper resource center around customer questions. For another, it might mean creating dedicated pages for distinct services. Another might have a large set of repeatable content that makes sense to manage dynamically.
The appropriate approach depends on the business. What the data gives us is a reason to take content depth seriously when making that assessment.
Another piece of internal research, since you made it this far; there are 4,801 sites built on Duda sporting monster/cryptid themes. Of those, the cryptids that earn the most traffic are the kraken and
bigfoot. For monsters? The humble witch. Maybe that could fit into your search strategy, too.