Snippet SEO

A snippet is what Google shows for your page in the search results: the blue link, the green URL, and the short description below it. That description is the part you can influence most directly. Google pulls it from your meta description tag, but also from visible content on the page if it thinks that text is more relevant to the query. I have seen cases where my meta description was completely ignored and Google used a sentence from the middle of the article. That is not a bug; it is the algorithm deciding what the searcher wants to see.

There are three types of snippet you need to distinguish. The standard snippet is the basic result everyone gets. A featured snippet is a boxed answer that appears above the organic results—often a paragraph, list, or table. A rich snippet includes extra data like star ratings, pricing, or recipe times, and it requires structured data from schema.org. I have found that most of the traffic gain from snippet work comes from the standard snippet, because it affects click-through rate for every query, not just the ones that trigger a featured box.

Google highlights the words from your snippet that match the search term. That means you do not need to repeat the exact keyword; showing you understand the topic is enough. For example, a page about "how to prune a rose bush" might get highlighted for "pruning roses" even if the phrase is not in the snippet. The matching happens on the server side, not from your wording.

My plain-English rule: the snippet is the first impression you get in search. If it does not clearly answer why someone should click, you lose the visit.

Snippet optimisation matters most when you are competing for clicks on pages that rank outside the top three positions. A well-crafted snippet can lift your click-through rate by 20–30% even from position five. I saw this happen for a client in the home services space: a page ranking #4 for "emergency plumber cost" got a 41% increase in organic clicks after I rewrote the meta description to include a price range and a clear call to action. The ranking did not change, but the snippet made the result look more useful.

It also matters when your page is eligible for a [featured snippet](/featured-snippets/). If you can get the featured box, you jump to position zero and capture a large share of clicks. But the format matters. Google prefers answers that are concise, direct, and structured. For "how to fix a leaky faucet" a step-by-step list works better than a paragraph. I always check the current [SERP](/serp/) to see what format is already winning the featured snippet, then model my content accordingly.

On the other hand, snippet optimisation is less important for brand searches where your site is the obvious answer. If someone searches your company name, the snippet barely influences the click. Also, for pages that already rank #1 with a high CTR, tweaking the snippet might not improve anything and could even hurt if Google decides to rewrite it into something worse.

A practical check: open Google Search Console, go to the Search Results report, and look at the average CTR for your top pages. If you see a page with good [keyword ranking](/keyword-ranking/) but low CTR, the snippet is likely the culprit. I have fixed dozens of pages that way, and the fix is usually a one-line change to the meta description.

I used to believe that if I wrote a perfect meta description with the exact keyword, Google would show it every time. That is not true. Google rewrites snippets for a large percentage of searches—I have seen estimates of 30–70% of queries, depending on the niche. My own data shows that about half of my pages have a snippet different from the tag I set. I wasted hours perfecting meta descriptions for pages that Google would never use as written. Now I focus on making the page content itself clear and well-structured, because that is what Google actually reads.

Another mistake: I thought rich snippets were always a good thing. I added schema markup for reviews and recipes on every possible page. But for some pages, a rich snippet with a rating can backfire. If the average rating is 3.5 stars and competitors have 4.5, showing that rating in the snippet may reduce clicks. I learned to check the [SERP features](/serp-features/) before deciding whether to enable rich results.

I also got the length wrong. I used to write meta descriptions exactly 155 characters, based on outdated advice. Google now shows snippets that can be 200–300 characters on desktop, and the length varies by device. The real constraint is not character count but whether the snippet communicates the value proposition in the first 120 characters. I now write descriptions that are functional, not truncated.

Finally, I assumed that snippet optimisation was a one-time task. It is not. Google changes how it generates snippets, and competitors update their pages. I check snippets for my top pages every quarter using a [keyword rank checker](/keyword-rank-checker/) to see if the displayed text has changed. If it has, I decide whether to update the page content or adjust the meta tag.