SEO & AEO

Schema Markup for SEO: How to Add It to a Service Website

A sandy seabed scattered with rocks and sea plantsA yellow seahorse holding on to an orange sea fanA spotted eagle ray over a reef seen from above

A visitor can glance at your home page and tell your business name from your phone number in about a second. Search engines like Google read that same page as text and code, so they have to work it out. Schema markup for SEO is a short block of code that labels those facts for them, using the shared vocabulary at schema.org.

You’ll come away able to choose the schema types a service business site needs, add them as JSON-LD on WordPress, Squarespace, or Wix, and test them before they go live.

How Schema Markup for SEO Works

Schema markup is code in a web page’s HTML that describes its content with schema.org types, such as Organization or Service. Google reads that code to understand what the page is about. Some types also make a page eligible for rich results, the search listings with extras like breadcrumbs or review stars. For background on search itself, see our posts on how SEO and AEO differ and how to rank in AI Overviews.

Google’s general structured data guidelines are clear that eligible doesn’t mean guaranteed. Even valid markup may never produce rich results if the algorithm decides a plain text listing suits a search better.

Types of Schema Markup a Service Business Needs

Plenty of schema.org types, like Recipe or JobPosting, have nothing to do with a plumber or an accountant. For a service business, the list of types of schema markup worth writing is short:

  • Organization, or the closest LocalBusiness subtype, on your home page or About page (Google says you don’t need it on every page).
  • Service on each service page, with the service name, a short description, the area you serve, and your business as the provider.
  • BreadcrumbList on pages that sit inside a section, like /services/drain-cleaning/.
  • Article on blog posts, with the author and the publish date.

For the business type, Google asks for the most specific LocalBusiness subtype that fits, such as Plumber, Electrician, or LegalService. A company with several trades can list an array like ["Electrician", "Plumber"]. Leave out ProfessionalService, a type schema.org deprecated after people kept confusing it with Service. Our post on Google Business Profile optimization covers keeping your name, address, and phone number identical everywhere they appear.

Example Schema Plan for a 40-Page Plumbing Site

Take an illustrative 12-person plumbing company with a 40-page site: a home page, About and Contact pages, eight service pages, four city pages, and 25 blog posts. Plumber markup on the home page plus a Service block on each of the 12 service and city pages makes 13 blocks to write by hand. An SEO plugin like Yoast can generate Article markup for the 25 posts and BreadcrumbList for the 37 pages that sit inside a section.

At about 15 minutes to write and test each one, those 13 hand-written blocks come to a little over three hours. On Wix, which allows five markups per page, a service page carrying Service and BreadcrumbList uses two of its five slots.

JSON-LD vs Microdata

Search engines read schema in three data formats: JSON-LD, Microdata, and RDFa. Google’s introduction to structured data says all three are equally fine as long as the markup is valid, and it points most sites to JSON-LD.

Microdata and RDFa both put attributes, like Microdata’s itemprop, on the HTML tags around your visible text. Rewrite a paragraph in the editor and you can break the markup woven into it without noticing.

JSON-LD schema markup sits in its own script block apart from the copy, which Google notes makes nested details easier to write, such as the country in a venue’s address. Google can still read JSON-LD that JavaScript or a CMS widget adds to the page, and it’s the format we use on service business sites.

How to Add Schema Markup to WordPress, Squarespace, and Wix

Each platform below needs a <script type="application/ld+json"> block in the page’s code, like this sample for a fictional plumber’s home page.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Plumber",
  "name": "Example Plumbing Co.",
  "url": "https://www.example.com/",
  "logo": "https://www.example.com/images/logo.png",
  "telephone": "+1-217-555-0142",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "100 Main St",
    "addressLocality": "Springfield",
    "addressRegion": "IL",
    "postalCode": "62701",
    "addressCountry": "US"
  },
  "areaServed": "Springfield, IL",
  "sameAs": ["https://www.linkedin.com/company/example-plumbing"]
}
</script>

Your own version needs the phone number’s country code and area code, plus a logo of at least 112 by 112 pixels.

WordPress

Before implementing schema markup by hand, check what your SEO plugin already writes. Yoast SEO, for example, outputs a JSON-LD graph with WebPage, WebSite, and Organization (or Person) entries on every page, so change anything it covers in the plugin’s settings.

In the WPCode plugin, choose + Add Snippet from the admin sidebar and paste your script in as HTML. New snippets default to the Site Wide Header location, which places the code in the head of every page. For a Service block, use the snippet’s conditional logic to limit it to that one page’s URL.

If you’re still choosing a platform, our comparison of Squarespace vs WordPress vs Wix covers how much SEO control each one gives you.

Squarespace

Squarespace includes code injection on its Core, Plus, and Advanced plans and on some legacy ones. For site-wide markup like your Organization block, open Pages, go to Website Tools, choose Code Injection, and paste the script into the Header field.

To add markup to a single page, hover over it in the Pages panel and open its settings. Click Advanced, paste the script into Page Header Code Injection, and save.

Wix

Wix accepts JSON-LD only, with up to five markups per page and fewer than 7,000 characters in each. Product pages from Wix Stores, along with Bookings services, blog posts, and event pages, come with preset markup that you edit in the site’s SEO Settings.

On a static page (dynamic pages are off limits), open its SEO settings and find Structured Data Markup. Click + Add New Markup, give it a name, paste your JSON-LD, and hit Apply. The menu beside each markup has a Test on Google option for a quick check.

FAQ Schema Markup After Google’s 2023 and 2026 Changes

FAQ schema markup used to put expandable questions under a search listing, a feature that Google’s Search Central documentation updates confirm is gone. Google stopped showing FAQ rich results in Search on May 7, 2026, and removed the documentation for them that June.

Back in August 2023, Google had already limited FAQ rich results to well-known, authoritative government and health websites. A plugin or an old guide that still promises FAQ dropdowns in Google is working from rules that no longer apply.

Schema Markup Validation with the Rich Results Test and Schema Markup Validator

These two schema markup tools answer different questions, so use both. Google’s Rich Results Test reports which Google rich result types it finds and flags errors in them. The Schema Markup Validator, which moved from Google to schema.org in 2021, checks syntax against the whole schema.org vocabulary and ignores Google features. Since August 2021, Google has redirected its old Structured Data Testing Tool to a landing page for choosing the right one.

  1. Before publishing, choose Code in the Rich Results Test, paste your script, and fix anything marked invalid.
  2. Run Service blocks, and anything else Google has no rich result for, through the Schema Markup Validator to spot misspelled properties.
  3. After publishing, test the live URL, which shows whether robots.txt or a noindex tag stops Google from crawling the page.
  4. Open URL Inspection in Google Search Console to confirm Googlebot found the markup, then request indexing.
  5. Once a month, check the rich result reports in Search Console, where each type of structured data Google finds, such as Breadcrumbs or Review snippets, has its own count of valid and invalid items.

Common Schema Mistakes That Block Rich Results

Run each block through this checklist before it goes live.

  • Every value in the markup also appears on the page, because Google’s guidelines say not to mark up content readers can’t see.
  • Required properties are filled in, such as name and address for LocalBusiness.
  • Star ratings describe someone else. Reviews of your own business, even through an embedded Google reviews widget, make the page ineligible for review stars.
  • Each block uses the most specific type that fits, and none uses ProfessionalService.
  • No comments sit inside the JSON-LD, since they aren’t part of the JSON-LD standard and can cause errors outside the Rich Results Test.
  • Googlebot can reach the page, with no robots.txt rule, noindex tag, or login in the way.
  • Image URLs in the markup, your logo included, can be crawled and indexed.
  • One Organization block describes your business, so a plugin and a hand-written script never disagree about your name or phone number.
  • After a redesign or a domain change, every URL in the markup points to the new site. Our checklist for when you update structured data after a migration covers the rest of that job.

Schema Markup for AI Search: What It Can and Can’t Do

Structured data isn’t required for Google’s generative AI features, according to the AI optimization guide Google published in May 2026. It lists “overfocusing on structured data” among the things you can ignore. In the same passage, Google still recommends it for SEO because it helps pages qualify for rich results.

Where schema does help is in stating your facts once, in a form software doesn’t have to interpret. Google says it uses structured data to learn about the world, companies included, and that organization schema markup helps it tell your company apart from others in search results. List your official profiles in sameAs, the way the sample above lists a LinkedIn page.

What schema can’t do is turn a thin page into one worth quoting. We write it for the uses Google documents and count anything other answer engines do with it as a bonus.

Tracking lives in Search Console, where Google’s guide points to the Generative AI performance report for how your pages show up in its AI features.

Frequently Asked Questions

Is Schema Markup a Ranking Factor?

Nothing in Google’s guide to its ranking systems mentions structured data. Its structured data guidelines also say that a manual action for bad markup removes rich result eligibility without changing how the page ranks in web search. What schema markup for SEO can change is how your listing looks, if the page qualifies for a rich result.

Where Do I Add Schema Markup on My Website?

Put each block on the page it describes, which is what Google’s guidelines ask for. Organization or LocalBusiness markup goes on your home page or About page, Service markup on each service page, and Article markup on each post. In the code itself, a JSON-LD script can sit in the page’s head or body.

How Do I Check the Schema Markup on a Website?

Paste the page’s URL into the Rich Results Test to see the Google rich result types it found, or into the Schema Markup Validator to see every schema.org item. For your own site, the rich result reports in Search Console show the valid and invalid items Google found.

What Does Schema Markup Look Like?

It’s a block of JSON inside a script tag with the type application/ld+json, like the 20-line sample above. Each line pairs a schema.org property, such as name or telephone, with a value from your page. Visitors never see it, because browsers don’t display the script.

Where to Start This Week

Pick your home page and write one Organization or LocalBusiness block from the facts already on it. Run it through both validators, publish it, and then move on to your busiest service page.

When you want a second pair of eyes on your markup, our SEO and AEO services are the place to start.