No structured data on the page: how to add schema markup in WordPress
No structured data means the page has no JSON-LD block describing what it is, such as an Article, Product, Recipe or Organization. Adding one makes the page eligible for rich results in Google, like breadcrumb trails, product prices and recipe cards, and gives machines a clear, labeled summary of the page.
It is an optimization, not an error. Structured data is not a ranking factor on its own, and many pages never get a rich result even with perfect markup. But it is cheap to add, and for types Google supports, it changes how your listing can look.
What it looks like in the HTML
After
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Cold Brew at Home: A Beginner's Guide",
"datePublished": "2026-09-01",
"author": { "@type": "Person", "name": "Priya Rao" }
}
</script>
Why it matters
Google uses structured data to decide whether a page qualifies for enhanced results: star ratings on products and recipes, prices and availability, event dates, breadcrumbs in place of a raw URL. A richer listing takes more space and gives searchers more reasons to click, which is where the benefit comes from.
Structured data also identifies who is behind a site. Organization markup with a logo and sameAs links to your social profiles helps search engines connect your site to your brand elsewhere. For the types and what each one does, see the schema markup guide.
Be realistic about what it will do. Google decides per query whether to show a rich result, and some types, notably FAQ and HowTo, are now shown rarely.
Why WordPress pages often have none
WordPress core outputs no structured data. Unless your theme or a plugin adds it, pages have none. Some themes add microdata attributes to their HTML instead of JSON-LD; Google can read microdata, but this audit looks only for JSON-LD blocks.
It also disappears when you deactivate an SEO plugin that was providing it, or when a performance plugin that combines or delays scripts mangles ld+json blocks.
How to fix it in WordPress
- Decide which type fits the page. Posts are usually Article or BlogPosting; products, Product; a local business homepage, LocalBusiness; recipes, Recipe. Only mark up what is actually on the page.
- Set site-wide defaults in Hydrogen SEO. On the Schema screen in the Hydrogen SEO menu, choose which types apply to which post types. Set Article for posts once, and every post carries it. Fields accept smart tags such as
%title%and%author%, so the values are correct on each page. - Handle exceptions per page. Open the page, press Ctrl+E or Cmd+E for the SEO Settings sheet, and pick a schema type and its fields, for example Product on a pricing page or FAQ on a support page with genuine questions and answers.
- Fill in your Organization details on the Schema screen, and your social profiles on the Social screen; they are merged into the Organization's
sameAslist. - Avoid duplicates. If your theme or another plugin also prints schema, you can end up with two conflicting Article blocks. Keep one source.
With a connected account, AI-assisted schema can draft business structured data from a plain-language description. Everything else here works with no account.
How to check the fix
View the page source and search for application/ld+json. Then test the live URL in Google's Rich Results Test, which shows which rich result types the page is eligible for, and the Schema.org validator at validator.schema.org, which checks the markup itself. Fix errors; fix warnings only when you have the real data. Over time, Search Console's enhancement reports show how Google reads markup across the whole site.
Common questions
Does schema markup improve rankings?
Not directly. Google has said structured data is not a ranking factor on its own. It makes pages eligible for rich results, which can improve click-through rate.
Which schema type should a blog post use?
Article or BlogPosting is the usual choice, with headline, author and dates. Add BreadcrumbList if your site shows breadcrumbs.
Is JSON-LD better than microdata?
Google supports both, and recommends JSON-LD because it is easier to add and maintain without touching the visible HTML.
Will adding schema guarantee a rich result?
No. Valid markup makes a page eligible; Google decides per query whether to show the enhanced result.