Schema markup for service businesses: a checklist that goes beyond Organization

What most sites ship

A single Organization JSON-LD block with name, URL, and logo. That is a fine start, but it is thin. It tells a machine your business exists without describing what you actually do, which services you offer, or how the pages on your site relate to each other. For a multi-service studio, that gap matters. A search engine or an AI assistant reading a bare Organization block has to guess at the rest, and guessing is where inaccurate descriptions come from.

Set expectations before you write a line of markup

The honest reason to add more schema in 2026 is not rich results. It is machine readability and entity clarity. A few years ago you could mark up FAQs and how-to steps and reasonably expect Google to draw a special result for them. That era is over for most sites. In August 2023 Google reduced FAQ rich results to a short list of well-known, authoritative government and health sites, and then removed FAQ rich results from Search entirely in May 2026. HowTo rich results were cut to desktop only in August 2023 and dropped on desktop about a month later, in September 2023, which ended them completely. Neither appears in Google's current gallery of supported rich results. So if you are adding schema hoping to earn a flashy SERP feature, most of the markup discussed here will not do that. What it will do is help Google and AI tools understand and describe your business correctly, which is the value worth chasing now.

What still earns a Google rich result

It is a short list, and knowing it keeps your effort grounded. The types that still produce rich results or knowledge-panel detail include Organization and LocalBusiness, Breadcrumb, Article, Review snippet, and Product. Google centers its business guidance on LocalBusiness, which is a subtype of Organization, and it asks you to use the most specific type that fits. For a studio with a real service area or address, LocalBusiness is the block that can still surface details in Search, including a knowledge panel. Breadcrumb markup still renders in results. Everything else below is scaffolding for understanding, not a ticket to a rich result, and it is worth being clear-eyed about which is which.

A fuller graph, and what each part is for

Use a single @graph that includes your business as Organization or LocalBusiness, a WebSite node, a WebPage node for the page itself, a BreadcrumbList, one Service node per offering, and a Person for the principal or author. The Organization and Breadcrumb nodes do real work in Search. The WebSite, WebPage, Service, and Person nodes are there for entity clarity: they let a machine stitch together who you are, what you sell, and who stands behind the work. Link the nodes by @id rather than by name. An @id reference is unambiguous; a name match is a guess. This is the single highest-leverage habit in the whole exercise, because it turns a pile of separate objects into one connected description of your business.

Service markup describes, it does not decorate

List one Service node per real offering and connect each to the provider with a provider reference that points at your Organization @id. Be candid about what this earns: Google has no dedicated Service rich result, so this markup will not put a special card in the SERP. Its job is to describe your offerings so a machine can answer the question of what you do without inferring it from marketing copy. That is genuinely useful for AI tools that summarize or cite your site, and it is honest to present it that way rather than implying a citation payoff that the markup does not deliver.

About FAQ, HowTo, and Speakable

If you already have FAQ markup on a page, leave it or remove it as you prefer. Google says unused structured data does not cause problems in Search, so leftover FAQPage markup is harmless. It simply earns nothing visible anymore. There is a quieter case for keeping well-structured questions and answers on the page: clear Q&A content helps language models comprehend and cite your pages even though the SERP feature is gone. That is a content decision, not a rich-result strategy, and it is fine to treat it that way. Skip HowTo markup as a rich-result play; those results are gone too. As for Speakable, do not add it as a general best practice. Per Google's documentation it is a beta feature limited to users in the United States with English-language Google Home or Assistant devices, and it is built for topical news queries, not service-business pages. For a studio site it is the wrong tool, and Google does not guarantee that features consuming structured data will appear at all.

Common mistakes that undermine the whole block

Stuffing marketing language into the description field. A machine reading that you craft transformative digital experiences learns nothing it can act on; a plain sentence describing the service does more. Inventing an aggregateRating with no real reviews behind it. That is the worst offender, because it is a fabricated claim sitting in structured data, and Google's structured data policies say marking up reviews or ratings that are not from actual users may trigger a manual action, on top of misleading anyone who reads it. Forgetting to link Service nodes to the parent Organization with a provider reference, which leaves your offerings floating unattached to the business that provides them. Each mistake makes the markup less trustworthy, and untrustworthy markup is worse than none.

The checklist

One: ship Organization or, better, LocalBusiness with accurate, factual details. Two: add WebSite, WebPage, and BreadcrumbList and link them by @id. Three: add one Service node per offering, each with a provider reference to your Organization. Four: add a Person node for the author or principal, with no invented name or credential. Five: keep every description plainspoken and true. Six: never fabricate a rating or a review. Seven: drop Speakable, and treat any leftover FAQ or HowTo markup as harmless but inert. Done well, this graph does not win you results that Google no longer hands out. It makes your business legible to the machines and AI tools that increasingly describe you to other people, which is the part you can actually control.

Sources

External sources are provided for verification. NavoTech is not affiliated with and does not endorse the organizations cited.

Written by the team at NavoTech Digital Solutions. Have a project or counter-example? Get in touch.