Extended Schema Types for SEO

More Schema.org coverage. Fewer incomplete entities. One connected Yoast SEO graph. Extended Schema Types for SEO adds hundreds of canonical Schema.org types to the native Yoast SEO > Schema selectors and supplies focused fields for Google Search features. It enriches Yoast SEO's existing @graph instead of printing a disconnected second JSON-LD block. The editor separates properties into:

• Required by Google for the selected feature profile;
• Recommended by Google for stronger entity understanding;
• Additional Schema.org fields for accurate data beyond Google's current feature set.

Titles, canonical URLs, descriptions, authors, dates, publishers and featured images are reused when WordPress or Yoast SEO can infer them reliably. Inferred values remain dynamic: they are not stored as snapshots, and an editor value is persisted only when the publisher explicitly creates an override. A final server-side safety gate checks the JSON-LD that will actually be emitted, including old posts and imported metadata. Highlights

• Native Yoast SEO selectors and connected graph integration.
• Native Yoast page and Article selector values, labels and translations are preserved; only add-on types are appended.
• Canonical CamelCase types such as NewsArticle, WebApplication, DiscussionForumPosting and ProductGroup.
• Immediate missing-property feedback in the editor.
• Visual repeaters for DataCatalog datasets and Dataset downloads.
• Conditional validation for offers, reviews, ratings, variants, events, answers, comments, shipping, returns, loyalty tiers, videos and carousels.
• Native Yoast ownership preserved for AboutPage, ContactPage, CollectionPage, SearchResultsPage, ProfilePage, QAPage and BreadcrumbList; the add-on supplements supported properties without rebuilding native graph pieces.
• Author archives remain fully context-driven by Yoast SEO, with an optional per-user Person or Organization author-entity setting on the native WordPress profile screen.
• No account, API key, tracking, remote content transfer or front-end JavaScript.

Google-aware profiles The plugin includes dedicated handling for:

• Article, BlogPosting and NewsArticle, including speakable and paywalled-content properties;
• BreadcrumbList, fully delegated to Yoast SEO's connected breadcrumb node;
• Course, Movie, Recipe and Restaurant host carousels;
• Course and Dataset Search profiles;
• DiscussionForumPosting and SocialMediaPosting;
• Education Q&A with Quiz/LearningResource flashcards;
• EmployerAggregateRating and ClaimReview;
• Event and supported Event subtypes;
• image license metadata;
• JobPosting and LocalBusiness subtypes;
• MathSolver;
• Organization, merchant return policy, loyalty program and ShippingService;
• Product snippets, merchant listings and ProductGroup variants;
• ProfilePage and QAPage;
• Recipe, Review, SoftwareApplication, WebApplication, MobileApplication and VideoObject;
• explicit SoftwareApplication rating/review models: AggregateRating or Review;
• paywalled-content controls for Article/WebPage and supported CreativeWork profiles;
• VacationRental, including review/date rules and its limited-access requirements identified in the editor.

Google feature availability, eligibility and display are controlled by Google. Correct structured data does not guarantee a rich result, and every value must accurately describe visible page content. Dataset markup is for Google Dataset Search rather than ordinary Google Search results. ClaimReview remains useful for Fact Check Explorer while Google Search support is being phased out. DataCatalog and Dataset done properly DataCatalog is not presented as a standalone Google rich-result profile. Use it for a real catalog and add optional datasets through a structured repeater instead of fragile pipe-delimited rows. Each nested Dataset provides separate fields for:

• required name and 50–5,000 character description;
• URL, alternate names and identifiers;
• creator type, name, URL and sameAs;
• license, citations, keywords and version;
• temporal and spatial coverage;
• measurement techniques and variables measured;
• sameAs, isBasedOn and free-access status;
• repeatable DataDownload records with contentUrl and encodingFormat.

Incomplete nested datasets are retained in the editor but are not emitted. Creator and license can inherit from the catalog, and valid records are linked with includedInDataCatalog. Defensive output The public graph rejects or suppresses incomplete structures such as:

• virtual-only Event locations or physical venues without a detailed PostalAddress;
• Product merchant listings without image, single Offer, price and currency;
• product-level return policies without applicableCountry and returnPolicyCategory;
• Organization return policies, shipping conditions or loyalty tiers missing dependent properties;
• ProductGroup variants that do not match the selected single-page or multi-page strategy;
• reviews without author and rating, or aggregate ratings without a count;
• QAPage answers without text or answerCount;
• DiscussionForumPosting without author, publication date and visible post content;
• MathSolver actions without the {math_expression_string} target placeholder;
• comments, flashcards, clips, opening hours and downloads with incomplete records.

Broader Schema.org vocabulary The plugin also exposes valid Schema.org types that do not currently have a dedicated Google Search appearance, including HowTo, FAQPage, Service, Person, podcast types, audio types, medical entities, legislation, government services and digital documents. Schema.org support does not imply Google rich-result support. Google labels and validation rules are reserved for documented Google features. Restricted and feed-based features Some Google experiences cannot be enabled by ordinary page JSON-LD alone. Book Actions require partner onboarding and a feed. Vacation rentals are limited to eligible partners. Product policies may also be supplied through Merchant Center. The plugin identifies these limitations instead of promising unsupported eligibility. Privacy and security Saved values are nonce-protected, capability-checked, unslashed and sanitized. Output is escaped where appropriate and empty values are removed recursively. The plugin performs no tracking, remote API calls, database-table creation or public credit injection. Independent add-on disclaimer: this plugin is independently developed by Rede Piabanha. It is not developed, maintained, sponsored, endorsed or affiliated with Yoast BV or the Yoast SEO team. Yoast and Yoast SEO are trademarks of their respective owners.

1.2.1

• Fixed a critical inference-provenance bug that could persist WordPress/Yoast-derived values as static post-meta snapshots.
• Inferred titles, authors, URLs, dates, images, descriptions, publishers and other source-derived values now remain dynamic unless the editor explicitly creates an override.
• Added explicit override provenance so manually entered values remain intentional while blank inferred controls continue to follow WordPress and Yoast SEO.
• Snapshots for inferable fields no longer override current source data; affected values are safely ignored and are cleaned when the corresponding Schema controls are saved.
• Added a "Use inferred value" reset path and clearer inferred/override status in the Schema editor.
• Added live editor refresh for title and author-name inference where WordPress exposes the edited values before save.
• Moved dependent ProfilePage, QAPage and inline VideoObject inference to server-side fallbacks so blank controls always resolve from the current post.
• Prevented Classic Editor saves from erasing fields belonging to Schema profiles whose controls are not present in the current form.

1.2.0

• Re-audited the Google Search Central structured-data profiles covered by the plugin according to the current documentation.
• Preserved Yoast SEO's native graph ownership for author/taxonomy/blog archives, search results, AboutPage, ContactPage, CollectionPage, SearchResultsPage, ProfilePage, QAPage and BreadcrumbList instead of reconstructing or downgrading those nodes.
• Preserved Yoast SEO's native Article selector values, labels and translations; the add-on now appends only Article descendants that Yoast core does not already provide.
• Removed archive Loop-ID fallback logic that could incorrectly apply the first listed post's metadata to an archive graph.
• Added a native WordPress user-profile control to select each author's Schema entity as Person or Organization; Person remains the backward-compatible default.
• Organization authors reuse Yoast SEO's existing author entity identifier so Article and ProfilePage relationships remain connected.
• Aligned author classification with Yoast SEO's current wpseo_schema_person_data generation flow; the final Person/Organization choice is applied only to the exact referenced native author node.
• Removed an unused NOWDOC-based administrative bridge so the release source does not trigger Plugin Check's HEREDOC rule.
• Added an explicit Google rating/review model for SoftwareApplication, WebApplication and MobileApplication, with backward-compatible auto-detection for existing posts.
• Completed nested AggregateRating and Review fields with ratingCount/reviewCount, bestRating/worstRating, review author and review date support where applicable.
• Allowed Google-documented rating values expressed as numbers, fractions or percentages.
• Added VacationRental review validation, including required review.datePublished and France-only review.contentReferenceTime.
• Added paywalled-content controls to WebPage, Course, HowTo and Review and speakable controls to base WebPage.
• Corrected Restaurant carousel validation so name and image are required while address remains recommended.
• Aligned Event and LocalBusiness address gates with Google property tables while retaining the explicit addressCountry rule for physical JobPosting locations.
• Corrected MathSolver validation and expanded the built-in Google requirement notes and documentation mappings.
• Added docs/google-rich-results-audit.md with the audited feature matrix and intentional limitations. See changelog.txt for the complete release history.