Free Meta Description Generator (Prompt-Based)

TL;DR: This is a prompt, not a hosted tool. Paste it into ChatGPT, Claude, or Gemini along with your page's content, and it returns a meta description sized against Google Search Central's own snippet guidance, with a manual character count you check before you publish. No fixed length limit exists in Google's documentation; the prompt below targets a safe range instead of a myth.

The meta description prompt

Fill in the three placeholder fields with your page's real content and target query, then run it.

Write a meta description for a web page with the following details:

Page title: {{page title}}
Page topic / main content: {{2-3 sentence summary of what the page actually covers}}
Target search query: {{the query you want this page to rank for}}

Requirements:
1. One to two sentences, written as a genuine pitch for what the reader gets on this page —
   not a restatement of the title.
2. Include the target search query, or a close natural variant of it, without stuffing it
   at the very start of the sentence.
3. Stay between 120 and 155 characters, counted including spaces. Show me the exact
   character count of your final answer.
4. Do not repeat this same description's structure verbatim across other pages I ask you
   to write for — vary the sentence pattern for each page you draft, even if the two pages
   cover similar topics.
5. Do not use vague filler openers like "Learn about" or "Discover our" — start with the
   specific benefit or fact the page delivers.

Write 3 variants and label them A, B, and C, each with its character count shown.

That fifth requirement matters more than it looks. Templates that always open the same way ("Learn about X," "Discover the best Y") are exactly the pattern Google's guidance singles out as unhelpful when it repeats across many pages of one site.

What Google actually says about meta descriptions (and what's a myth)

The "155-character limit" repeated across most SEO blog posts is not a number Google Search Central publishes. Google's own guidance on controlling search snippets states there is no fixed length limit on a meta description tag. The visible snippet gets truncated as needed to fit the search result, which in practice usually lands somewhere in the 120-160 character range on desktop and can differ on mobile. That's a rendering consequence of screen width, not a documented rule with a hard cutoff. Source: Google Search Central, "Control your snippets in search results," accessed 16 September 2026.

Read that carefully and it says something specific: the snippet is truncated "as needed," not truncated "at 155 characters." A description of 200 characters isn't rejected or penalized. It's just cut off wherever the display runs out of room, on whatever device is rendering it. Writing to a 120-155 character target is still the right practical move, because it means your actual message survives the cut instead of getting chopped mid-sentence. It's a display strategy, not compliance with a published rule.

Two other things from that same guidance are worth building into your prompt rather than learning the hard way:

• Google doesn't always use what you write. The same page states Google sometimes uses the meta description element when it would give a more accurate description than content pulled directly from the page. Meaning sometimes it doesn't, and picks a different snippet instead. A strong meta description raises the odds of being shown; it isn't a guarantee.
• Identical descriptions across pages actively hurt. Google's guidance calls out identical or near-identical descriptions on every page of a site as unhelpful once multiple pages from that site appear together in results. This is the actual argument for requirement 4 in the prompt above: a template that only swaps the noun is a version of the same failure.

None of this makes meta descriptions a ranking factor. Google does not use them that way. What they influence is click-through from an already-earned ranking, by giving a searcher a reason to pick your result over the one above or below it.

A worked example

Say you're writing a meta description for a page selling a project-management tool's free tier. Filling in the prompt above:

Page title: Free Project Management Software for Small Teams
Page topic / main content: A free-forever plan of our project management tool, covering
task boards, up to 3 projects, and 2GB storage, aimed at teams under 10 people.
Target search query: free project management software

A weak, template-shaped output would read: "Learn about our free project management software. Discover powerful features for your team today." That fails on three of the five requirements at once: it opens with "Learn about," it makes no specific claim, and it would be nearly identical to a description written for any other software page on the same site.

A description that follows all five requirements looks more like: "Free project management for teams under 10: task boards, 3 projects, 2GB storage, no credit card required." That's a specific pitch, includes the query naturally, and would need its exact facts changed (not just its noun) to reuse on a different page. That's the difference the prompt's fifth requirement is actually enforcing.

Why this matters beyond Google's own results page

A meta description doesn't only feed Google's search results. The same tag is frequently what a link preview card pulls when a page is shared on Slack, LinkedIn, or in a chat app, and it's one of the first things an AI answer engine reads when deciding how to summarize a page it's citing. A vague, templated description undersells the page in all three places at once, not just in a search result a human might skim past.

Variants for common page types

The base prompt works for any page, but these small additions handle the pages where a generic pitch reads flat.

Blog post: Add "Frame this as what the reader will be able to do or understand after reading, not a summary of the outline."

Product or pricing page: Add "Include one concrete detail, such as a price, a specific feature, or a number, rather than a general claim like 'the best solution.'"

Category or listing page: Add "Mention roughly how many items or options are on this page, since that's often the deciding factor for a searcher comparing category pages."

Local business page: Add "Include the city or service area by name, since local intent queries often include it and Google bolds matching terms in the snippet."

Quick reference: what to add per page type

What to do when Google isn't using your description

If you've written a strong description and Google is still showing a snippet pulled from the page body instead, that's not necessarily a sign the description was weak. Google's own guidance is explicit that it makes this choice per query, based on which text it judges gives that specific searcher a more accurate answer. A description written for a broad, generic version of the page's topic can lose out to an on-page sentence that happens to match a narrower search more precisely.

Two things are worth checking before assuming the description itself is the problem. First, whether the description accurately reflects the page's actual content, not an aspirational version of it; a mismatch between the promise and the page is exactly the kind of thing that would push Google toward pulling text from the body instead. Second, whether the page has enough clear, well-structured content on the topic for Google to have a body sentence worth pulling in the first place. A thin page gives Google little choice but to lean on whatever text exists, description or not.

There's no fix that guarantees your written description gets used every time, for every query that lands on the page. Writing a strong one, sized correctly and specific to the page's actual content, is what raises the odds. It isn't a lever you can pull all the way to certain.

Variants for comparison and "versus" pages

Comparison pages (X vs Y) have their own failure pattern worth naming separately: a description that just repeats both product names without saying anything about the comparison itself. Add this to the base prompt for that page type: "Include the specific dimension this comparison focuses on, such as price, features, or ease of use, rather than just naming both products being compared." A description reading "Compare Tool A and Tool B" tells a searcher nothing they didn't already know from the title; one reading "Tool A vs Tool B on pricing, storage limits, and free-tier caps" gives them a reason to click through for the specifics.

Writing descriptions at scale without them starting to sound the same

If you're running this prompt across dozens of pages in one sitting, the fifth requirement (varying sentence structure) gets harder to hold onto by page thirty than page three. A useful check: after a batch, paste the full set of descriptions back into a fresh prompt and ask "Do any of these open with the same first three words, or follow an identical sentence pattern? List the ones that do." That catches drift a single-page review won't, because you only notice a repeated pattern once you can see several descriptions side by side.

Three mistakes worth checking for before you publish

Writing the description before the page is finished. A description drafted from an early outline often describes what the page was supposed to say rather than what it ends up saying. Run the prompt again after the final draft, not the first one.

Copying the H1 into the description with minor wording changes. The title tag and the meta description do different jobs in a search result. The title identifies the page; the description sells the click. A description that just rephrases the title wastes the one line Google gives you to make a case for clicking your result over a competitor's.

Forgetting the description still needs to make sense truncated. Since Google can cut it anywhere depending on device width, front-load the actual value in the first 100 characters or so rather than saving the specific detail for the end of a longer sentence.

Turning this into a repeatable task

If you're writing more than a handful of these, the actual bottleneck isn't the prompt. It's rewriting the same instruction from scratch every time you have a new page. Save the prompt above with {{page title}}, {{page topic}}, and {{target query}} as reusable variables, and drafting one becomes filling in three fields instead of reconstructing five requirements from memory.

Prompt Architects stores prompts exactly this way, with named variables you fill in per use, so the meta description prompt, the ad copy prompt from our free ad copy prompt generator, and any other recurring SEO task live in one searchable library instead of scattered across old chat threads. The Free plan covers 5 prompt enhancements a day, which is enough for occasional use; Pro removes the daily cap for anyone doing this across a full site.

The honest limits of an AI-written meta description

A model can size a description correctly, avoid the repeated-template problem, and write a natural sentence that includes your target query. It cannot guarantee Google displays it instead of a snippet pulled from the page body. That choice happens at query time and isn't something any tool, prompt-based or hosted, controls. Write the best possible candidate, publish it, and let Google's own ranking system decide when to show it.