Implementing Schema involves more than adding code to a webpage. Challenges include choosing the right markup types, handling properties and nesting, and coordinating development and validation. To improve the process, first identify the content type and website environment, then decide whether to use a generator, a plugin, or custom code. Do not assume one method works for every website. The experiences with tools cited below come from a 2020 discussion and do not guarantee that those tools and approaches are still suitable today.
Choose the right markup types first—more markup is not necessarily better
Semrush recommends prioritizing types relevant to the content, such as Organization, Product, Article, Event, Recipe, or Review. Article and product pages need to describe different information. A tool offering the same template for both is no reason to overlook those differences.
Having more types available does not necessarily make the work easier. In a 2020 Semrush discussion, Tallwave said that more types could meet the needs of different websites but also meant more things to consider, implement, and test. Martha van Berkel noted that the trade-offs depend on a team’s tools, knowledge, and time available for learning and testing.
- Identify the page’s main content before choosing relevant types.
- Review the properties available for each type rather than treating the fields shown by a plugin as the complete set of options.
- Include testing time in the assessment instead of counting only the time needed to generate code.
Tools can reduce manual coding, but the data still needs judgment
In the same 2020 discussion, Jason Barnard described writing markup by hand as slow and error-prone. Hamlet Batista identified challenges including nesting elements correctly, choosing property values, and handling requested property information that was not displayed on the page. These were practical difficulties raised by participants, not an indication that every type has the same required properties.
For hand-coded websites, Batista suggested trying JSON-LD. He felt it “should be easy to use,” but that was not a guarantee that it would be easy to use with every website architecture. Semrush also recommends using a markup generator and then validating the implementation with Google’s Rich Results Test. Tools can reduce manual coding, but you still need to judge whether the types and property values are appropriate.
In 2020, Matthew Silva also advised looking beyond the fields shown in a plugin’s interface and reviewing the full set of properties for relevant types. The point is not to abandon plugins altogether, but to avoid letting tools limit your understanding of the markup.
Explain the benefits to clients and the requirements to developers
Participants in the 2020 discussion, James Leisy and Alexis Huddart, both mentioned communication barriers: explaining Schema to clients and asking developers to implement or automate it are not always easy. Simply handing over a piece of code does not resolve these collaboration challenges.
When explaining the benefits, be clear about the limitations. Semrush states that Schema helps search systems understand content but is not a direct ranking factor. Rich results may improve click-through rates, but that outcome is not guaranteed. Implementation discussions should therefore focus on what information to describe, which approach to use, and how to validate it, rather than promising that adding markup will improve rankings.
Schema implementation: perspectives from across the web
What implementation options are available for websites using Craft?
If a website uses Craft, a dedicated plugin is an option worth evaluating. A 2020 discussion recommended nystudio107's Schema plugin, suggesting that it could reduce tedious setup and maintenance work. However, this was a user opinion at the time and does not mean the plugin is still suitable for every Craft environment. Whether to adopt it still depends on an assessment of the website's environment.
Can HTML5 semantic tags replace Schema?
There is no blanket answer. In 2020, Hamlet Batista pointed out that HTML5 semantic tags overlap with some Schema markup, such as article and Schema.org's Article, and suggested that semantic tags might be used where appropriate. This was a conditional recommendation, not sufficient evidence that the two have identical functionality or are fully interchangeable.
Why do some people want Schema.org to provide more implementation examples?
Implementers need complete examples to make it easier to understand how to apply markup for different types. In a 2020 discussion, Bill Slawski suggested that Schema.org might increase adoption by providing more of these examples. However, increased adoption was his prediction; the available material provided no data demonstrating that effect.
References
- The technical SEO checklist for search engines and AI searchwww.semrush.com · 2024-09-18T14:13:00Z — Source used in the article above.
- How to Improve Your SEO by Using Schema Markupwww.semrush.com · 2020-02-10T19:20:00Z — Discusses: What implementation options are available for websites using Craft?; Can HTML5 semantic tags replace Schema?

