內容簡介
Extended Schema Types for SEO 外掛提供更精確的結構化數據選擇，幫助網站擁有者和開發者在 Yoast SEO 中添加特定的 Schema.org 類型和屬性，提升內容的可見性和描述準確性。
【主要功能】
• 提供數百種額外的 Schema.org 類型
• 清晰標示 Google 所需及建議的屬性
• 重用現有的 WordPress 和 Yoast SEO 資料
• 支援五顆星的訪客評分小工具
• 針對不同出版需求進行設計
外掛標籤
開發者團隊
② 後台搜尋「Extended Schema Types for SEO」→ 直接安裝（推薦）
原文外掛簡介
Your content deserves structured data that describes what it actually is.
Yoast SEO handles common schema needs well. When a page describes a software application, dataset, course, product variant or another specific entity, you may need more precise types and properties. Extended Schema Types for SEO adds those choices inside the familiar Yoast SEO > Schema panel, without replacing Yoast or creating a competing JSON-LD graph.
Choose the accurate type, complete missing properties and validate the result. This plugin does not promise rankings, clicks or rich results.
What you gain
More precise descriptions: hundreds of additional canonical Schema.org types, including WebApplication, SoftwareApplication, ProductGroup, Dataset, Course, Event and specialized articles.
Clearer editing decisions: fields identified as Google-required, Google-recommended or additional Schema.org properties, with contextual checks for dependent data.
Less repetition: reuses current WordPress and Yoast SEO titles, canonical URLs, authors, dates, descriptions and images where reliable. Inferred values stay dynamic unless you explicitly override them.
Continuity with Yoast: enriches Yoast’s connected @graph while preserving its native page, article, author and breadcrumb entities.
Optional visitor feedback: an opt-in five-star voting widget for eligible items, with locally saved votes and calculated aggregateRating values.
Best for: publishers, developers and site owners who need more precise schema. If Yoast already describes a page correctly, additional markup may be unnecessary.
A short path to your first result
Open a post or page, then Yoast SEO > Schema.
Choose the type that represents the visible content. Complete the applicable Schema.org fields.
Publish or update, then verify the public output with the Google Rich Results Test and, for broader vocabulary, the Schema Markup Validator.
Do not invent values to satisfy a test.
Built for different publishing needs
Publishing: articles, discussions, supported reviews, fact checks and paywalled-content properties.
Software and commerce: applications, products, variants, offers, shipping, returns and rating/review models.
Education and data: courses, datasets, catalogs, educational Q&A and structured downloads.
Other entities: events, jobs, organizations, businesses, recipes, movies, videos and image licenses.
Google rich-result eligibility varies by feature. Some require additional programs or feeds.
Structured validation, not extra guesswork
The editor checks dependent fields for products, events, ratings, reviews, datasets, Q&A and videos. Incomplete nested structures can remain editable without being emitted as valid markup.
For DataCatalog, repeaters organize nested Dataset entries with creators, descriptions, licenses and downloads. DataCatalog alone is not a Google rich-result type.
Important: Schema.org vocabulary, valid JSON-LD and Google’s rich-result eligibility are different. Valid markup does not guarantee rankings, clicks or traffic.
New in 1.3.0: Five-star visitor voting
Enable five-star visitor ratings under Yoast SEO > Schema > Schema.org fields for an eligible published item. This checkbox is off by default; enabling it is the publisher’s decision.
Vote: readers select one of five stars. Accepted submissions are saved in a dedicated WordPress database table.
Numbers, not placeholders: the public summary displays average (vote count), such as 0.0 (0) before voting or 4.8 (12) when supported by real votes.
Connected structured data: the plugin calculates aggregateRating.ratingValue and ratingCount from recorded votes. With zero votes, it does not invent an aggregate rating.
Placement and appearance: the widget follows the post content by default, or can be placed via [rp_extfs_rating]. Its basic typography and colors follow the active theme.
Control over existing data: disabling visitor voting preserves previously entered manual rating metadata and does not delete recorded votes.
Repeat votes: limited per WordPress account or anonymous browser cookie; not fraud-proof.
Supported types include SoftwareApplication, WebApplication, MobileApplication, OperatingSystem, RuntimePlatform, VideoGame, Recipe, Movie, Product and supported product descendants. The plugin does not offer self-serving Organization or LocalBusiness rating widgets.
Enable ratings only when visitors can genuinely evaluate the specific item shown.
Cache: accepted votes can purge WP Rocket’s post cache. For other caches/CDNs, configure invalidation. Voting uses a normal HTML form, without depending on JavaScript or AJAX; the result reload bypasses normal page caching.
Privacy and operational boundaries
No external account, API key, telemetry or remote rating provider is required. No public attribution link is inserted.
Optional voting stores post ID, score, timestamp and a salted pseudonymous voter identifier locally. Anonymous voters receive a one-year HttpOnly cookie; a salted, short-term IP-based limit mitigates abuse. Raw IPs are not saved in vote records. Only totals are public.
Review privacy and consent obligations before enabling voting; WordPress supplies suggested Privacy Policy Guide text. Browser cookies cannot verify unique identities.
Support and feedback
For help, open a support topic with WordPress/Yoast versions, the schema type and reproduction steps. Never share passwords or personal data.
If it helps your work, review the plugin on WordPress.org. Five stars are welcome if genuinely deserved. Constructive feedback also helps guide development. Reviews are optional.
Independent add-on: developed by Rede Piabanha. Not developed, maintained, sponsored or endorsed by Yoast BV. Yoast and Yoast SEO are trademarks of their respective owners.
Software app fields now include practical examples and conservative inference from explicit post metadata or matching WooCommerce product details. Manual values take precedence; no prices or ratings are invented. WebApplication adds browserRequirements.
