How to Write a Meta Description People Actually Click

Anyone publishing a page can write a meta description people actually click in 15 minutes: one promise, one proof, one next step, and a 155-character cap. Run it in ChatGPT, Claude, or Gemini before you recycle the first paragraph and call it a snippet.

A meta description is not a summary. A summary repeats the H1. A description earns a click by naming the job and the next move. If the line could sit under any URL on your site, it is still a brochure.

Search still uses the tag as a fallback snippet. AI Overviews often lift the first clause. Write a sentence a machine can quote and a person can choose.

This loop is a skill, not a character-count ritual. If you are still pasting "write a meta description" into a blank chat, read what a skill prompt actually is and save the card at the end.

A loop for a meta description people actually click

Job first. Proof second. Variants last. Reverse that order and every draft arrives as a vague invite.

1. Steal the query's job, not the page summary

Paste the title and the one-sentence job. Instruct ChatGPT, Claude, or Gemini: "Do not summarize the page. Restate the search job in the user's words. List what a clicker will be able to do after the visit. Stop. Do not draft the description yet."

Hold the model to the job. A description built on "we help teams" is a homepage leftover.

If the page brief is a pile of notes, shape it first like a messy note into a one-page brief. Raw then job then snippet.

2. Force promise, proof, next step

Every description, same bones:

• Promise — the job the title already named, in different words.
• Proof — one fact you can defend. A number, a time cap, a limit, a format.
• Next step — what the page lets them do in the first screen. Not "learn more."

Example: promise the job, prove it with a cap, name the next step.

Tell the model: "One or two sentences. Promise cannot repeat the title verbatim. Proof must be in the input. Next step is a verb the page supports. 120 to 155 characters including spaces."

UNKNOWN is a feature. If the proof is missing, write UNKNOWN and you go find a fact. Do not let the model invent a statistic.

3. Ban brochure words before you generate

Paste this list:

seamless, cutting-edge, comprehensive, unlock, elevate, world-class, one-stop, tailored solutions, learn more, find out how, discover, journey.

Then add your site's three crimes.

Instruct: "If a draft uses a banned word, rewrite the whole description. Do not swap in a synonym. Change the thought."

Synonym swaps are how "comprehensive" becomes "end-to-end" and you still sound like a vendor booth.

The same honesty test that keeps captions from sounding like ads applies here. If you would not say it as an aside to one person, it is still an ad.

4. Generate three, pick one, do not blend

Ask for three variants that share the same proof and the same next step, but change only the promise clause.

Pick one. Do not stitch the punchiest fragments. Blended descriptions have no voice. They have a moodboard.

Refuse a "higher CTR" version with emoji or fake urgency. Cut anything long. Fast is fine. Hype is not.

5. One human pass as a spoken aside

Read the description the way you would mutter it over someone's shoulder at a laptop. Cover the page. If the line cannot stand alone, it fails the SERP and it fails AIO.

Kill:

• A repeat of the title with "and more" glued on.
• A call to action the first screen cannot keep.
• An ellipsis that pretends the CMS will finish the thought.

Fix those in your own words. Send the edit back: "Replace only this description. Do not re-expand."

One pass. Then stop. Save the shape with the Promptcrates tools for reusable website skills so the next page does not inherit last month's brochure.

Reusable skill card

Trigger: The meta field is empty or a pasted first paragraph.

Input: The title, one job sentence, one defensible proof, one next-step verb, plus your banned-word list.

Output: Three descriptions, 120–155 characters, promise / proof / next step, title not repeated verbatim, zero banned words, UNKNOWN if proof is missing.

Stop: After you pick one and read it as a spoken aside. No blending. No emoji. No second "punchier" pass.

Takeaways

• A meta description earns a click. It does not recap the H1.
• Promise, proof, next step. One job noun, once.
• Cap 155 characters. Put the promise first so a rewrite still quotes it.
• Ban brochure words before you generate.
• Save the loop. The last snippet is disposable.