Browse sections
What does this check look at?
The raw server response contains at least 100 words of visible text without executing JavaScript.
The hundred words are counted across the entire response, so navigation, the footer and cookie text are part of the total. A page whose article is assembled by JavaScript can clear the threshold on its chrome alone: the check proves the response is not empty, not that the article is in it.
How do I fix it?
- Crawlers do not execute JavaScript. Server-render the content you want cited.
Why is it worth 2 points?
Points are relative weights inside a dimension, and a dimension's weight decides how much of the total it can move. The reasoning for this dimension's weight is published rather than asserted:
| Dimension | Semantic Structure — 8% of the total score |
| Points for this check | 2 of 8 in this dimension |
| Worth at most | 2.0 of the 100 points |
Moderate. Mostly a one-time fix.
Which dimension does this belong to?
Semantic Structure — 8% of the total score, decided by 3 published rules.
Heading hierarchy and landmark elements are how a parser locates section boundaries at all.
None of the five guides covers this rule, which is why this page shows the fix in full rather than pointing at one.
What else is measured in this dimension?
- Exactly one H1 — 3 points
- Semantic landmarks are used — 3 points
How do I see my own result?
Run a scan on your own domain. The report lists every failed check with the evidence that produced it, so you can tell a real failure from a check that does not apply.
Run a free GEO audit on your own site →
The full method, including the dimensions that are deliberately weighted low and the parts of a picture a single-URL scan cannot see, is on the methodology page.
Questions about this rule
What does this check look at?
The raw server response contains at least 100 words of visible text without executing JavaScript.
Why does this dimension carry 8% of the score?
Mostly a one-time fix.
Evidence and sources
GEO can boost visibility by up to 40% overall in generative engine responses, and in the paper's Table 1 the best of the tested methods improve on the no-optimization baseline by 41% and 28%. — Generative Engine Optimization, KDD 2024
This rule is applied by the scanner and published in the rule set it is read from, so the condition on this page is the condition the scan tests rather than a summary of it.
Primary sources
- Generative Engine Optimization (KDD 2024) — the measured gains the citability weight follows
- What Generative Search Engines Like — what generative engines prefer in retrieved content
- What Gets Cited: Competitive GEO — which of two competing sources is cited first
- The rule set and its weights — every check, its weight and its pass condition