Why this matters for an insurance agent
For the agent, schema is what makes Google and AI name their agency with confidence instead of guessing. It feeds the map pack, rich results, and AI answers the exact facts, who they are, what they sell, where they serve, so a prospect sees the agent's name, phone, and services front and center at the moment they are ready to reach out.
JSON-LD in plain terms
Structured data is a small block of code (we use the JSON-LD format) tucked in the page's head. It labels the facts on the page in a vocabulary from schema.org that every search engine understands.
Without it, Google reads your text and infers "this looks like an insurance agency in Dallas". With it, you state it as fact: name, address, phone, hours, services, areas served. Less guessing means more trust and richer results.
Why it matters more every year
AI assistants and Google's own AI answers lean heavily on structured data to resolve who a business is and pull the right facts. Good schema is now a requirement for being cited by AI, not a nice-to-have.
A connected graph, not scattered stubs
We do not drop one bare stub and call it done. We wire a connected @graph: several schema objects linked together by a shared @id so search engines see one coherent entity.
- LocalBusiness (or a specific type like InsuranceAgency): the enriched core. Name, url, image, logo, phone, email, full address with postal code, geo coordinates, areaServed, opening hours, services offered, founder, and sameAs profile links.
- WebPage: the page itself, linked to the business.
- Service: what is offered on a service page.
- FAQPage: real question-and-answer pairs, which can win expanded results and feed AI.
- BreadcrumbList: the page's position in the site.
Never fabricate ratings or reviews
Zero tolerance
Never invent an aggregateRating, a star count, or reviews in schema. Use only the client's real review data. If they have none yet, leave it out and flag it as a pending win. Fake review schema is a policy violation that can get a site penalized and is a fast way to lose a client's trust.
Everything in the schema must be true and byte-consistent with what shows on the page and on the client's Google Business Profile and citations. Structured data is a promise to the search engine. We keep it honest.
* Key takeaways
- Schema (JSON-LD) labels the facts on a page so search engines know them for certain instead of guessing.
- AI answers and AI Overviews rely on structured data, so good schema is now required to be cited, not optional.
- We ship a connected @graph wired by a shared @id: LocalBusiness/InsuranceAgency + WebPage + Service + FAQPage + BreadcrumbList.
- The LocalBusiness block must be enriched (address, geo, hours, areaServed, services, sameAs), not a bare stub.
- Never fabricate aggregateRating or reviews. Use only real data or leave it out and flag it.
Module 5 quiz
Score 75% or higher to complete this module and unlock the next one.
4 questions
Not completed-
What does structured data (schema) do for a page?
Why: Schema labels the facts (business, phone, FAQ) in a vocabulary engines understand, so they read the page with certainty.
-
Why does schema matter more every year?
Why: AI assistants and AI Overviews lean on structured data to know who a business is, so good schema is now required for AI citation.
-
What is the right way to build our schema?
Why: We wire a connected @graph (LocalBusiness, WebPage, Service, FAQPage, BreadcrumbList) linked by a shared @id.
-
The client has no reviews yet. What do we put in aggregateRating?
Why: Never fabricate ratings or reviews. If there are none, leave the field out and flag it. Fake review schema can get a site penalized.