Adding Schema in WordPress Without a Bloated Plugin

Before you install a schema plugin, check whether you need one.

Your SEO plugin almost certainly outputs Article, Organization or Person, and BreadcrumbList already. For a blog, that's the complete useful set — and adding a second plugin on top produces duplicate, conflicting markup rather than better markup.

So this is a guide about doing less, mostly. Three approaches, when each makes sense, and how to check what Google is actually reading.

The short version

Option 1 — Your SEO plugin. Already installed, already outputting the essentials. Covers most sites entirely.

Option 2 — Manual JSON-LD in your child theme. Full control, no extra plugin, needs a little PHP comfort.

Option 3 — A dedicated schema plugin. Only when you need types your SEO plugin doesn't handle — Recipe, Course, Event, Job Posting, complex Product.

And know what's changed: Google retired FAQ rich results entirely on 7 May 2026, and HowTo rich results on desktop back in 2023. Those markup types no longer produce a search feature. The full picture.

Option 1 — Check what you already have

Open any blog post on your site, view source, and search for application/ld+json.

You'll almost certainly find a JSON-LD block your SEO plugin generated. Read it. On a typical Yoast or Rank Math install it contains an Article or BlogPosting, an Organization or Person, a WebPage, a WebSite, and a BreadcrumbList — usually connected in a @graph.

That's a complete, well-formed schema setup for a blog. Nothing to add.

What to configure rather than replace:

Your entity type. In your SEO plugin's settings, choose Organization or Person. On a personal-brand site, Person is usually correct — and it's the single most valuable schema decision you'll make, because it's how search engines resolve you as a recognisable entity rather than an anonymous byline.

Your sameAs profiles. Add your real LinkedIn, X, GitHub, or publisher profile URLs. This is what lets engines confirm the Person on your site is the same Person elsewhere. Why entity resolution matters.

Author attribution. Make sure posts are attributed to a real author profile, not a generic admin account.

Breadcrumbs. Enable them if your theme supports it — you get both the visible navigation and the BreadcrumbList markup.

Ten minutes of configuration beats any plugin you could add.

Option 2 — Manual JSON-LD

When you need something specific and don't want another plugin, add it directly in your child theme's functions.php:

add_action( 'wp_head', function() {
    if ( ! is_singular( 'post' ) ) {
        return;
    }

    $schema = [
        '@context'      => 'https://schema.org',
        '@type'         => 'Article',
        'headline'      => get_the_title(),
        'datePublished' => get_the_date( 'c' ),
        'dateModified'  => get_the_modified_date( 'c' ),
        'author'        => [
            '@type' => 'Person',
            'name'  => get_the_author(),
            'url'   => get_author_posts_url( get_the_author_meta( 'ID' ) ),
        ],
        'mainEntityOfPage' => get_permalink(),
    ];

    echo '<script type="application/ld+json">'
       . wp_json_encode( $schema, JSON_UNESCAPED_SLASHES | JSON_UNESCAPED_UNICODE )
       . '</script>';
});

Three things worth noting about that code:

wp_json_encode rather than json_encode — it handles WordPress's character encoding properly.

get_the_date('c') produces ISO 8601 format, which is what schema.org expects.

The is_singular check means it only fires on single posts, not archives or pages.

The critical caveat: if your SEO plugin already outputs Article schema, this creates a duplicate. Either disable your plugin's Article output first, or use this approach only for types your plugin doesn't handle.

Always use a child theme. Code in a parent theme's functions.php disappears at the next theme update.

Option 3 — A dedicated schema plugin

Justified when you need types your SEO plugin doesn't cover: Recipe, Course, Event, Job Posting, Software Application, or complex Product markup beyond what WooCommerce provides.

If you go this route:

Disable the overlapping output in your SEO plugin first. Two plugins both emitting Article schema is worse than either alone.

Check what it actually adds to your page weight and admin load. Some schema plugins are substantially heavier than the value they deliver. How to measure.

Verify the output, don't assume it. Plenty of schema plugins produce technically valid markup that doesn't match the visible page — which is a guidelines violation.

Validating what Google actually reads

Two tools, and use both, because they answer different questions.

Google's Rich Results Test tells you which rich results your page is eligible for. Paste your URL, and it reports what Google detected and any errors. Note that its FAQ support was removed in June 2026 following the retirement, so it won't report on FAQPage at all now.

Schema.org's validator checks whether your markup is structurally valid regardless of whether Google surfaces a feature for it. Increasingly the more useful of the two, precisely because Google keeps retiring features while the markup itself remains valid and parseable.

Then check Search Console under Enhancements a few weeks later for anything Google flags at scale.

And view source manually. Search for application/ld+json and count the blocks. More than one is worth investigating — it usually means two plugins are both outputting, which is the most common schema problem on WordPress and completely invisible unless you look.

The mistake that causes real problems

Schema that doesn't match the visible page.

An author credited in markup who doesn't appear on the page. A dateModified that updates on a cron schedule while the content sits untouched. Review markup for reviews nobody can see. Product markup on a page that isn't a product.

This is a guidelines violation, it can trigger manual actions, and it's almost always the product of an automated plugin rather than deliberate deception.

The habit that prevents it: whenever you change something visible, change the markup in the same edit. Drift between the two is where long-term schema problems come from.

What about AI citations?

Modest help, not magic.

Google's own guidance says no special schema is needed for AI Overviews or AI Mode, though structured data you do use should match visible page content.

The mechanism that plausibly matters is parsing — structured data removes ambiguity about what a page is, who wrote it, and when it was updated. Models cite what they can parse confidently.

But read the correlation carefully: sites with clean schema tend to be technically competent, well-maintained sites, and those independently predict citation. Schema is probably doing some direct work and probably also standing in for general quality.

Since it costs almost nothing, do it. Just don't expect markup to rescue a page that buries its answer three screens down.

Frequently asked questions

Does my SEO plugin already add schema?
Almost certainly. Yoast, Rank Math, SEOPress, and All in One SEO all output Article or BlogPosting, Organization or Person, WebPage, and BreadcrumbList by default, usually connected in a @graph. Check by viewing your page source and searching for application/ld+json. For a typical blog that's the complete useful set, and adding a schema plugin on top produces duplicate markup rather than better markup.

Do I need a separate schema plugin?
Only for types your SEO plugin doesn't handle — Recipe, Course, Event, Job Posting, or complex Product markup. For a standard blog or business site, your SEO plugin covers everything that produces a search feature. If you do add one, disable the overlapping output in your SEO plugin first, since two plugins emitting Article schema is worse than either alone.

How do I test my schema?
Use Google's Rich Results Test for eligibility and the Schema.org validator for structural validity — they answer different questions, and the second is increasingly more useful since Google keeps retiring features while the markup stays valid. Also view your page source and count the application/ld+json blocks: more than one usually means two plugins are both outputting, which is the most common WordPress schema problem and invisible unless you look.

What to do next

View source on one of your blog posts and search for application/ld+json.

Read what's there. Two things to check: is your entity type set to Person rather than a generic Organization (on a personal-brand site, it should be), and does it include real sameAs profile URLs?

For most WordPress sites the answer to the second is no — and adding them is the highest-value schema change available, in about ten minutes, with no new plugin.

Free: The WordPress maintenance checklist.

---

Related guides

• Schema markup for blogs — what still earns rich results
• WordPress SEO: setup, settings and the traps — configuring your plugin
• Yoast vs Rank Math vs SEOPress — schema handling compared
• Entity SEO — what Person schema is doing for you