Schema markup, in plain English.
Schema markup is structured code you add to your website so search engines understand what your content means — not just what it says. Here's what it does and why it matters.
Schema markup is structured data you add to a web page so search engines can read the meaning of your content, not just the words.
Google can crawl text. What it struggles with is context. A page might mention a name, a date, and a price — but without schema, Google is guessing whether that's a job listing, a product, or a law firm's fee schedule. Schema removes the guessing. It tells Google exactly what each piece of information is.
What schema markup actually is
Schema markup is code — usually in a format called JSON-LD — that sits in the <head> or body of a web page and describes the content to machines.
The code follows a shared vocabulary from Schema.org, a project maintained by Google, Bing, Yahoo, and Yandex. Every type of content has a defined format. A recipe has ingredients, cook time, and a rating. A local business has an address, phone number, and opening hours. A legal service has a practitioner name, jurisdiction, and service type.
When Google reads your page, it reads two things: the visible content, and the structured data underneath. The structured data is what makes rich results possible — those star ratings, FAQs, and event details you see in search results before you click anything.
JSON-LD is the format Google recommends. It looks like this in practice: a <script> block with a type of application/ld+json, containing a structured object with @context, @type, and then the relevant properties. You do not need to know how to write it from scratch. You need to understand what it does and why it belongs on every professional services site.
Why schema matters for search visibility
Schema markup increases the chance that Google shows your content in a richer format — and richer formats get more clicks.
A plain blue link gets a certain click-through rate. That same link with a star rating, a review count, and a FAQ dropdown gets a higher one. The page hasn't changed. The content hasn't changed. The only difference is that Google now understands the content well enough to display it better.
For professional services — law firms, accountants, consultancies, medical practices — schema matters for a second reason. These are fields where Google applies heightened scrutiny under its quality guidelines. Demonstrating that your content is authored by a real person, affiliated with a real organisation, at a real address, with real credentials, is not optional. Schema is one of the clearest signals you can send.
A review schema on a testimonials page. An organisation schema on your about page. A person schema on your team pages. A FAQ schema on your service pages. Each one adds a layer of machine-readable credibility that Google can act on.
The types of schema that actually move the needle
For most professional services sites, six schema types do the work.
LocalBusiness (or its subtypes — LegalService, AccountingService, MedicalBusiness) tells Google who you are, where you are, and what you do. This is the foundation. Without it, your Google Business Profile and your website are not clearly linked in Google's understanding.
Person schema on team or bio pages establishes individual expertise. Name, job title, employer, and credentials. This feeds directly into how Google evaluates authoritativeness — the kind that matters in regulated sectors.
FAQPage schema on service pages can generate FAQ dropdowns directly in search results. Users see your answers before they click. That can mean fewer clicks from unqualified visitors and more from people who already know what they need.
Review and AggregateRating schema surfaces your rating in results. You need legitimate reviews — on Google, on Trustpilot, or elsewhere — and then you need the markup to reference them correctly.
Article or BlogPosting schema on content pages tells Google when the piece was written, who wrote it, and what organisation published it. This is not vanity. Google uses this to assess content freshness and source credibility.
BreadcrumbList schema helps Google display the path to a page in search results — Home > Services > Commercial Law, for example. It is a small thing that improves how users read results before they click.
How to implement schema without a developer
You do not need to write JSON-LD by hand. Several tools generate it for you.
Google's Structured Data Markup Helper lets you highlight elements on a page and tag them. It outputs the JSON-LD you need. Merkle's Schema Markup Generator does the same with a cleaner interface. Both are free.
Once generated, the code goes into the <head> of the page — or if you use a CMS like WordPress, into a plugin like Rank Math or Yoast, both of which have schema settings built in. Shopify and Squarespace handle some schema automatically, though they rarely get it right for professional services without customisation.
After implementing, validate with Google's Rich Results Test. Paste the page URL or the code directly. It will tell you what schema it found, whether it's valid, and whether it's eligible for rich results. This takes two minutes. Run it every time you make a change.
One common mistake: marking up content that isn't visible on the page. If your schema says you have 47 five-star reviews but your page shows none of them, Google treats that as manipulative. Schema must describe what users can actually see.
Schema for professional services — a practical example
A law firm is a clear case. The site needs schema, and the stakes of getting it wrong are real — both for search performance and for the credibility signals Google weighs in your category.
At the top level: a LegalService schema on the homepage with the firm name, address, phone number, jurisdiction, and areas of practice. On each practice area page: a Service schema describing what the service is and who provides it. On solicitor profile pages: Person schema with name, role, and the firm as employer. On the blog: Article schema with author and publication date. On the contact page: the same LocalService schema reinforced, plus opening hours.
This is exactly the kind of structured foundation that the McShanes Solicitors work addressed — a firm with strong local reputation but thin machine-readable signals that made it harder for Google to represent them accurately in search results.
The fix was not a content rewrite. It was getting the structural layer right first.
What schema doesn't do
Schema does not guarantee rich results. Google chooses when to display them. Eligibility is not the same as certainty.
Schema does not fix a slow, poorly structured, or thin site. If your pages take four seconds to load, no amount of structured data compensates for that. If you want to understand how speed interacts with visibility, Core Web Vitals: the three numbers that decide if Google bothers covers that ground directly.
Schema does not rank you for keywords you haven't earned the right to rank for. It helps Google understand what you have. It does not create what you don't.
And schema is not a one-time task. When you add services, hire staff, change your address, or update your hours, the schema needs to match. Stale schema is sometimes worse than no schema — it sends conflicting signals.
Where this fits in a broader search strategy
Schema markup belongs to the structural layer of search — the things that have to be right before content and links can do their full work. Getting the structure right is the foundation. Everything built on a weak foundation costs more to fix later.
At the boring digital co., we treat technical foundations as the starting point, not the finish line. Search Foundations covers what this layer looks like in practice — including schema, site speed, crawlability, and the signals that tell Google your site is trustworthy before a single user clicks.
For professional services firms especially, these signals carry more weight than in most sectors. Google applies its quality guidelines differently to legal, financial, and medical content. The structural signals — schema included — are part of how you demonstrate that your site deserves to rank.
If your site is slow as well as poorly marked up, the problems compound. Why your slow site is a sales problem, not an IT problem explains why performance and structure belong in the same conversation.
Schema markup is not a silver bullet. It is one component of a site that Google can read, trust, and represent accurately. Get it right, keep it current, and it does its job without drama — which is exactly what good technical SEO should do.
Things readers usually ask.
- Does schema markup directly improve my Google rankings?
- Schema markup does not directly change your ranking position. It helps Google understand your content more accurately, which can lead to richer search result formats that improve click-through rates.
- What format should I use for schema markup?
- Use JSON-LD. Google recommends it, it's the easiest to implement without touching your page's visible HTML, and it's what most CMS plugins and schema generators produce by default.
- How do I check if my schema markup is working?
- Use Google's Rich Results Test — paste your page URL and it will show what structured data Google found and whether it's valid. Run it after every implementation or change.
- Do I need schema on every page of my site?
- No. Focus on the pages that carry the most weight: your homepage, service or practice area pages, team bio pages, and any blog content you want attributed to a named author. Start there and expand.
- Can schema markup hurt my site if I get it wrong?
- Incorrect schema rarely causes penalties on its own, but marking up content that isn't visible to users — inflated review counts, for example — can be treated as manipulative. Keep your structured data consistent with what users actually see on the page.
Want us to look at your site?
A 20-minute call. No pitch. We'll tell you what we'd fix first.
CONTACT US →