Technical SEO Schema: What It Is and How to Add It (JSON-LD Guide)

I ignored schema for the first year I ran this site. It looked like a setting for e-commerce stores and recipe blogs, and I had bigger problems to fix. When I finally tested my pages properly, I found my theme and my SEO plugin were both outputting their own markup, and the two copies were fighting each other.

That’s the thing about technical SEO schema. It’s invisible on the page, easy to get wrong, and most guides either bury you in code or oversell what it does.

This guide is the version I wish I’d had. It covers what schema is, where it fits in technical SEO, whether it actually helps, how JSON-LD works, which free tools to use, and how to check that it’s working. It also covers one important change: Google has now retired FAQ rich results entirely, so a lot of older advice no longer applies.

What Is Technical SEO Schema?

Technical SEO schema is structured data you add to a page’s code so search engines can tell exactly what the content is. Instead of guessing that a block of text is an author name, a publish date or a breadcrumb trail, the engine reads it from labeled markup.

The vocabulary comes from Schema.org, a shared standard used by Google, Bing and other engines. The code itself is usually written in JSON-LD, a small block of structured text that sits in the page’s HTML and is never shown to visitors.

If you’re newer to the wider field, here’s the short version of what technical SEO covers. It’s everything that affects whether search engines can crawl, render, index, and understand your site, as opposed to what the content says or who links to it. Schema sits in the “understand” part. I covered the crawl and index side in my post on technical SEO mistakes that hurt rankings even on a fast website.

Is Schema Markup On-Page SEO or Technical SEO?

Both, depending on who you ask, and the honest answer is that the label matters less than the job it does.

The case for on-page: schema describes content that’s on the page, and it lives in the page’s HTML. The case for technical: it’s code, it’s invisible to readers, and it needs testing and validation like any other technical element.

Most SEO professionals file it under technical SEO, because the work involved is technical. You’re writing or generating code, checking it for errors, and monitoring it in Search Console. But the rule that connects both sides is simple: the markup must match what’s actually visible on the page. If your schema says something the reader can’t see, you’re doing it wrong, whichever category you put it in.

Does Schema Help With SEO?

Not directly. Schema isn’t a ranking factor, and Google says structured data makes a page eligible for certain search features rather than boosting its position.

What schema can do is change how your result looks and help machines understand your page more reliably. That’s useful, but it’s a supporting role. A page that isn’t ranking won’t start ranking because you added markup. If that’s your problem, the fix is almost always content, targeting, or crawlability, which I walked through in why my blog wasn’t ranking, using real Search Console data.

The part that has changed recently is which features you can still earn. Here’s where things stand:

FAQ rich results are gone. Google restricted them to a small group of government and health sites in August 2023, then stopped showing them entirely on May 7, 2026. It’s also removing the FAQ report from Search Console and FAQ support from the Rich Results Test. Google’s guidance is that leaving valid FAQ markup in place does no harm, but it no longer produces the dropdown in results.

HowTo rich results were removed earlier. If an older tutorial tells you to add HowTo schema to win extra space in search, it’s out of date.

Other types still earn their place. Article and BlogPosting markup, breadcrumbs, organization details, product and review markup, and several others remain supported. Always check Google’s structured data documentation for the current list, because it changes more often than most SEO guides do.

What about AI search? Some people claim schema is the secret to being cited by AI answers. I haven’t seen solid evidence that it is, and Google hasn’t said it’s required. What I’m comfortable saying is that clean, accurate markup helps any system read your page correctly, and that’s reason enough to do it properly.

What Is JSON-LD Schema?

JSON-LD stands for JavaScript Object Notation for Linked Data. In practice, it’s a block of text in your page’s HTML that lists facts about the page in a structured way.

Google recommends JSON-LD over the older formats, Microdata and RDFa, which mix the labels directly into your visible HTML. JSON-LD keeps everything in one separate block, which makes it much easier to add, edit, and debug.

Here’s a simple example for a blog post:

html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Technical SEO Schema: What It Is and How to Add It",
  "author": {
    "@type": "Person",
    "name": "Your Author Name"
  },
  "datePublished": "2026-10-19",
  "dateModified": "2026-10-19",
  "image": "https://yoursite.com/wp-content/uploads/featured-image.webp",
  "publisher": {
    "@type": "Organization",
    "name": "Blogging Magazine",
    "logo": {
      "@type": "ImageObject",
      "url": "https://yoursite.com/logo.png"
    }
  }
}
</script>

You don’t need to memorize this. The key parts are @context, which points to Schema.org, and@type, which says what kind of thing you’re describing. Everything else is a property of that type, like the headline, author, or date.

One detail that catches people out: the author name should be a real name. If your WordPress byline says “Admin,” that generic name flows straight into your markup, which does nothing for readers or for machines trying to work out who wrote the page.

Which Schema Types Does a Blog Actually Need?

You don’t need dozens. A content site like this one needs a short list.

BlogPosting or Article goes on every post. It tells search engines the headline, author, dates, and image. For a personal blog, I stick with BlogPosting instead of NewsArticle, because news markup is meant for actual news publishers.

Organization or Person describes who’s behind the site, usually set once for the whole site rather than on every post.

BreadcrumbList describes the path from your homepage to the current page. It can replace the raw URL in your search result with a cleaner trail.

WebSite is a sitewide type, often set up once by your SEO plugin.

That’s the core set. Product, Review, LocalBusiness and the rest matter if you actually sell products, collect reviews or run a local business. Don’t add a type just because it exists. Markup for content that isn’t on the page can make things worse, not better.

How to Add Schema to a WordPress Blog

There are two realistic routes, and for most bloggers the first one is enough.

Can I Add Schema With a Plugin?

Yes, and it’s the route I use. Rank Math applies Article markup to posts by default and has a Schema tab for each post where you can check or change the type. Because it fills in the headline, author, dates, and featured image from data already on the post, there’s very little to do by hand.

I walked through every setting I use, including the checks I do before each post goes live, in my Rank Math schema guide. If you haven’t configured the plugin’s base settings yet, start with my Rank Math settings guide first, because schema builds on it.

If you’re still choosing between plugins, my Rank Math vs Yoast comparison covers how each one handles schema.

How Do I Add JSON-LD Manually?

If you want to add a custom block, like the example above, you can paste it into your page’s head or body using a header and footer snippets plugin, or through your theme’s custom code area. Replace every placeholder with your real details, and test the result before you leave it live.

Be careful here. If your SEO plugin already outputs Article markup for the post, adding another Article block by hand gives you a duplicate. Check what’s already on the page first.

Free Schema Generators for JSON-LD

If you’d rather not write JSON-LD by hand, a generator builds it from a form. The tools worth knowing:

Merkle’s Schema Markup Generator on TechnicalSEO.com. It’s free, outputs JSON-LD, and covers many common types. It’s the one that tends to show up first when people search for this topic.

Your SEO plugin’s built-in generator. Rank Math includes a schema generator with a good set of types on the free plan. If you’re on WordPress and already run it, this is the simplest option and needs no copy and paste.

A few tips, whichever tool you use. Generate only the types that match content on your page. Fill in every field the type requires, not just the ones that look interesting. And always run the output through a validator before you publish it.

Do I Need an FAQ Schema Generator?

For Google’s results, no. Since FAQ rich results have been retired, there’s no dropdown to win by generating FAQ markup. You can leave existing markup in place without penalty, but spending time creating new FAQ schema for Google’s sake is no longer worthwhile.

The FAQ section itself is still worth writing. Short, direct answers to real questions help readers, and they can still be picked up in snippets and in “People also ask” results. Keep the content, but don’t expect the markup to do anything visible in Google.

How to Check Schema in SEO

Never trust that schema works just because a plugin says it does. Three tools cover almost everything.

Google’s Rich Results Test. Paste in a live URL or code snippet, and it tells you whether the page is eligible for Google’s supported rich result types. It only tests types Google supports, so it won’t help you with every kind of markup.

The Schema Markup Validator at validator.schema.org. This checks whether your markup is valid against the Schema.org vocabulary, whether or not Google offers a rich result for it. It’s the right tool when you want to check syntax and structure.

Google Search Console. After your pages are live and crawled, the reports for supported structured data types show errors and warnings across your whole site. If you’re new to the tool, my Google Search Console guide for beginners shows where to look.

What’s the Difference Between Valid and Eligible?

Valid means the code is written correctly and can be parsed without errors. Eligible means the page also meets Google’s extra requirements to actually display a particular rich result. Code can be perfectly valid and still not produce anything visible in search, and that’s normal, not a sign something is broken.

Common Schema Mistakes to Avoid

Duplicate markup from theme and plugin. Some themes add their own schema independently of your SEO plugin. I found two competing Article blocks on my own pages this way. If a test shows the same type twice, a theme-and-plugin overlap is the usual cause.

Marking up content that isn’t on the page. Schema should describe what visitors can see. Hidden or invented details go against Google’s structured data guidelines.

Choosing the wrong type. A personal blog post carrying NewsArticle markup is a classic example. Pick the type that honestly matches the page.

Leaving outdated markup in place without a reason. Old HowTo and FAQ markup won’t hurt you, but there’s no benefit in building more of it.

Broken JSON. One missing comma or quote can invalidate the whole block. This is why you validate before publishing.

Missing required fields. Many types need specific properties, such as an image or a date. A missing one can disqualify the page from a feature.

Where Schema Fits in Your Technical SEO Checklist

Schema comes after the basics, not before them. If Google can’t crawl, render, or index a page, markup on that page does nothing. Before you spend an afternoon on structured data, make sure a stray noindex tag, a bad canonical, or a redirect chain isn’t hiding your content. My technical SEO mistakes post lists the ones I check first.

If you’re building your SEO foundation from scratch, my SEO roadmap for beginners puts schema in context with everything else, in the order I’d tackle it.

Final Thoughts

Technical SEO schema is worth doing right, but it’s a supporting actor. It helps search engines read your pages accurately and keeps you eligible for the rich results Google still offers. It won’t rescue a page that isn’t ranking, and it no longer gets you FAQ dropdowns.

Use a plugin for the standard types, add custom JSON-LD only when you have a real reason, and test everything before you publish. Then get back to the work that actually moves rankings.

Frequently Asked Questions