Section Length Distribution

Section Length Distribution checks whether your H2 sections average 120-180 words, the range AI answer engines tend to cite. friendly4AI splits the main content at each H2 boundary (anything before the first H2 counts as an implicit section), counts the words per section, and scores the arithmetic mean. You get 100 when that average sits inside the 120-180 word band, and the score falls off as the average drifts away.

What does this parameter measure?

It measures the average word count across your H2 sections. friendly4AI cuts the main content region at each H2 heading, counts words in each resulting section, and takes the mean. The best score lands when that average falls in the 120-180 word window. That's wide enough to carry a real answer and tight enough to keep one subtopic in focus.

Why does section length matter for AI-readiness?

Answer engines pull and cite at the section level. They map an H2 heading to the passage underneath it, then decide whether that passage is worth quoting. Sections that are too short look thin and give a model nothing to lift. Sections that sprawl across hundreds of words bury the core answer, and the model has to guess which sentence actually answers the question. Keep each section near 120-180 words and you hand ChatGPT, Gemini, and Perplexity a clean, self-contained unit. That raises your odds of being cited in answer-style results.

How does friendly4AI score it?

Under the v4.5 methodology, this Content Structure parameter scores on a gradient driven by the average section length:

• Pass (100): averageWords falls inside the inclusive [120, 180] range.
• Partial: the average drifts moderately outside the band. The processor measures the deviation (120 - avg when too short, or avg - 180 when too long) and subtracts round(20 * deviation / 50), clamped to 0-100. The penalty bites, but it won't zero the score on its own.
• Fail (0): the average sits far outside the range, or the page has fewer than two sections. A single block earns an automatic 0, since you can't assess distribution across one section.

So the bands track the processor's proportional penalty, not fixed cutoffs.

How do I fix section length issues?

• Target roughly 120-180 words of substantive content for each H2 section.
• Break sprawling sections that run well past 180 words into smaller, focused sub-sections, each with its own H2. That also helps your heading hierarchy.
• Build out thin sections under 120 words with concrete examples, data, or evidence. Don't pad them with filler.
• Give the page at least two real H2 sections, otherwise there's no distribution to measure.
• Re-scan and read the averageWords and sectionCount evidence fields to confirm the average moved into range.

Related parameters

• Paragraph Length Distribution
• Heading Hierarchy
• Internal Link Coverage