It is worth considering, but the decision should depend on your site’s content and the search features you want to target. There is no need to add every type of markup across the board. schema.org describes content using a shared vocabulary, allowing search engines to display more useful information. It does not guarantee traffic or better rankings. There are reasonable grounds for choosing a shared standard over platform-specific formats, but that does not mean it will remain applicable forever or that Google and Bing will display the same results.
A shared standard has value, but platform support can differ
schema.org was originally developed by Google, Microsoft/Bing, and Yahoo, with Yandex joining later. That sets it apart from a format introduced by a single search engine. However, participation by several companies does not guarantee continued platform support. Some participants in public discussions suggest that it may last a long time, but these are assessments, not platform commitments.
Clothing sizes offer a concrete example. Google’s documentation says Google can interpret text values for some sizing systems and size groups, but other search engines may not. It therefore recommends using standard schema.org enumeration values. A shared vocabulary helps with compatibility, but does not mean that every platform supports the same search features.
Start with the page content, then choose markup with a clear purpose
To decide whether the investment is worthwhile, first ask: What information does the page provide? Does it match features supported by the target platform? Google provides relevant documentation for these two types of content:
- Reviews and ratings: For content about products, books, recipes, and similar items, consult the review snippet guidelines. When Google finds valid markup, it may display star ratings and summary information, but this is not guaranteed.
- Datasets: Google can interpret dataset information through Dataset markup or equivalent DCAT structures. Google’s documentation examples recommend JSON-LD and schema.org. Google also accepts the same vocabulary expressed in RDFa or Microdata.
Check the restrictions before adopting markup. For example, the LocalBusiness and Organization types in review snippets apply only to sites that collect reviews of other businesses or organizations. Sites must also follow the rules on self-serving reviews. Simply being a business does not mean that marking up reviews of your own business will earn star ratings in search results.
Focus on how information is displayed, not on guaranteed growth
When implementing markup, add the properties required for the target feature, follow the guidelines, and test it. Sites using a CMS can also evaluate integrated plugins. Google’s Rich Results Test can preview most relevant features, but the documentation cautions that the actual display may differ from the preview.
A sensible starting point is to choose pages whose content clearly matches the target feature, rather than treating the amount of markup as a measure of success. Some participants in public discussions suggest that more useful information in search results may bring traffic, but there is no guarantee. The available material does not provide specifications for Bing’s relevant features, so Google’s examples cannot be directly applied to Bing.
schema.org markup: perspectives from across the web
Is it worth implementing schema.org specifically to gain more citations in AI search?
It is not worth investing solely to gain AI citations. One article argues that marking up entities and relationships helps AI understand and cite content. Another article summarizing Google's guidance, however, states that structured data is not required for Google's generative AI search and that there is no AI-specific schema. Standard markup can still be used for eligible rich results, but it does not guarantee citations.
If AI can extract information from markup, does that mean it understands schema.org semantics?
Not necessarily. In one experiment, a system returned an address from syntactically valid JSON even though its types and properties were not valid schema.org vocabulary terms. The experiment's author therefore concluded that this result could not demonstrate that the system parsed the data according to schema.org semantics. However, a single experiment also cannot establish that no AI systems parse valid markup.
Can implementing markup improve the chances of appearing in Google featured snippets?
The available material does not establish that markup improves those chances. An analysis of a 2017 dataset found that URLs using the schema.org markup described in the analysis accounted for a smaller share of featured snippets than of regular search results. However, Wikipedia, which had the most featured snippets in that dataset, did not use that markup, potentially skewing the findings. This was an association observed during a specific period. It does not establish that markup decreases or increases the chances of appearing in a featured snippet.
Are platforms that operate forums required to adopt schema.org?
Not all forums are subject to this requirement. If a platform wants to participate in Google's program for fresh user-generated content, it must already use or be prepared to implement valid schema.org markup on its pages. It must also have secure OAuth 2.0 authentication and the ability to construct rigorously validated JSON-LD payloads. The program has additional content, volume, and accessibility requirements, and does not guarantee that content will be displayed.
References
- 關於使用者原創內容最新資料計畫 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Discusses: Are platforms that operate forums required to adopt schema.org?
- 評論摘錄 (Review、AggregateRating) 結構化資料 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Source used in the article above.
- 資料集結構化資料 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Source used in the article above.
- 如何新增商家資訊結構化資料 | Google 搜尋中心 | Documentation | Google for Developersdevelopers.google.com — Source used in the article above.
- 超越傳統SEO:我投資生成式引擎優化(GEO)的商業決策tenten.co · 2025-10-14T02:54:30.000Z — Discusses: Is it worth implementing schema.org specifically to gain more citations in AI search?
- Ahrefs’ Study Of 2 Million Featured Snippets: 10 Important Takeawaysahrefs.com · 2017-05-30T03:17:29+00:00 — Discusses: Can implementing markup improve the chances of appearing in Google featured snippets?
- Why Data Integrity Is The New Technical SEO: From Crawling To Trustwww.searchenginejournal.com · 2026-07-28T14:30:34+00:00 — Source used in the article above.
- Should we follow the schema.org paths?webmasters.stackexchange.com — Source used in the article above.
- Schema, LLMs & The Low Bar For ‘Evidence’ In GEOwww.searchenginejournal.com · 2026-06-16T11:00:57+00:00 — Discusses: If AI can extract information from markup, does that mean it understands schema.org semantics?
- Google AI 優化指南正式上線:官方親口宣告 AEO 與 GEO 終究還是 SEOtenten.co · 2026-05-17T04:53:00.000Z — Discusses: Is it worth implementing schema.org specifically to gain more citations in AI search?
