LLM Best Practices

SERP features and featured snippets

5 min read

View markdown source

Overview

A SERP feature is any result block that is not a plain blue link: featured snippets at position zero, People Also Ask accordions, knowledge panels, image packs, video carousels, site links, and the AI Overview at the top. These features compress the page into a quotable answer block. Win them by matching the format Google already shows for the query, not by writing the longest page.

Structure paragraph snippets as a 40-to-60-word direct answer under an H2

The paragraph snippet is the single most-cited featured snippet type. Google extracts a 40-to-60-word block from the page and renders it under the title in the result. The block is almost always the paragraph directly after an H2 that paraphrases the query.

Template:

## What is a featured snippet?
 
A featured snippet is a result block at the top of Google's SERP that
extracts a direct answer from a page. The answer typically runs 40 to 60
words and appears above the first organic link. Google picks the source
by combining keyword match in the H2, sentence clarity, and on-page
authority signals.

The H2 mirrors the query. The opening sentence states the definition or answer. The remaining sentences add one specific fact each. No preamble, no marketing copy, no filler phrasing.

Structure list snippets as an ordered list under a step-or-rank H2

Google extracts list snippets from <ol> or <ul> blocks immediately following an H2 that signals enumeration: “how to,” “steps to,” “best ways to,” “types of.”

## How to set a canonical URL
 
1. Add a `<link rel="canonical" href="...">` tag inside the page `<head>`.
2. Point the `href` at the absolute, HTTPS, self-referential URL.
3. Confirm one canonical per page, no duplicates.
4. Verify with the Rich Results Test.

The first 6 to 8 items appear in the snippet; deeper lists are truncated. Front-load the steps the searcher actually needs.

Structure table snippets as a single comparison HTML table

Google extracts table snippets from <table> elements that follow an H2 phrasing the comparison: “X vs Y,” “X by year,” “X pricing.” The table must have a <thead> row.

| Plan | Price | Storage |
|---|---|---|
| Free | $0 | 1 GB |
| Pro | $20 | 100 GB |
| Team | $50 | 1 TB |

Keep tables under 6 columns and 10 rows. Larger tables get truncated unpredictably. The first column is the row label; the first row is the column header. See schema-markup-deep for the optional Product schema that pairs with pricing tables.

Add FAQPage schema to win People Also Ask

People Also Ask (PAA) is the expanding question accordion. Google sources PAA answers from pages with clear Q&A blocks and, where present, FAQPage JSON-LD. The schema does not guarantee inclusion, but a body that already reads as Q&A plus matching JSON-LD increases the odds.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "What is a featured snippet?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "A result block at the top of Google's SERP that extracts a direct answer from a page."
    }
  }]
}

Match the name field to a real H3 in the body and the text field to the first paragraph under that H3. Mismatches between schema and body trigger structured data errors in GSC; see structured-data.

Pair definitions with DefinedTerm schema for knowledge panel candidacy

Knowledge panels appear for entities Google recognizes as named things: people, products, organizations, concepts with a stable definition. For concept pages, structure the opening paragraph as a single-sentence definition and mark it up with DefinedTerm or the matching Article subtype.

{
  "@context": "https://schema.org",
  "@type": "DefinedTerm",
  "name": "Featured snippet",
  "description": "A result block at the top of Google's SERP that extracts a direct answer from a page.",
  "inDefinedTermSet": "https://example.com/glossary/"
}

A glossary folder of DefinedTerm pages compounds the effect; each term cross-links to the deep-dive page that explains it. See ai-search-optimization for how the same structure helps AI search citation.

Audit the SERP before writing the page

Search the target query in an incognito window with Google set to your target country. Note every feature in the result: snippet type, PAA questions, image pack, video carousel, AI Overview, knowledge panel. Reverse-engineer the formatting from the winning page.

  • If a paragraph snippet wins, an H2 plus 40-to-60-word block is the format.
  • If a list snippet wins, an ordered list under an H2 is the format.
  • If no snippet appears, do not force one; write for the dominant result type instead.

The audit takes 3 minutes per query and replaces guesswork. Match the format that already wins; see keyword-research for the upstream query selection and content for the on-page rules that surround the snippet block.

Common errors

  • Snippets longer than 60 words. Google truncates aggressively; the snippet ends mid-sentence and the click-through suffers. Keep the answer block tight.
  • No keyword anchor in the first paragraph. The H2 matches the query but the body opens with backstory. Lead with the answer.
  • Schema markup that does not match the body. FAQPage JSON-LD listing a question the page does not actually ask is a structured data violation. Mirror the body exactly.
  • Stuffing every page with FAQPage schema. Google deprecated the rich result for most non-government, non-health sites in 2023; only mark up real FAQ content. See title-tags for the related title-stuffing trap.
  • Writing for a snippet that does not exist for the query. If the SERP shows ten blue links and no features, no snippet block will appear no matter how the page is structured. Audit first.

Graph View

Backlinks