Block Reference
Complete reference for all 21 Egg Blocks. Each entry lists the block's purpose, variants, fields, product binding, and related blocks. For concepts, getting started, and recipes, see the Introduction.
Block index
Article Structure
callout · conclusion · faq · intro · section-header · step-list · toc
Editorial Insights
criteria · definitions · key-takeaways · methodology · myth-fact · pros-cons
Product & Commerce
comparison-table · product-card · quick-picks · rating-breakdown · specifications · verdict · where-to-buy
Navigation
related-posts
Core block
Paragraph (allowed as a fallback)
Common fields
Many blocks share the same header and TOC fields. They're documented once here; block entries below mention only the unique fields.
Header fields
Most blocks support a two-level header:
Section label — small uppercase eyebrow text above the title (e.g. "Key takeaways", "Where to buy"). Often has a sensible default per block; leave empty to hide.
Title — large bold heading for the block. Optional. Leave empty to hide.
Heading level —
h1,h2,h3,h4, ordiv. Defaulth2. Usedivwhen you want the heading look without it counting as a document heading (useful for tables of contents).
TOC metadata
Blocks that support the table of contents expose four fields:
Anchor — becomes the URL anchor (the
#somethingat the end of the link) and the TOC jump target.TOC label — the text shown in the TOC.
Include in TOC — toggle on to register this block in an auto-mode TOC.
Level — TOC indent depth. Default
2.
See Introduction → Table of contents integration for the full rules.
Article Structure
callout
Purpose. Editorial aside for a note, tip, warning, or insight adjacent to prose.
When to use. Call out important context without breaking the main reading flow. Good for safety warnings in how-tos, editor's notes, disclaimers, and quick tips.
Variants.
Default — standalone aside in article flow.
Compact — nested or space-tight usage.
Fields.
Callout type
note, tip, warning, or insight. Controls color, icon, and default label.
Label override
Replace the default label for the chosen type. Optional.
Title
Meaningful only in the default variant. Optional.
Body
The callout content. Required.
Product binding. None. Header fields. Title only (no section label). TOC support. No.
conclusion
Purpose. Closing summary block with optional takeaway bullets and next-step links.
When to use. End of a review, roundup, or guide. Wraps up the article and points readers toward logical next actions.
Variants.
Default — full standalone article close.
Compact — short wrap-up for nested or short-form contexts.
Fields.
Points
Bullet list of takeaways. Optional.
Summary
The main closing text. Required.
Next steps label
Eyebrow label above the next-step links. Optional.
Next steps
Link list (text + URL). Use real URLs, not #.
Product binding. None. Header fields. Yes (section label, title, heading tag). TOC support. Yes.
faq
Purpose. Reader Q&A block for common questions and SEO-friendly answer coverage. Outputs FAQPage structured data automatically so your FAQs can qualify for Google's FAQ rich results.
When to use. Bottom of any article. Especially useful for buying guides, reviews, and how-tos where readers arrive with specific questions.
Variants.
Default — collapsible accordion.
Flat — always-open static Q&A list.
Fields.
Items
Repeatable list of question + answer pairs. Both required.
Collapsed by default
When on, accordion items start closed. Off by default.
Enable schema
Output FAQPage structured data for Google rich results. On by default.
Product binding. None. Header fields. Yes (section label defaults to "Frequently Asked Questions"). TOC support. Yes.
intro
Purpose. Article-opening orientation block with lead framing and optional preview list.
When to use. First block of most articles. Frames what the article is, who it's for, and what the reader will learn.
Variants.
Default — full-length article intro.
Compact — shorter intro when prose should stay tight.
Fields.
Lead
The 1–2 sentence hook. Required.
Body
Longer supporting prose. Optional. Works in both variants.
Points label
Eyebrow label above the preview bullets. Optional.
Points
Bullet list of article highlights. Optional.
CTA label
Button text. Optional.
CTA URL
Button target URL. Optional.
Product binding. None. Header fields. Yes. TOC support. Yes.
section-header
Purpose. Named section opener for procedural steps or editorial framing before a grouped block.
When to use. Introduce a step in a guide, or frame a group of related blocks (e.g. a "Top Pick" cluster of product-card + pros-cons).
Variants.
Default — step header in a guide sequence.
Accent — stronger "Step N" treatment.
Editorial — framing header before lists, grids, or grouped recommendations.
Fields.
Step number
For default/accent variants. Optional.
Title
Main heading text. Required.
Subtitle
Supporting subhead. Optional.
Step label text
Override the "Step" word. Optional.
Kicker
Small text above the title. Optional.
Meta
Small text below the title. Optional.
Chips
Tag-like labels. Most useful in editorial variant. Optional.
Product binding. None. Header fields. Title + heading tag only (no separate section label — the block is a section header). TOC support. Yes.
step-list
Purpose. Ordered steps, checklist items, or scan-friendly instructional sequences.
When to use. How-to articles, setup guides, processes. Step numbers are derived from item order — no manual numbering.
Variants.
Default — strict sequential process.
Checklist — completeness-focused tasks where order is advisory.
Cards — steps that need visual separation.
Card grid — parallel-scanning overview.
Fields.
Steps
Repeated title + description. Title required per step; description optional.
Note
Small footer note. Optional.
Product binding. None. Header fields. Yes (section label defaults to "Step List"). TOC support. Yes.
toc
Purpose. Table of contents for anchor navigation within the article.
When to use. Long-form articles (5+ major sections), roundups, buying guides. Improves scanability and supports in-article jump links.
Variants.
Default — standard TOC with optional sub-items.
Compact — dense flat TOC for many sections.
Numbered — sequence-oriented TOC for listicles and guides.
Fields.
Label
Heading above the TOC. Optional.
Source mode
Auto pulls items from other Egg Blocks on the page; Manual uses the items you list here.
Items
Manual-mode entries: text + anchor, with optional sub-items (default variant only).
Collapsible
Let readers collapse the TOC. On by default.
Default open
Whether a collapsible TOC starts open. On by default.
Product binding. None. Header fields. Label only (no separate section label / title pair). TOC support. N/A — this block is the TOC.
Editorial Insights
criteria
Purpose. Buying-criteria guidance — what to prioritize, what to look for, and what to avoid.
When to use. Buying guides and roundups to give readers a framework for evaluating products themselves.
Variants.
Default — 2×2 panel treatment (best with 4 criteria).
List — linear reading flow (best with 3–6 criteria).
Fields.
Criteria
Repeated items: title + description + importance (high/medium/low) + look-for text + avoid text.
Product binding. None. Header fields. Yes (section label defaults to "What to look for"). TOC support. Yes.
definitions
Purpose. Glossary-style term and definition pairs for jargon, terminology, or spec explanations.
When to use. Explainer articles, technical reviews, or any content where readers might not know the terms.
Variants.
Default — row-card glossary.
Compact — lower-interruption inline glossary.
Inline — integrated prose-adjacent terminology list.
Cards — equal-weight 2-column grid.
Fields.
Items
Repeated term + definition. Best kept to 3–6 items.
Product binding. None. Header fields. Yes (section label defaults to "Definitions"). TOC support. No.
key-takeaways
Purpose. Concise editorial insights or conclusions — separate from product-spec data.
When to use. Top of an article as an at-a-glance summary, or interspersed at section breaks. Not for raw specs or commerce facts — use specifications or product blocks for those.
Variants.
Default — standalone icon list.
Compact — nested or tight-column summary.
Inline — prose-adjacent quick list.
Cards — top-of-article or equal-weight takeaway grid.
Fields.
Items
Repeated text + optional title per item.
Note
Small footer note. Optional.
Product binding. None. Header fields. Yes (section label defaults to "Key Takeaways"). TOC support. Yes.
methodology
Purpose. Explains how recommendations were evaluated — adds credibility and transparency.
When to use. Roundups, buying guides, and any content where readers should trust your selection process. Strong E-E-A-T signal.
Variants.
Default — parallel criteria list.
Timeline — ordered evaluation process.
Grid — compact 2×2 methodology overview (best with 4 items).
Fields.
Description
Block-level lead text. Optional.
Items
Repeated items. In default/timeline: title + description. In grid: icon + title + description.
Note
Small footer note. Optional.
Product binding. None. Header fields. Yes. TOC support. Yes.
myth-fact
Purpose. Debunks misconceptions as myth/fact pairs or verdict-rated claims.
When to use. Educational articles, category explainers, or when you want to counter common misunderstandings.
Variants.
Default — full myth vs. fact treatment with optional explanation row.
Inline — fast-scanning claim-verdict list.
Fields.
Items
Repeated: myth text, fact text, optional "why" explanation, verdict badge, verdict tone (true/false/partial/neutral), verdict text.
Label overrides
Rename "Myth", "Fact", "Why". Optional.
Product binding. None. Header fields. Yes (section label defaults to "Myth vs Fact"). TOC support. No.
pros-cons
Purpose. Structured strengths and weaknesses summary for a product or recommendation.
When to use. Reviews, product evaluations, and anywhere readers need a quick trade-off snapshot.
Variants.
Default — standalone review assessment.
Compact — nested inside shared layouts.
Highlight — high-attention summary near top of article.
Inline — minimal prose-adjacent aside.
Fields.
Pros
List of strengths. 4–12 words each.
Cons
List of weaknesses. 4–12 words each.
Best for
Who benefits most. Optional.
Not for
Who should skip. Optional.
Quick take
One-sentence verdict. Optional.
Label overrides
Change default labels ("Pros" → "Strengths", etc.). Optional.
Product binding. None. Header fields. None — no section label or title. TOC support. No.
Product & Commerce
comparison-table
Purpose. Multi-product comparison table with shared criteria across rows.
When to use. Roundups (3+ products) and head-to-head comparisons (exactly 2 products).
Variants.
Default — standard side-by-side comparison, 3+ products.
Versus — head-to-head comparison, exactly 2 products.
Product list — dense quick-reference table where criteria become columns.
Fields.
Heading label
Small eyebrow above the table heading. Optional.
Heading title
Main table heading. Optional.
Heading level
Default is a plain div (no document heading). Set to h2 or h3 if you want the title to count as a heading.
CTA label
Text for row-level buttons. Optional.
Footer note
Small note below the table. Optional.
Items
Rows — each needs a Content Egg product plus optional title, role label, and "winner" flag.
Criteria
Columns — each has a label, a value type (text, score, stars, yes/no, or price), and a value per row. For the price type the live price comes from Content Egg, so any value you type is ignored.
Product binding. Required per row. Header fields. Uses its own heading label and title fields instead of the shared section label / title pair. TOC support. Yes.
product-card
Purpose. Single product recommendation card bound to a Content Egg product.
When to use. Featured product blocks, top-pick callouts, or per-product cards in roundups.
Variants.
Default — standard recommendation card.
Featured — top-pick or lead recommendation.
Compact — lower-ranked scan-friendly row.
Fields.
Product
The Content Egg product (module + unique ID) this card represents. Required.
Title
Your editorial title override for the product. Optional.
Subtitle
Short positioning line. Hidden in compact.
Merchant
Merchant name override. Optional.
Badge
Small status tag (e.g. "Editor's Pick"). Hidden in compact.
Rank
Rank number for roundup usage. Optional.
Score
Editorial score. Hidden in compact.
Description
1–2 sentence explanation. Hidden in compact.
Chips
Short feature tags (max ~4). Hidden in compact.
CTA label
Button text override. Optional.
Product binding. Required. Header fields. The block has its own separate "Block title" field (so it doesn't clash with the product's own title), plus optional section label and heading level. Skip these when using the card inside a roundup; fill them in for a standalone featured callout. TOC support. No.
quick-picks
Purpose. Multi-product shortlist driven by Content Egg — a ranked list with editorial overrides.
When to use. Roundup "at-a-glance" sections, alternatives lists, or "best in category" shortlists.
Variants.
Default — ranked shortlist.
Compact — tighter ranked list.
Alternatives — "consider instead" set after a lead recommendation.
Shelves — grouped by use case rather than rank.
Grid — finalists matrix.
Highlight — lead pick plus supporting picks.
Fields.
CTA label
Row-level button text. Optional.
Items
Rows — each needs a Content Egg product plus optional editorial overrides (title, subtitle, merchant, badge, description, chips, score). Row order sets the rank.
Product binding. Required per row. Header fields. Yes (section label defaults to "Quick picks"). TOC support. Yes.
rating-breakdown
Purpose. Visual score breakdown for one product — overall score plus per-category scores.
When to use. Review articles with quantified evaluation. Pairs well with verdict and pros-cons.
Variants.
Default — main review score breakdown.
Compact — space-constrained score view.
Grid — hero-score treatment with category grid. Best with 6 categories; extras are clamped.
Category grid — category-only scoring without overall score.
Fields.
Overall score
Main 0–10 score. Ignored in category-grid variant.
Overall denominator
Denominator text. Default "out of 10".
Stars
Star rendering (0–5). Ignored in category-grid.
Categories
Per-category label + score pairs.
Product binding. Optional. By default the block shows editorial scores only; binding a product lets the button link to the merchant through Content Egg. Header fields. None. TOC support. No.
specifications
Purpose. Structured factual spec display for a product.
When to use. Spec tables in reviews and product deep-dives.
Variants.
Default — full spec grid with icons.
Compact — nested label/value table.
Highlight — at-a-glance stat band.
Fields.
Specs
Rows — each with an icon (default variant only), value, and label.
Product binding. None. Header fields. Yes in default variant only. Section label defaults to "Key specs" when empty; compact and highlight variants render no header. TOC support. No.
verdict
Purpose. Single-product editorial verdict with score, summary, and CTA.
When to use. End of a review article, summarizing the overall take in one block.
Variants.
Default — standard review conclusion block.
Compact — lighter-weight inline verdict.
Summary — full visual closing verdict.
Fields.
Score
Overall score. Optional.
Score denominator
Default "/ 10".
Score label
Only meaningful in summary variant. Optional.
Title
Verdict headline. Optional.
Award label
"Editor's Choice", "Best Value", etc. Optional.
Chips
Short highlights (not prose). Optional.
Verdict text
The main verdict paragraph. Required.
CTA label
Button text. Optional.
CTA URL
Button target. Optional.
Product
Link to a Content Egg product. Optional, but recommended when you want the button URL to come from Content Egg with affiliate tracking.
Band label
Only meaningful in summary variant. Optional.
Product binding. Optional. Header fields. Title only. TOC support. No.
where-to-buy
Purpose. Multi-offer merchant block backed by Content Egg — buying options and price comparison.
When to use. Near the end of review articles, or as a standalone offer table. Ideal when the article isn't a roundup but still needs clear purchase paths.
Variants.
Default — full multi-merchant comparison.
Compact — tighter offer list.
Table compact — densest table layout.
Fields.
CTA label
Row button text override. Optional.
Footer note
Small disclosure or shipping note. Optional.
Items
Offer rows — each needs a Content Egg product, plus optional merchant override, title, and chips. Live price, stock, buy URL, and merchant logo all come from Content Egg automatically.
Product binding. Required per row. Header fields. Yes (section label defaults to "Where to buy"). TOC support. Yes.
Navigation
related-posts
Purpose. Internal navigation block linking to related articles on your site.
When to use. End of article, mid-article section breaks, or as a standalone "related reading" section. You pick the posts; the block pulls titles, excerpts, and thumbnails from WordPress automatically.
Variants.
Compact — text-only chevron list with optional snippets. 3–6 items. Good for tight spaces.
Media list — thumbnail + badge + title + excerpt rows. 3–5 items.
Cards — 2-column grid with cover images. 4 items recommended.
Featured — hero card (first item) + thumbnail list (remaining). 4–6 items.
Fields.
Items
Repeatable list of posts — each has a WordPress post ID plus optional title, badge, and snippet overrides. When overrides are empty, the block falls back to the post's title, first category, and excerpt.
Notes.
Items pointing to a post that no longer exists are skipped silently.
Scheduled posts render as plain text without a link.
Item order sets visual hierarchy — in the featured variant, the first item becomes the hero card.
Product binding. None. Header fields. Section label only (defaults to "Related Articles" if not overridden). TOC support. No.
Core block
Paragraph
The standard Gutenberg Paragraph block isn't an Egg Block, but it's fine to use as a fallback for short connecting prose between major sections where no Egg Block fits — for example, a one-sentence lead-in before a comparison table.
Most editorial prose should live inside Egg Block fields instead: the intro body, conclusion summary, callout body, key-takeaway note, section-header subtitle, methodology description, or a dedicated callout block. Reach for those first.
Other core Gutenberg blocks (Heading, List, Quote, Image, Table, Columns, and so on) shouldn't be used alongside Egg Blocks — each has a semantic Egg Block equivalent (section-header, key-takeaways, pros-cons, callout, specifications, comparison-table, step-list, faq).
Last updated