What this check tests
For every page the audit crawled (the homepage plus up to nine more), the check takes the page's visible body text, with scripts, styles, noscript and template content removed and whitespace collapsed, and keeps the first 500 characters. A page is good when both hold:
- Those 500 characters contain at least 20 words, split on whitespace.
- The page has a
<meta name="description">whosecontentis not empty.
The score is the share of good pages, rounded. 70 or more is a pass, 1 to 69 is partial, 0 is a fail. A crawl with no pages scores 0.
The name promises more than the code delivers. It does not look for a question, a direct statement, a heading or a summary. It does not skip navigation: menu links, a cookie banner or a header tagline at the top of the body count as words, so a page that opens with 20 words of menu passes. What it really detects is a page that has text near the top of the HTML and a description tag, and conversely a page whose first 500 characters are mostly empty or script-driven.
Why it matters to agents
No source fetched for this page says that AI assistants prefer content that leads with the answer. Google's guide to generative AI search says you do not need to write in a specific way just for generative AI search, because its systems understand synonyms and meaning. Its helpful-content guidance does ask whether the main heading or page title gives a descriptive, helpful summary of the content, and that is a reasonable human test for an opening.
The meta description part has a clearer basis. Google says snippets are primarily created from page content, and that it sometimes uses the meta description when that describes the page better. So the tag is optional help, not a requirement.
Treat this check as a sanity test that a page has early, readable text and a summary. A fail usually means a page is a JavaScript shell, a gallery, a login wall or a template whose first screen is mostly navigation. A pass does not mean your pages answer questions.
How to fix it
- Open a failing page's source and look at the first 500 characters of text after
<body>. If it is a mega-menu, move the main content earlier in the source, or make the menu shorter; CSS can keep the visual layout. - Start the main content with a plain statement of what the page covers or answers, in a sentence or two. Write it for the reader, not for an assistant.
- Add a meta description of one or two sentences that describes the page:
<meta name="description" content="How to rotate API keys without downtime, with a checklist and example commands.">
- For client-rendered pages, make sure the text is in the HTML the server sends; see no JavaScript dependency.
- If the failing pages are utility pages (carts, logins, search results), a partial score is expected and needs no change.
Related: content length and citation readiness measure other properties of the same text. A matching Article or FAQPage block can be checked with schema.org validity.