Methodology
Cited samples up to 5 pages from your site and checks the meta description on each against two criteria: presence and length. Presence. Every sampled page either has a<meta name="description" content="…"> tag with non-empty content, or it doesn’t. Pages without descriptions force AI models to extract a summary from page text — slower, less reliable, and often wrong for landing pages or thin content where the first paragraph isn’t summary-shaped.
Length quality. A description between 80 and 160 characters scores as “quality.” This range matches the calibration used by AI summarizers and search engine snippet generators: too short and the description doesn’t carry enough information for AI to differentiate the page from siblings; too long and the description gets truncated, often mid-sentence, losing the most informative trailing content.
The score is based on the quality rate across sampled pages — the percentage of pages with descriptions in the 80-160 character band:
- 80% or more pages have quality descriptions → 6/6. Full score.
- 50-79% quality → 3/6. Partial — most pages are right, but enough are off to drag the score down.
- Any pages have descriptions, but few hit the quality band → 1/6. Descriptions exist but aren’t optimized.
- No pages have descriptions → 0/6. Critical failure.
Verification
You can verify our finding yourself in a browser. Step 1: Open the pages we sampled. Cited reports the URLs we tested. Open each in a new tab. Step 2: Check the meta description tag. Right-click the page, View Page Source (Cmd+U / Ctrl+U), and search (Cmd+F / Ctrl+F) for name="description". The full tag looks like <meta name="description" content="…">. The content attribute value is what the scanner extracts.
Step 3: Count the description length. Copy the content attribute value (without the surrounding quotes) into any character counter — for example, paste it into the DevTools Console with ('…').length substituting your description. The 80-160 character band scores as quality.
Step 4: Spot-check the description content. Length is necessary but not sufficient. A 100-character description that just repeats the page title doesn’t help AI understand the page. Read each description and ask: would this description tell an AI model what’s unique about this page versus a generic competitor page? If not, the description is technically passing this signal but not pulling its weight in AI citation.
If your verification disagrees with Cited’s finding, that’s a bug — let us know.
Technical detail
The meta description tag is governed by the HTML Living Standard and has been a stable convention since HTML 4 (1997). Search engines have always used it; AI models inherited the same parsing path because the data is already in their training corpora and refresh cycles. Extraction logic. Cited’s scanner uses regex against the raw HTML (not DOM parsing) for this signal:- Primary pattern:
<meta name="description" content="…">with thenameattribute beforecontent - Reversed pattern:
<meta content="…" name="description">withcontentbeforename - Both patterns are case-insensitive and tolerate arbitrary additional attributes (e.g.,
id,lang) - The content attribute value is extracted between matched quotes (single or double)
- Multiple meta description tags on one page. The regex finds the first match in document order. If a page has two
<meta name="description">tags (which is invalid HTML but happens — usually one in<head>and one duplicated by a plugin), the first one wins. - Whitespace-only content attributes — a description like
content=" "is detected as present but the trimmed length is 0, so it fails the quality check. - Open Graph descriptions —
<meta property="og:description">tags don’t satisfy this signal even though they serve a similar purpose. OG descriptions are scored separately under the Open Graph Tags signal. - Server-rendered vs client-rendered descriptions — some single-page applications inject the meta description via JavaScript after page load. The scanner reads the post-hydration HTML (after Puppeteer’s 3-second delay), so JS-injected descriptions are detected.
- Encoded HTML entities — descriptions containing entities like
&or'count by character length including the entity, not the decoded form. A description with three&substitutions reads as 18 entity characters where a user would see 3 ampersands.
- Description content quality. The scanner counts characters, not meaning. A page-title-repeat description scores the same as a unique value-prop description.
- Description uniqueness across pages. Every page can have the exact same description and score 6/6 if all are in the 80-160 band. Duplicate descriptions are a real signal of editorial neglect but aren’t modeled here.
- Keyword presence. No keyword matching against page topics or brand terms.
- Brand name inclusion. Some style guides require the brand name in every description (e.g., ”…— BrandName” suffix). The signal doesn’t check.