What we look for
These meta descriptions (the summary search engines may show under the title) are wider than 985 pixels in Raptor's estimate of how Google draws them. Only pages search engines may list are counted.
Why it matters
Search results cut off a summary that is too wide for its space, so the end of it may not be seen.
How to fix
Shorten each description in the CMS or page template and put the most useful words first.
What it cannot know
Width is Raptor's estimate in the font Google uses on desktop. The real cut-off varies with the device and the letters used.
Where you’ll see it
The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.
- Terminal
- When it is one of the five findings under Fix first,
raptor crawlprints the id under it.Check: meta_
description. over_ 985_ pixels - crawl.json and the CSV
- The crawl JSON names the finding by this id, and so do the CSV and
raptor_query."check_
id": "meta_ description. over_ 985_ pixels" - The HTML report
- This link opens the finding in the report, and each finding shows its id.
crawl.
html# finding= meta_ description. over_ 985_ pixels - MCP
raptor_findingswith thischeck_idreturns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.raptor_
findings { "job_ id": ". . . ", "check_ id": "meta_ description. over_ 985_ pixels" }