Why JSON-LD Is Cheap Insurance for Your Website

TL;DR

Structured data in JSON-LD format tells search engines and AI systems exactly what your business does, where it is, who runs it, and what makes it credible. Websites without it are invisible to the systems that now route most discovery traffic. The fix is not expensive or complex. It is a small block of code that most developers can add in minutes.

I spent three days last week auditing the websites of two hundred and fifty businesses on the Seattle Eastside. Acupuncturists, chiropractors, dentists, physical therapists, mental health counselors, med spas, urgent care clinics. The full spread of small professional practices that depend on local discovery.

The pattern was stark. One hundred and forty-seven of them had no structured data at all. That is 59 percent. Their websites looked fine. Many were professionally designed. But behind the scenes, they were speaking to Google in a language Google could not understand. And if Google cannot understand what you do, it cannot show you to people who are looking for exactly that.

This is not an SEO article. I am not going to talk about keyword density or backlink strategies. This is about a specific, cheap, durable fix that most businesses ignore because they do not know it exists. The fix is JSON-LD, and it matters more now than it ever has.

What JSON-LD Actually Does

JSON-LD stands for JavaScript Object Notation for Linked Data. It is a standardized format for telling machines what is on a web page in terms they can process without guessing. When a human reads a webpage, they see “Dr. Sarah Chen, Licensed Acupuncturist, Kirkland, WA.” When a machine reads the same page without structured data, it sees a bunch of text and has to infer what it means. With structured data, the machine sees a labeled, typed data structure: this is a person, this person has a medical license, this person practices at this address, here is the phone number, here are the hours.

That matters because Google does not rank websites by reading them like a human. It ranks them by understanding them as entities in a knowledge graph. The more clearly you describe your entity, the more confidently Google can match you to relevant searches. And the less clearly you describe it, the more you are trusting Google to guess correctly. Which it often does not.

The Search Visibility Difference

Research from 2024 shows that 72 percent of first-page Google results include some form of structured data markup. That is not a coincidence. Google uses structured data to generate rich results: the knowledge panels that appear on the right side of search results, the star ratings under local business listings, the event carousels, the FAQ dropdowns. These rich results take up more visual space on the results page and attract disproportionately more clicks.

One study from ClickForest estimates that pages with rich snippet enhancements see approximately 35 percent higher click-through rates than plain text listings. Another study, from Seer Interactive in late 2025, found that organic click-through rates dropped 61 percent for queries where Google displayed an AI Overview. The implication is clear: if you are not in the enhanced results, you are in the shrinking pool of plain blue links that fewer people click.

For local businesses, structured data is even more consequential. Google’s Local Pack, the map-and-listing block that appears for searches like “acupuncture near me,” draws its information from a combination of Google Business Profile data and structured data on your website. If the two sources disagree, Google gets confused. If your website has no structured data at all, Google has only the Business Profile to work with. And the Business Profile may not include your credentials, your services, your accepted insurance, or your specific areas of expertise.

The NAP Consistency Problem

NAP stands for Name, Address, Phone. It sounds trivial. It is not. Every directory listing, social profile, review site, and citation of your business has some version of your NAP. If your website says “Seattle Acupuncture & Wellness Center” but Yelp says “Seattle Acupuncture and Wellness Ctr,” and Google Business Profile says “Seattle Acupuncture,” you now have three entities in Google’s index that may or may not be the same business. Google handles uncertainty by downranking. It does not know which entity to trust, so it trusts none of them fully.

Structured data fixes this by anchoring your canonical NAP in the one place you control: your own website. When your LocalBusiness schema markup uses identical name, address, and phone fields, and those match your Google Business Profile exactly, you train Google to see one entity with one source of truth. The consistency itself becomes a ranking signal.

This is particularly important for healthcare practices. A patient searching for a specific treatment is not just looking for anyone nearby. They are looking for someone credentialed, experienced, and accessible. If your website lists your NCCAOM certification, your years in practice, your specialty areas, and your accepted insurance, but none of that is in structured data, Google has to extract it from plain text. And plain text extraction is error-prone. Your credentials might get missed entirely.

AI Systems Are Now Reading Your Site Too

Search is no longer just Google. In 2025 and 2026, a growing fraction of discovery happens through AI systems: ChatGPT, Perplexity, Claude, and Google’s own AI Overviews. These systems do not crawl the web like search engines. They index it, summarize it, and cite sources. When someone asks Perplexity “who is the best acupuncturist in Kirkland for fertility issues,” Perplexity reads its index of websites and synthesizes an answer. It cites the sources it used.

If your website does not have structured data, you are nearly invisible to this process. AI indexing systems weight structured data heavily because it is the only content they can consume without ambiguity. They can read your BlogPosting schema to know what you wrote about. They can read your Person schema to know your credentials. They can read your LocalBusiness schema to know your location and services. Without these signals, you might as well not be in the index.

The traffic pattern is already shifting. Studies from late 2025 show that queries triggering AI Overviews divert substantial click volume away from traditional organic results. If your business depends on being found online, and your website has no structured data, you are preparing for a world that no longer exists.

What Proper JSON-LD Looks Like for a Professional Practice

Here is a simplified example. This is not the full markup. It is the conceptual structure.

A proper LocalBusiness schema for an acupuncture clinic includes: the business name and type, the address with postal code, the phone number, the website URL, business hours by day, accepted payment methods, the practitioner’s credentials (linked as a Person entity), the services offered (linked as Service entities), a link to the Google Business Profile (via sameAs), and the geographic coordinates.

The key is not just that this information exists. It is that it exists in a format that every major search engine and AI system can consume without interpretation. You are not relying on Google to correctly parse “Dr. Chen, Licensed Acupuncturist, practicing in Kirkland since 2015” from a paragraph of text. You are telling it explicitly:

This is a MedicalBusiness.
The practitioner holds this specific license.
The address is this exact geolocated point.
The hours are these specific times.
The profile on Google is this verified URL.

The specificity builds trust. Trust builds ranking.

Which Pages Need What Kind of Structured Data

A common mistake is treating structured data as something you add once to your homepage and forget. Different pages serve different purposes, and the structured data should match. Here is what goes where.

Homepage: This is where you establish your business entity. The primary schema is LocalBusiness or MedicalBusiness. Include your name, address, phone, hours, and a link to your Google Business Profile. You can also add WebSite schema with a search action, which tells Google your site has an internal search function. That is optional but useful.

Service pages: Each specific service you offer should have Service schema. If you are an acupuncturist, your fertility support page carries Service schema for fertility acupuncture. Your pain management page carries Service schema for pain management. This helps Google and AI systems connect specific queries to specific pages rather than just knowing you are an acupuncturist in general.

Practitioner bios: About pages and team member profiles should use Person schema. Include name, job title, credentials, education, affiliations, and a link to the LocalBusiness entity they belong to. This creates the connection between the person and the practice that AI systems use when answering queries about specific providers.

Blog posts and articles: Every post gets BlogPosting schema. Required fields are headline, author, datePublished, and image. Recommended fields are dateModified and description. The dateModified field is particularly important. If you update a post with new information, the dateModified tells search engines and AI systems that the content is current. Without it, they may assume the post is stale.

FAQ pages: If you have a frequently asked questions page, use FAQPage schema. Each question-answer pair becomes eligible for FAQ rich results in search, which can expand your listing significantly.

Contact page: This is often the worst-structured page on small business sites. A contact page should carry LocalBusiness schema with your full contact details, hours, and accepted payment methods. Do not assume the homepage schema covers this page too. Each page that contains unique contact information should declare it.

Do you need structured data on every single page? No. A privacy policy or terms of service page probably does not need custom schema beyond the basic WebPage type that most platforms add automatically. But every page that serves a discovery purpose, that answers a question a potential patient or client might ask, should have structured data that matches its content.

The Update Problem

Here is where most structured data efforts quietly fail. Someone installs it once, validates it, and walks away. Six months later, the phone number has changed, the practitioner has added a new certification, the business moved locations, or a new service replaced an old one. The structured data now says something different from the visible page content.

Google calls this a mismatch, and it is one of the fastest ways to lose trust. If your JSON-LD says you are open until 8 PM but your visible hours say 6 PM, Google does not know which to believe. If your schema lists a credential you no longer hold, or a service you no longer offer, you are making claims you cannot substantiate. In the worst case, structured data that contradicts the visible page can trigger a manual review or rich result suppression.

For traditional search, this is a gradual credibility erosion. For AI systems, it can be worse. When an AI cites your structured data to answer a question, it treats that information as a factual claim. If the claim is outdated, the AI may repeat it, and you may end up associated with information that is no longer true. The damage to your reputation is harder to recover than a ranking drop because the AI citation lives in someone else’s answer, not on a page you control.

How to Keep It Current

The best approach depends on how your website is built.

If you use WordPress with a plugin like Yoast or RankMath, the plugin generates structured data automatically from your page content and settings. The catch is that the plugin only knows what you have entered into its fields. If you update a page directly in the editor without updating the plugin’s schema settings, you still have a mismatch. The fix is to treat schema-related fields as part of the content editing workflow. When you change a service, update the service page, the menu, and the plugin’s service schema all at once.

If your site is custom-built or static, you are probably managing JSON-LD by hand. This gives you full control but creates a maintenance burden. The discipline that works is to keep a master data file, a single source of truth for your business information, and generate all JSON-LD from that file. When something changes, you change it in one place and regenerate every block.

For the clients we work with, we provide both the initial structured data blocks and a maintenance schedule. We recommend a quarterly review: check the markup against the visible page content, verify that dateModified fields on posts reflect actual updates, confirm that NAP data still matches the Google Business Profile, and validate everything against Google’s test tool. If you change something material, a new service, a new practitioner, a location move, update the structured data the same day.

Some changes are easy to miss. If you add a new accepted insurance to your site text but do not add it to your LocalBusiness schema, the old information is still what the machines see. If you publish a blog post update but do not update the dateModified field in the schema, the machines still see the original publication date. These small gaps accumulate into a profile that looks neglected, and neglected profiles do not rank well.

The Discipline That Matters

Structured data is not a plugin you install. It is a representation of your business that you maintain. The businesses that benefit from it treat it like their Google Business Profile or their directory listings: a living document that changes when the business changes.

The cost of maintenance is low if you build it into your workflow. The cost of neglect is that your competitors, the ones who keep their structured data current, gradually become the entities that machines trust and cite.

Why Most Businesses Do Not Have This

In my audit of two hundred and fifty Eastside businesses, the reasons fell into three categories.

The websites built on DIY platforms, Wix and Squarespace, often had minimal structured data: a WebSite type and maybe a WebPage type. These are generic. They tell Google “this is a website” and nothing more. They do not tell it what kind of business it is, who runs it, or what services are offered.

The websites built by web designers on WordPress were more varied. Some had excellent structured data, usually via plugins like Yoast or RankMath that generate it automatically. Others had none at all because the designer never enabled the feature. The designer focused on how the site looked, not on how it communicated with machines.

The third category was the most common: small business owners who built their own sites or hired a relative who knew HTML. They had no structured data because nobody told them it existed.

This is not a criticism of web designers. Design and user experience matter enormously. But the invisible layer matters too, and it is often neglected because it is invisible. You do not see structured data when you visit a website. You only see its absence when your site does not show up in search.

What Common Sense Systems Does

At Common Sense Systems, we have built a structured data service specifically for professional practices: healthcare providers, therapists, wellness practitioners, and small professional services firms. The way it works is straightforward.

We interview you for thirty minutes. We collect your business information: name, address, phone, hours, services, credentials, accepted insurance, languages spoken, accessibility features, everything that should be in your structured data. We then produce a complete, validated JSON-LD block for your website. It includes LocalBusiness, Person for each practitioner, Service for each offering, and proper sameAs links to your Google Business Profile and other verified profiles.

We validate the output against Google’s Rich Results Test and Schema.org’s validator before delivery. The markup is designed to be dropped into your website’s header with no modification. Most web developers or site administrators can install it in under five minutes. If you do not have someone who can do that, we can do it for you.

The cost is fixed and small relative to the value. And unlike paid advertising, which stops working the moment you stop paying, structured data is a durable asset. It keeps working for as long as it is on your site.

The Business Case Is Simple

If 72 percent of first-page results use structured data, and 59 percent of small business websites do not have it, the competitive opportunity is obvious. This is not a marginal improvement. For many businesses, it is the single highest-return change they can make to their web presence.

The cost of adding structured data is measured in hundreds of dollars and a few hours of your time. The cost of not having it is measured in patients, clients, or customers who never find you because a machine could not understand what you do.

If you want to know whether your website currently has proper structured data, the fastest way is Google’s own Rich Results Test. Enter your homepage URL and see what it finds. If the result is empty or shows only generic WebPage markup, you are in the majority of businesses that have left this channel unexplored.

If you would like help fixing that, or if you just want to sanity-check what your current site is communicating to machines, send me a note at john@common-sense.com. I am happy to look at it and tell you what I see.

Why JSON-LD Is the Cheapest Insurance Your Website Can Buy