Structured Data / JSON-LD
Why Structured Data Is Needed
Structured data is markup that packages the standard vocabulary defined by schema.org in a machine-readable format so search engines can understand exactly what a page means. Google Search Central’s documentation defines it as “a standardized format for providing information about a page and classifying the page content.” Google (official) Crawlers can read HTML text, but they can’t be sure of its meaning the way people can. Whether “STUDIO-JT” on a page is a company name, a person’s name or a project title can be ambiguous from context alone. Structured data states this information clearly in a machine-readable format, leaving less room for misinterpretation.
Pages with structured data become eligible to appear on the SERP as rich results, such as star ratings, prices and breadcrumbs. In case studies Google has shared, Rotten Tomatoes saw a 25% higher click-through rate on pages with structured data, and Nestlé saw an 82% higher click-through rate on pages shown as rich results. Google case studies
The schema.org Vocabulary and How to Write JSON-LD
schema.org is a standard vocabulary developed jointly by Google, Microsoft (Bing), Yahoo and Yandex, defining more than 800 types such as Organization, Article, Product and LocalBusiness. Google Search Central’s documentation says most structured data for search uses the schema.org vocabulary, but it explicitly tells you to check how things actually work in Google Search against Google’s own documentation, not schema.org’s. Google (official)
There are three formats: JSON-LD, Microdata and RDFa. Google Search Central’s documentation recommends JSON-LD “if your site’s setup allows it,” because it is the easiest format to implement and maintain at scale. Google (official) JSON-LD is a standard format finalized by the W3C as a Recommendation (JSON-LD 1.1) in July 2020. W3C (standard) Unlike the other formats, which weave attributes into HTML tags, it keeps all the data together in a single script tag. Here is an Organization example that declares company information.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.example.co.kr/#organization",
"name": "Example Web Agency",
"url": "https://www.example.co.kr/",
"logo": "https://www.example.co.kr/assets/logo.png",
"description": "A web agency specializing in custom WordPress themes",
"sameAs": [
"https://www.instagram.com/example",
"https://www.linkedin.com/company/example"
]
}
</script>
For a custom WordPress theme, the standard approach is to output this script on the wp_head hook. Adding an @id lets other schemas such as Article or WebPage reference this entity in their publisher field, connecting the whole site into a single graph. Google’s Organization documentation says properties such as url and sameAs help uniquely identify the organization, and sameAs can list multiple URLs. Google (official)
Rich Results Are Not Guaranteed
Adding structured data doesn’t guarantee rich results. Google Search Central’s documentation states explicitly that structured data makes rich results possible but does not guarantee they will be shown. Google (official)
There is a real example. In August 2023, Google announced on the Search Central Blog that it would limit FAQ rich results to well-known, authoritative government and health websites and reduce HowTo rich results to desktop only. In September of the same year, it stopped showing HowTo on desktop too, effectively retiring it. Google Blog The same post added that there’s no need to remove leftover markup, but unused structured data has no visible effect in search.
The relationship to rankings is also clear. In 2019, Google’s John Mueller said structured data helps Google understand the entities on a page but is not a ranking factor. Having structured data doesn’t mean Google will show the page to more users or rank it higher. John Mueller (Google) Google’s general structured data guidelines also separate the two areas: a manual action for a policy violation only makes you lose eligibility for rich results and does not affect web search rankings. Google (official)
Structured Data in the Age of AI Search
Google has also documented its position on AI search features. Google’s AI features documentation says there are no additional requirements or special optimizations for appearing in AI Overviews or AI Mode, and no special schema.org structured data you need to add for AI. Google (official) Instead, it lists “making sure structured data matches the visible text on the page” as one of the existing SEO best practices. From a GEO perspective as well, sticking to this basic is the approach that fits the official documentation, rather than inventing new markup.
Practical Checkpoints from a Builder’s Perspective
When you build the site yourself, accidents happen less in the schema declarations and more in the output path and validation. The items below follow the recommendations in Google’s official documentation.
- Match the visible content – Google’s general structured data guidelines state, “Don’t mark up content that is not visible to readers of the page.” Google (official) Putting star ratings or prices in the schema that aren’t on the page can lead to a manual action.
- Always use a validator – Google’s Organization documentation recommends validating your code with the Rich Results Test and fixing any critical errors. Google (official) A single comma can cause the whole block to be ignored, so run it through a validator instead of eyeballing it, and after launch, use the URL Inspection tool in Search Console to see how Google views the page.
- Logo requirements – Per Google’s Organization documentation, the logo image must be at least 112x112px, the image URL must be crawlable and indexable, and the file must be in a format supported by Google Images. Google (official)
- No self-serving review markup – Google’s review snippet documentation states that when the entity being reviewed controls the reviews about itself, Organization-type pages, including LocalBusiness, lose eligibility for star ratings. Google (official)
- Check for duplicate output – If an SEO plugin already outputs Organization and the theme outputs it again, you end up with two conflicting sets of schema. Count the ld+json blocks in the page source yourself, then disable one side or merge them into one.
- Don’t invest anew in retired rich results – For ordinary sites, FAQ and HowTo rich results are no longer shown. According to Google’s blog, leftover markup won’t cause problems, but it has no visible effect either. Google Blog
Further Reading
References
- Introduction to structured data markup in Google Search – Google Search Central
- General structured data guidelines – Google Search Central
- Organization structured data – Google Search Central
- Review snippet structured data – Google Search Central
- Changes to HowTo and FAQ rich results – Google Search Central Blog
- AI features and your website – Google Search Central
- JSON-LD 1.1 (W3C Recommendation) – W3C
- John Mueller Answers About Structured Data and Rankings – Search Engine Journal
Jul.2026By Studio JT