Schema markup for insurance agents: exactly which types, on which pages

Short answer: an insurance agency site needs six schema types, and each one has a specific home. Organization plus InsuranceAgency on the homepage. Person on the about page. Service with a service area on every line-of-business and county page. BlogPosting on every article. BreadcrumbList everywhere. FAQPage anywhere you genuinely answer questions. Written in JSON-LD, which is the format Google says it prefers. That's the whole list — everything past that is decoration.

The reason most agent sites get this wrong isn't difficulty. It's that a plugin dumped a generic LocalBusiness block on the homepage in 2021, nobody looked since, and it says your business is called "My WordPress Site."

What schema markup actually is

Schema markup is a block of JSON in the head of your page stating facts in a vocabulary machines already agree on — schema.org. Instead of hoping a crawler infers from your header image that you're an insurance agency in Grand County, you tell it, in a field named areaServed, that you serve Grand County.

Two ground rules from Google's structured data guidelines that people break constantly. "Don't mark up content that is not visible to readers of the page" — if your JSON claims four locations and your page shows one, that's a policy violation, not a growth hack. And "try to use the most specific applicable type and property names," because generic markup is nearly as useless as none.

Which schema type goes on which page?

Homepage: InsuranceAgency, not LocalBusiness

On schema.org, InsuranceAgency sits below LocalBusiness — Organization → LocalBusiness → FinancialService → InsuranceAgency — inheriting every LocalBusiness property while being more precise about what you are. Google's local business documentation is explicit: use the most specific sub-type possible. Only name and address are required; telephone, url, geo, and openingHoursSpecification are recommended and worth the five minutes.

Google suggests putting Organization data on your home page or a single page describing the organization, not scattering conflicting copies site-wide. Give the block a stable @id — https://youragency.com/#org — and have every other page reference that ID instead of restating the details.

About page: mark up the human

Insurance is a licensed, personal business, and the about page is where you prove a real person is behind the site. Person markup with jobTitle, worksFor pointing at your agency's @id, and knowsAbout listing your actual lines links a named, licensed individual to a named business. If you publish your NPN or state license number on the page — and you should — mirror it in the markup.

Service pages: the type nobody uses

Most agency sites have a "Medicare" page with no markup at all. Service is the right type, carrying serviceType ("Medicare Advantage plan comparison"), provider (your agency's @id), areaServed, and audience. Google renders no rich result from it, which is why SEO plugins ignore it — and exactly why it's underused. It's there for machines that need to know what you do and where, which is the entire question an assistant is trying to answer.

What about FAQ schema — didn't Google kill it?

Yes, and you should know the timeline before a vendor sells you on it. Google restricted FAQ rich results in August 2023 to well-known, authoritative government and health websites, and deprecated HowTo rich results outright. Then, per the Search Central changelog, the FAQ rich result stopped appearing in Google Search entirely on May 7, 2026, and the documentation was removed on June 15, 2026.

So if someone quotes you a price for "FAQ schema to get rich snippets," they're selling a feature that no longer exists. We still put FAQPage markup on our builds, for a more honest reason: it's the cleanest machine-readable way to bind a question to a complete, self-contained answer — the raw material an assistant needs to quote you without reading your whole page. The rich result is gone; the parseability isn't.

Will schema get my agency into AI Overviews?

Not on its own, and we'd rather say that than sell you a myth. Google's guide to generative AI features states it plainly: "Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add." The same page says it's still worth using as part of overall SEO — but that unique, useful content will influence your presence in generative AI search more than any other suggestion in the guide.

That's the correct framing. Schema isn't a citation switch — it's a disambiguation layer that removes every guess a machine would otherwise make about who you are, where you work, and what you sell. The content still has to be worth quoting. The rest of that stack is in our AEO guide for insurance agents, and the "why am I invisible" version in this post on getting cited.

Four mistakes we find on almost every agency site

1. Star ratings on your own reviews. Google's review snippet documentation calls a review about entity A published on entity A's own site self-serving, and LocalBusiness or Organization pages are ineligible for the star feature on that basis. Keep the testimonials. Drop the aggregateRating you generated yourself.
2. Two conflicting Organization blocks. A theme injects one, a plugin another, and they disagree on the phone number. Pick one, delete the other.
3. Markup pointing at pages that don't exist. Breadcrumbs referencing a "Locations" page you removed, or a logo URL that 404s. Every URL in your markup must resolve.
4. Compliance claims smuggled into JSON. Don't put plan names, premiums, or superlatives in schema fields you wouldn't put on the visible page — the same rules apply either way. Your consumer-facing site still needs the "we do not offer every plan available in your area" language and the non-affiliation disclaimer; confirm the specifics with your FMO and carriers.

How to check yours in ten minutes

1. Open your homepage, view source, and search for application/ld+json. If there's nothing, that's your answer.
2. Paste the URL into the Schema Markup Validator. It checks whether your markup is valid schema.org at all, including types Google doesn't consume — which is most of what matters here.
3. Then run Google's Rich Results Test on the same URL to see which Google features the page qualifies for.
4. Read the output like a stranger. Does it name your agency, your agent, your phone, and your counties? If a human couldn't identify your business from the JSON alone, neither can a model. Repeat on one service page and one blog post — usually where the markup stops entirely.

None of this is hard — a capable agent with a free afternoon can do it. What it isn't is one-and-done: every new page needs markup, every county page its own areaServed, every article its BlogPosting block. That's what quietly stops happening in month three. It's built into every site we ship; full deliverable list on what you get, broader site audit in our 12-point website checklist.

Frequently asked questions

What schema markup does an insurance agent website need?

At minimum: Organization plus the InsuranceAgency type on the homepage, Person for the licensed agent on the about page, Service with an areaServed value on each line-of-business and county page, BlogPosting on every article, and BreadcrumbList site-wide. FAQPage is worth adding to any page with a real question-and-answer section. All of it should be JSON-LD, which is the format Google recommends, and it should only describe things a human can also read on the page.

Should I use LocalBusiness or InsuranceAgency schema?

Use InsuranceAgency. On schema.org it sits underneath LocalBusiness in the hierarchy — Organization to LocalBusiness to FinancialService to InsuranceAgency — so it inherits every LocalBusiness property while being more precise about what you are. Google's own local business documentation tells publishers to use the most specific LocalBusiness sub-type available, and for an agency that sub-type is InsuranceAgency.

Is FAQ schema still worth adding in 2026?

It no longer earns a rich result. Google restricted FAQ rich results to authoritative government and health sites in August 2023, and the feature stopped appearing in Google Search entirely on May 7, 2026, with the documentation removed that June. FAQPage markup is still worth writing because it is the cleanest machine-readable way to pair a question with a self-contained answer, which is exactly the shape an AI assistant needs in order to quote you — but nobody should promise you stars or an expanded listing from it.

Can schema markup make my agency show up in AI Overviews?

Not by itself, and Google says so directly: structured data is not required for its generative AI search features and there is no special schema.org markup that makes a page eligible. What schema does is remove ambiguity — it states your business name, license, service area, and lines of business in a format a machine parses instead of infers. Treat it as a foundation that makes good content easier to verify and quote, not as a switch that turns on citations.

How do I test my schema markup?

Use two tools, because they answer different questions. Google's Rich Results Test tells you whether a page qualifies for a specific Google search feature, and the Schema Markup Validator at validator.schema.org checks whether your markup is valid schema.org at all, including types Google does not consume. Run the validator first to catch broken JSON and misspelled properties, then the Rich Results Test to see what Google will actually do with it.