How to Write Meta Descriptions AI Engines Actually Use
Key takeaway
A meta description that AI engines will use is a self-contained, 140-155 character sentence that states the page's core claim in plain language, without marketing adjectives, and matches the phrasing a user would actually type as a question. Write it as the answer, not as an advertisement for the answer. If it can't stand alone as a correct, complete sentence outside the context of your page, most engines will discard it and generate their own summary instead.
Key takeaways
- Keep it to one factual sentence (140-155 characters) that could be lifted and quoted with no edits.
- Skip adjectives like "best," "leading," or "powerful" — extraction models tend to strip subjective language before quoting.
- Match the phrasing of the actual question a user asks, not your internal product vocabulary.
What a meta description actually does for an AI engine
Most people assume the meta description is what ChatGPT or Perplexity reads and repeats. That's only sometimes true. Google's own documentation on creating good snippets is explicit that the meta description is a candidate for the snippet, not a guarantee — Google's systems frequently generate their own summary from body text if they judge it more relevant to the query. AI answer engines behave the same way, but the stakes are higher: if your meta description is vague, the engine's fallback isn't a slightly different snippet, it's a paraphrase pulled from wherever your body copy happens to be clearest — which might be a caveat, a pricing footnote, or a competitor's name in your comparison table.
The practical implication: your meta description isn't decoration for search results, it's a hint to the extraction model about which sentence on your page is the canonical answer. Write it to match a sentence that also appears, near-verbatim, in your first paragraph. Redundancy here isn't wasteful — it's how you make the same claim show up regardless of which source (meta tag, body text, or open graph tag) the engine chooses to extract from.
The mechanics: how these engines actually pull your text
Different engines pull from different places, and knowing which matters more than memorizing a character count.
- Google AI Overviews primarily re-rank and summarize from indexed body content, using meta descriptions mainly as a CTR signal for the traditional listing beneath the overview.
- Perplexity and Bing Copilot rely on live or cached crawls and tend to favor the first substantive paragraph plus any structured data (
og:description,schema.orgdescription fields) over the HTML meta tag alone. - ChatGPT with browsing weights whatever text renders highest on the page after JavaScript execution — so a meta description sitting in a
<head>that never gets parsed because your CMS injects it client-side is functionally invisible to it.
That last point is the one founders miss most often. We've seen SaaS marketing sites where the meta tag is populated correctly in the CMS but rendered only after a client-side React hydration step — a crawler with a short JavaScript timeout never sees it. If you're not sure, view your page's raw HTML response (not the rendered DOM) and confirm the description tag is present before any script runs.
The structure that actually gets quoted
Engines quote sentences that are self-contained, meaning they don't rely on "it," "this," or "here" to make sense. Compare:
- Weak: "Learn how our platform helps you grow faster with powerful AI tools."
- Strong: "Seolyn generates SEO-optimized blog drafts from a product's changelog and publishes them automatically to a CMS."
The second version survives being lifted out of context because it names the subject, the mechanism, and the output. That's the same pattern used in structuring pillar pages for AI search engines — lead with the entity and the concrete claim, not the framing.
A reliable template:
[Subject] does [specific action] by [mechanism], resulting in [outcome].
This forces you to include a verifiable claim instead of a vague benefit. "Improves your SEO" is not extractable as a fact; "reduces manual meta-tag writing by generating descriptions from page content at publish time" is.
Common mistakes that make engines rewrite you anyway
Stuffing the keyword unnaturally. If your meta description reads like it was built for a 2015 crawler ("Best AI SEO tool | AI SEO software | AI SEO automation"), extraction models flag it as low-information boilerplate and skip it. Ironically, the more keyword-dense a description is, the less likely it survives as a quote.
Writing to the brand instead of the query. A description like "Discover what makes Acme different" answers nothing a user searched for. AI engines are ranking against a specific query, and a sentence that doesn't restate the query's intent in its own words has nothing to match against semantically.
Letting every page share one description. Templated meta tags ("The best SaaS tool for your business") produce identical embeddings across dozens of URLs, which tanks how confidently an engine can select any single page as the authoritative source. This is the same failure mode we cover in why AI answer engines choose specific product comparisons to cite — undifferentiated pages don't get picked, duplicates cancel each other out.
Overpromising beyond the page content. If the meta description claims something the body text doesn't support with detail, the engine's internal consistency check (comparing summary to source) tends to suppress the page from citation entirely rather than risk quoting an unsupported claim.
A practical, working example
Say you run a changelog-to-blog automation feature. Here's the difference in practice:
- Before: "Automate your content marketing with AI and save hours every week."
- After: "Converts a GitHub changelog into a published blog post draft within minutes, without a writer."
The second version is 88 characters, names the input (GitHub changelog), the mechanism (automated conversion), and the output (a draft, not a finished polished asset — an honest claim). It's also the kind of sentence you'd want appearing identically in your technical documentation or product page copy, because consistency across surfaces is what lets an engine treat the claim as verified rather than a one-off marketing line.
How this differs from writing for a "blue link" search result
Traditional SEO meta descriptions are written to earn a click — urgency, curiosity gaps, and calls to action ("See how," "Find out why") historically boosted CTR in classic SERPs. Those same techniques actively hurt you in GEO. An AI engine isn't trying to entice a click; it's trying to extract a fact it can present with confidence. A curiosity gap has no factual payload to quote, so the model either ignores the tag or, worse, interprets the vagueness as low content quality and downranks the page in its retrieval step.
This split matters most on pages meant to do double duty — like a pricing page — where you're courting a browsing human and a summarizing model simultaneously. If your pricing page description reads "See our flexible plans," neither audience gets what it needs. Structuring those pages so the description states an actual number or tier, the way we outline in optimizing SaaS pricing pages for AI Overviews, tends to perform better for both.
Length: why 155 characters is a floor, not a target
Google truncates snippets around 920 pixels of rendered width, which typically lands between 150 and 160 characters depending on character width — a fact documented in Google's own Search Central guidance. AI engines don't truncate the same way, since they're not rendering a fixed-width UI element — but shorter isn't automatically safer. A 60-character description often lacks the specificity needed to be self-contained. Aim for 140-155 characters as a sweet spot: long enough to include subject, mechanism, and outcome; short enough to avoid the tag getting flagged as filler once it runs past two sentences.
Frequently Asked Questions
Q: Do AI answer engines actually read the HTML meta description tag?
Some do, some don't, and it depends on how the page is rendered. Perplexity and similar crawlers often use it as a fallback signal alongside og:description, while engines relying on rendered DOM content may miss it entirely if it's injected client-side after page load.
Q: What's the ideal length for a meta description AI engines won't truncate or ignore?
Aim for 140-155 characters. That's long enough to state a subject, mechanism, and outcome in one sentence, and short enough to avoid being flagged as filler text by extraction models.
Q: Should I write different meta descriptions for traditional SEO versus GEO?
The underlying discipline is the same — be specific and self-contained — but curiosity-driven, click-bait style descriptions that work in classic search results tend to get ignored or penalized by AI engines looking for a quotable factual claim.
Q: Does the meta description affect whether ChatGPT or Perplexity cites my page?
It's one input among several, not the deciding factor. The bigger drivers are whether your first paragraph makes the same claim in the same words and whether the page is technically renderable to the crawler in the first place.
Q: Can I reuse one meta description template across many pages?
No — identical or near-identical descriptions across pages produce similar embeddings, which makes it harder for an engine to pick any single page as the definitive source, since none of them look distinct enough to prefer.
Want content like this on autopilot?
Seolyn researches keywords, writes the articles, and publishes on a schedule — 3 days free, no credit card.