Reading time:

11 min read

|

Last updated:

SaaS Meta Description Best Practices That Win Clicks

Meta description best practices: answer the query in the first eight words, not a slogan. Why Google rewrites snippets, templates, and a four-week test.

We design websites and products that make AI companies more money.

Siddarth Ponangi

Founder, Studio Maydit

We design websites and products that make AI companies more money.

Web and product design for AI companies

We help AI companies build fast, clean, and conversion-focused websites and products.

Meta description best practices come down to one rule: answer the searcher's query in the first eight words of both the title and the description. Say what the page is, who it is for and what it measures or makes, in plain nouns, and keep the slogan somewhere else. Length, keyword counts and a closing call to action matter far less than whether the snippet matches what the person just typed.

This matters most on pages that already rank. Getting onto page one is the slow, expensive part. The snippet is the last twenty or thirty words between that work and a visit. You know your product, so you read your own slogan and fill in the rest. A stranger scanning ten blue links cannot do that. He clicks the result that says the thing.

The snippet that opens with Data is the new oil

Picture an AI analytics startup. Its product tracks how people use the LLM features inside other apps: which prompts users retry, which answers get a thumbs down, and what each session costs in tokens. The page sits at position 4 for the query product analytics for ai apps. Over the last four weeks that query earned 1,100 impressions and 6 clicks.

Here is the result a searcher sees. The title link reads Home | The Future of Product Intelligence. The description underneath reads Data is the new oil. We help modern teams turn it into insight. Book a demo today.

The two results above it read differently. At position 2 the title is Product Analytics for LLM Apps: Prompts, Costs, Retention. Its description starts with See which prompts users retry, which answers they rate down, and what each session costs. At position 3 the description opens with Track token spend per user and per feature.

The searcher typed five words. Two results repeat those words back and then name what the tool measures. One result names a commodity from an old conference slide. The product behind the slogan may be the best of the three. The searcher never finds out, because nothing in the snippet told him it was even the same kind of tool.

Position 4, six clicks and a green arrow in the report

The founder checks Search Console on Monday mornings. The page moved from position 7 to position 4 this month, and he posted the screenshot in the team channel. The freelancer who writes the blog sent a report with the same green arrow. Nobody opened the clicks column sitting next to it.

When he finally does, he blames the searchers. Maybe that query is students, he says, or people looking for a free tool. He approves two more blog posts aimed at nearby keywords. The title tag that says Home stays exactly where it is, because nobody on the team remembers writing it.

Reading this properly takes ten minutes. In Search Console, open Performance, turn on Average CTR and Average position, and switch to the Queries tab. Sort by impressions. Then compare each query only with your own queries at a similar position. If most of your position 3 to 5 queries earn a few percent and one earns half a percent, the ranking is not the problem. The snippet is. Six clicks from 1,100 impressions is about half a percent.

Check the shape of the query before you blame the snippet. A long first person question, the kind people ask an assistant, often gets answered before anyone clicks, and no rewrite fixes that. We covered that pattern in why position 1 now gets you zero clicks. A short typed phrase like product analytics for ai apps is the opposite case. Someone typed it because they wanted a list of tools to open in tabs. That click is there to win, and a slogan hands it to the result above you.

What most meta description advice gets wrong

Most guides lead with length. Keep it between 150 and 160 characters, use the keyword once, and end with a call to action like Learn more. None of that is harmful. It is just about the container, and it says nothing about the first words a person reads.

Length barely changes what Google does with your text. An Ahrefs study of 192,656 pages found Google rewrote 62.78 percent of meta descriptions. Overly long ones were rewritten 61.46 percent of the time, and ones at the recommended length 63.69 percent. Counting characters is not the lever. The closing call to action is worse than neutral. Book a demo today spends four words asking for a meeting before the reader knows what you sell.

Here is the claim we would defend. The first eight words of the title and of the description should answer the query in the searcher's own nouns. Not a benefit, not a mood, not your tagline. The category, what the product measures or makes, and who it is for. Everything after word eight is a bonus, and on a phone it may be cut off anyway. A founder who writes a slogan there is not being lazy. He is writing for someone who already knows the product, and that person is not searching.

Why Google rewrites your snippet, and when it keeps yours

Google's documentation says snippets come mainly from the page content, and that it uses the meta description when it gives a more accurate description than the page text would. Titles work the same way. Google may build the title link from the h1, other headings or anchor text when the title element is boilerplate or does not describe the page. A title that starts with Home is exactly that.

Read those two rules together and the rewrite rate stops being a reason to give up on descriptions. A rewrite is a verdict. Google compared your description with the query and your page and picked a sentence it thought matched better. The same Ahrefs study found rewrites were more common for long-tail queries, 65.62 percent, than for head terms, 59.65 percent. The more specific the search, the more a vague description loses.

Two things follow. A description that answers the query plainly has the best chance of being the one shown. And the page itself needs a plain answer near the top, because when Google does rewrite, it quotes your copy. A hero that also says Data is the new oil fails twice, once in the description and again as the fallback. If that is your hero, how to write a SaaS hero section covers the first screen.

Title and description templates for three kinds of page

Every template below starts with the searcher's words and then adds the one detail that separates you from the result above. Put your brand at the end of the title, once, or let the site template add it. Google suggests the site name at the start or end, separated by a delimiter. Never let the title begin with Home.

  • Homepage. Title: category for audience, then what it tracks or makes. Product Analytics for AI Apps: Prompts, Costs, Retention. Description: the three things it measures, then one difference. Track which prompts users retry, which answers they rate down, and what each session costs in tokens. Connects to your LLM calls in one line of code.

  • Feature page. Title: the job the feature does, in the verb a buyer would type. Track Token Cost per User and per Feature. Description: what the person sees on the screen. See what each account costs to serve, split by feature and model, and flag the ones that cost more than they pay.

  • Blog post. Title: the query, then the promise. Description: the first sentence of the answer, then what the post contains. The description on this page follows that pattern: the rule first, then the parts.

Notice what the examples leave out. No modern teams, no insight, no future. Those words fit every company in the category, which is why they help nobody choose between them.

Change one thing, then wait four weeks

You can do this in an afternoon this week. The waiting is the hard part.

  • Export the Queries report for the last four weeks. Keep every query at position 1 to 10 with enough impressions that a few extra clicks would show up.

  • Mark each query as typed or conversational. Set the conversational ones aside for this exercise.

  • For each typed query, open the page it lands on and search the query yourself in a private window. Write down the first eight words of your title and description, and of the two results above you.

  • Rewrite the title or the description, not both, so the first eight words carry the query's nouns. Keep the old text and the date in a spreadsheet.

  • Request indexing for the page in URL Inspection, then leave it alone for four weeks.

  • Compare click rate at a similar position, not raw clicks. If the position moved a lot, compare with your other queries at the new position. If the rate went up, change the other element next. If it did not, put the old text back.

Why one at a time? If you change the title, the description and the hero on the same day and clicks go up, you do not know which change did it. You will then copy the wrong one across the next ten pages. Small sites need this discipline most, because a single month of data is all you get.

The click is a promise the first screen has to keep

A snippet that says prompts, costs and retention brings in people who want to see prompts, costs and retention. If they land on a gradient and the words Data is the new oil, they go back to the results and click position 2. You won the click and lost the visit. So check the page behind every snippet you rewrite. The same nouns should appear in the headline or the first screenshot, within one scroll. Our SaaS landing page guide goes section by section through what should follow.

Where Studio Maydit fits

A slogan in the snippet is almost always a slogan on the homepage too, written by someone who knows the product too well to read it cold. That is the legibility work we do. Studio Maydit is a web and product design studio for AI founders in the US, UK and Europe, and we build in Framer, Webflow and custom code. A fixed-scope project runs three to four weeks and starts by reading your site the way a stranger meets it: the search result, the first screen, and the noun that is missing from both. If your pages rank and nobody clicks, book a 30-minute call with Studio Maydit and bring your Search Console.

Frequently Asked Questions

Table of Contents
Scroll to view headings
0%