Structured Data (Schema) in GT ACF Blocks

Overview

Several blocks output JSON-LD structured data in <script type="application/ld+json"> tags. This helps search engines understand your content and can enable rich results in search listings.

Three blocks output JSON-LD structured data automatically: Product Review, Star Rating and Table of Contents. The Accordion printed FAQPage schema until version 2.9.1, and Product Box prints none. The schema renders in script tags alongside the block, which means rich-result eligibility without an extra SEO plugin doing the markup.

Accordion Block: No Schema Since 2.9.1

Google stopped showing FAQ rich results on May 7, 2026, so the accordion block no longer outputs FAQPage schema. Version 2.9.1 removed the Enable FAQ Schema toggle. Older blocks that still carry the setting render normally and print no schema, and the Block Migrator strips that retired flag from saved blocks.

Keep using the accordion for FAQ sections. It renders native <details> and <summary> elements that readers and AI answer engines read without any markup. If a page needs FAQPage JSON-LD for another consumer, add it from one source, such as your SEO plugin.

Product Review: Product Schema

The product review block outputs a comprehensive Product schema. A Product Type field switches the type to SoftwareApplication for apps and SaaS (adding applicationCategory and operatingSystem). The schema includes:

• Review with author, reviewBody, and reviewRating
• Offer with price, priceCurrency, and availability. Offers are always generated (price defaults to "0" when empty) so Google Search Console never flags a missing price.
• hasMerchantReturnPolicy from the Return Policy field (no returns, finite window with configurable days, or unlimited)
• shippingDetails from the Delivery Type field (digital products get zero-cost instant delivery) and the Shipping Country field
• positiveNotes (pros) and negativeNotes (cons) as ItemList objects
• aggregateRating if ratings are provided
• image, falling back to the post’s featured image when no product image is set

This schema can produce rich review snippets in Google Search results. The return policy, shipping, and image fallback fields exist specifically to clear the four structured-data warnings GSC used to raise on review pages.

Star Rating: AggregateRating Schema

The star rating block outputs AggregateRating schema based on submitted user ratings. The @type of the parent object is configurable from the block settings:

• Article
• BlogPosting
• CreativeWork
• Product
• (and others)

The schema includes ratingValue (the average) and ratingCount (total number of submissions).

Table of Contents: ItemList Schema

The TOC block outputs ItemList with SiteNavigationElement typed items. Each heading linked in the table of contents becomes a ListItem with a url pointing to the heading’s anchor.

Best Practices

• Product review schema should reflect real editorial reviews, not user-generated content.
• The star rating schema suits reader ratings on recipes, software and products. Its default type, CreativeWork, and the Article and BlogPosting types no longer earn review stars in Google, so turn schema off on ordinary blog posts. Nothing prints until the first rating arrives. For editorial product ratings, use the product review block instead.
• Validate your structured data using Google’s Rich Results Test after adding blocks with schema support.

Quick answers to common questions:

Which blocks output JSON-LD schema?

Three blocks: product review (Product or SoftwareApplication with a review, offers and ratings), star rating (AggregateRating) and table of contents (ItemList). The accordion and product box output no schema. Each block’s reference entry notes its schema output.

Will block schema conflict with Rank Math or other SEO plugins?

Generally no; block-level schema covers types SEO plugins don’t generate from your content. Avoid double-declaring the same type, for example Product schema from both the product review block and Rank Math for the same product; one source per type is the rule.