"Optimize for snippets" is common SEO advice, but it's hard to act on when you've never actually looked closely at what a snippet is. Is it the little paragraph at the very top of the results page? The stars under a listing? The FAQ dropdown? The honest answer is: all of the above, and they don't all work the same way.
Before chasing a snippet, it helps to see exactly what each type looks like on the page, where it appears relative to normal results, and what kind of content earns it. This guide walks through the real appearance of each one.
A Google snippet is either a featured snippet — a boxed answer pulled from one page and placed above the normal results — or a rich snippet, a regular result enhanced with extras like star ratings, prices, or an FAQ dropdown. Featured snippets come from plain text, lists, or tables; rich snippets come from structured data (schema markup) added to the page.
What does a Google snippet actually look like?
"Snippet" gets used as a catch-all term, but on the actual results page it shows up in a few distinct visual forms:
- Featured snippet. A single boxed result placed above position one, showing a short paragraph, numbered list, bulleted list, or table pulled straight from a page's normal content.
- Rich snippet. A normal-position result with extra visual details layered underneath it — star ratings, review counts, price, stock status, or an author's headshot — generated from schema markup.
- FAQ / expandable snippet. A result with one or more collapsed questions underneath it that expand in place when clicked, without leaving the results page.
- People Also Ask. A separate stack of expandable questions, related to but visually distinct from any one listing, that can appear anywhere on the results page.
The common thread: every snippet type is Google reformatting existing page content into a more scannable shape, not new content Google invents on its own.
Why this matters for your search visibility
Knowing what each snippet actually looks like changes how you evaluate your own search presence:
- Position one isn't always the top of the page. A featured snippet sits above it, so a page ranking second or third can still visually outrank the page in position one.
- Rich snippets don't move your ranking, they change your listing. Stars and prices make an already-ranking result more clickable; they aren't a separate ranking boost.
- Different snippets need different work. A featured snippet is earned through clear, well-formatted answer content; a rich snippet is earned through accurate schema markup. Chasing the wrong one wastes effort.
- Snippets are not permanent. Google reassigns featured snippets and re-validates rich results regularly, so a listing's appearance can change without the page itself changing.
Step-by-step: checking and shaping your own snippet
- Search your target query in an incognito window. This avoids personalized results skewing what you see, giving you a closer look at the actual public listing.
- Identify which snippet type, if any, currently appears. Note whether it's a featured box, a rich result with stars or price, an FAQ dropdown, or a plain listing with none of the above.
- For a featured snippet, tighten the on-page answer. Place a direct, self-contained answer in a short paragraph, numbered list, or table right under the heading that matches the query.
- For a rich snippet, add the matching schema type. Product schema for ratings and price, FAQPage schema for expandable questions, Article schema for author and date details.
- Validate before publishing. Run the page through Google's Rich Results Test to preview the rich result and catch any structural errors.
- Re-check after the page is re-crawled. Search the query again after a few days to see whether the intended snippet actually appeared, since eligibility doesn't guarantee display.
Common mistakes when chasing snippets
1. Confusing the two snippet families
Adding schema markup and expecting a featured snippet, or rewriting page copy and expecting star ratings to appear, targets the wrong mechanism — the two are earned through different work entirely.
2. Burying the direct answer
A page can have the best answer on the web, but if it's wrapped in three paragraphs of preamble before the actual answer, Google has nothing clean to extract into a featured snippet box.
3. Marking up content that isn't visible to a reader
Structured data describing a rating, price, or FAQ answer that doesn't appear anywhere on the rendered page violates Google's guidelines and puts the rich result at risk of being suppressed.
4. Treating a snippet as permanent
A featured snippet or rich result won without ongoing upkeep can quietly disappear if a competitor's page answers more directly, or if the underlying page content drifts out of date.
Real-world examples
How different snippet types actually show up for different kinds of queries:
Each example pulls from content the page already had — none of these required writing new material specifically "for Google."
Snippet types compared
How the main snippet types differ in where they appear, what earns them, and what they require.
| Snippet type | Where it appears | What earns it | Requires schema? |
|---|---|---|---|
| Featured snippet | Boxed, above position one | Clear, extractable text, list, or table | No |
| Rich snippet (ratings/price) | Underneath a normal listing | Accurate Product or Review schema | Yes |
| FAQ dropdown | Underneath a normal listing | FAQPage schema matching visible Q&A | Yes |
| People Also Ask | Standalone block, anywhere on page | Related pages answering nearby questions | Sometimes |
Build the schema behind rich snippets — free
The Rebrixe Schema Generator produces clean, validated JSON-LD for Product, FAQPage, Article, and other common types — the exact markup that drives rich snippets in search results. No account, no watermark, just fill in the form and copy the code.