Schema Markup June 12, 2026 · 9 min read

Schema Markup for Local Businesses: A Plain-English Guide

Schema markup is consistently the single highest-ROI fix in AI visibility audits. It’s also the one that sounds the most technical and gets the most clients saying “that’s probably not something I can do myself.” Good news: the concept is straightforward. The implementation, for a local business, is simpler than you think. And the impact on how clearly AI engines understand what your business does — and whether they recommend it — is significant.

What Schema Markup Actually Is

Schema markup is structured data written in a format called JSON-LD. It lives in your page’s HTML — specifically in the <head> section — and it’s completely invisible to website visitors. But it’s very visible to AI crawlers and search engines, because it tells them exactly what your page represents in a structured, machine-readable format.

Without schema, an AI system reading your homepage has to infer that you’re a plumbing company in San Antonio from the text on your page. With schema, you’re explicitly stating it in a format the machine reads perfectly. You’re also stating your hours, your phone number, your service area, the specific services you offer, and how all of this connects to your other pages.

Schema markup is like a business card for machines. Your website copy is what customers read. Schema markup is what AI engines read. Both need to be present — and they need to agree with each other.

Why Schema Markup Matters for AI Search

AI engines are risk-averse. When deciding which businesses to recommend, they weight certainty heavily. A business with clear, valid schema markup is a lower-risk recommendation than one that requires interpretation. And in competitive local markets where multiple businesses offer the same service, the one with cleaner structured data consistently has an advantage.

There’s also an accuracy dimension. AI systems that make incorrect recommendations lose user trust. Schema markup gives them the information they need to make accurate recommendations about your specific business — not a guess based on your copy. That accuracy benefit is why Google, OpenAI, and Anthropic have all indicated strong preference for structured, schema-marked content when generating AI responses.

Want to know if your schema is valid and complete? Schema validation is one of 16 categories in a Raise Rank AI audit.
Book Your Audit →

The 5 Most Important Schemas for Local Businesses

  • 1

    LocalBusiness

    The foundation. This schema tells AI engines your business name, type, address, phone, hours, and service area. Without it, everything else is built on inference. Every local business website should have a valid LocalBusiness schema on the homepage.

  • 2

    FAQPage

    The highest-ROI schema for AEO specifically. FAQPage markup tells AI engines that your page directly answers specific questions. When someone asks that question to an AI, your answer is a candidate for the response. This is one of the most direct pathways to AI citation that exists for local businesses.

  • 3

    Service

    Adds structured detail to each individual service you offer — what it is, who provides it, and where. This lets AI engines match you to specific service queries rather than just general business-type queries. An attorney with Service schemas for each practice area gets matched to more targeted queries than one with only LocalBusiness.

  • 4

    BreadcrumbList

    Tells AI engines how your pages relate to each other and creates a clear site hierarchy. It also produces the breadcrumb trail visible in Google search results, which improves click-through rate. While not as directly impactful as LocalBusiness or FAQPage for AI recommendations, it significantly improves how AI engines understand your site structure.

  • 5

    Person (for E-E-A-T)

    For service businesses where the founder’s expertise matters — attorneys, financial advisors, medical professionals — Person schema establishes the real human behind the business. It connects your professional credentials to your business entity, which is critical for YMYL (Your Money or Your Life) queries where AI engines apply elevated trust standards.

Writing Your LocalBusiness Schema: A Real Example

Here’s what a complete, correctly formatted LocalBusiness schema looks like for a law firm in San Antonio:

<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "LegalService", "@id": "https://yourlawfirm.com/#business", "name": "Smith Law Firm", "description": "Personal injury attorney serving San Antonio, TX", "url": "https://yourlawfirm.com", "telephone": "+12105550199", "address": { "@type": "PostalAddress", "streetAddress": "123 Commerce St, Suite 400", "addressLocality": "San Antonio", "addressRegion": "TX", "postalCode": "78205", "addressCountry": "US" }, "geo": { "@type": "GeoCoordinates", "latitude": 29.4241, "longitude": -98.4936 }, "openingHours": ["Mo-Fr 08:00-17:00"], "areaServed": "San Antonio, TX", "sameAs": [ "https://www.google.com/maps/place/...", "https://www.yelp.com/biz/..." ] } </script>

A few things to note. The @type should be as specific as possible — use “LegalService” for law firms, “MedicalBusiness” for medical practices, “HomeAndConstructionBusiness” for contractors. The sameAs array links your schema entity to your profiles on other platforms, which significantly strengthens the trust signal.

FAQPage Schema: The Highest-ROI Schema for AEO

FAQPage schema is what enables your website to directly feed AI responses. When a user asks an AI tool a question that matches your FAQPage content, the AI has a structured, verified answer it can cite from your site. This is different from hoping the AI reads your copy and extracts the right information — you’re providing the answer in the exact format the AI expects.

<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "How long does a personal injury case take in San Antonio?", "acceptedAnswer": { "@type": "Answer", "text": "Most personal injury cases in San Antonio settle within 6 to 18 months. Cases that go to trial can take 2 to 3 years. The timeline depends on the severity of the injury, liability disputes, and the defendant's insurance response." } }, { "@type": "Question", "name": "Do I need a lawyer for a car accident in Texas?", "acceptedAnswer": { "@type": "Answer", "text": "You are not required to hire a lawyer, but studies show that accident victims represented by attorneys receive settlements 3 to 4 times larger on average than those who negotiate directly with insurance companies." } } ] } </script>

The questions to include in your FAQPage schema should come directly from what your customers actually ask — not what you wish they asked. Pull from your intake forms, your phone calls, your GBP Q&A section. The more literally your FAQ questions match real user queries, the more likely your answers are to surface in AI responses to those queries.

How to Test That Your Schema Is Working

Adding schema to your site doesn’t guarantee it’s valid. A single misplaced comma or bracket in your JSON-LD will invalidate the entire block without producing a visible error. Always test after implementation.

Two tools to use:

  • Google Rich Results Test (search.google.com/test/rich-results): Paste your URL and see which schema types are detected and whether they pass validation. This is the authoritative tool for anything that affects Google-powered features.
  • Schema.org Validator (validator.schema.org): Provides more granular detail on property-level errors and warnings. Use this to catch issues that Google’s tool might not surface explicitly.

Common mistakes to fix:

  • Missing @context or @type fields (required in every schema block)
  • Using a generic @type: "LocalBusiness" when a more specific type is available
  • Phone numbers not formatted as E.164 (+12105550199 instead of (210) 555-0199)
  • Address fields that don’t match your GBP address exactly
  • FAQPage answers that are too short or don’t actually answer the question

Frequently Asked Questions

Not necessarily. WordPress has plugins like RankMath and Yoast that handle LocalBusiness and FAQPage schema through a UI. Squarespace and Wix have built-in schema tools. For custom sites, a developer can add JSON-LD to your page head in under an hour. On platforms like Duda, schema support is built into the platform.
JSON-LD is a block of JavaScript added to your page head. Microdata embeds schema attributes directly into your HTML. Google and most AI engines strongly prefer JSON-LD because it’s easier to maintain, doesn’t require changes to visible HTML, and is much less likely to contain errors.
Schema effects are typically visible in Google AI Overviews within 30 to 60 days. ChatGPT citation eligibility generally builds over 60 to 90 days as AI systems re-index and re-evaluate your site. The improvements compound — each additional schema type you add makes your entity clearer and more citable.
Incorrect schema generally doesn’t actively hurt rankings, but it also doesn’t help. Invalid schema that fails validation is typically ignored by Google. The bigger risk is schema that misrepresents your business — incorrect hours, wrong address, wrong business type — which can cause confusion in AI recommendations and user experience.
Google’s Rich Results Test (search.google.com/test/rich-results) is the primary tool — it shows which schema types are detected and whether they pass validation. Schema.org’s validator (validator.schema.org) provides additional detail on property-level errors. Use both after any schema implementation.

Schema Markup Is the Foundation Everything Else Builds On

You can have great reviews, a complete GBP, and a well-written website — but without schema markup, AI engines still have to guess about your business. Schema removes the guesswork. It tells them exactly who you are, what you do, where you do it, and why you’re trustworthy. In a landscape where AI engines are increasingly risk-averse about which businesses they recommend, that clarity is a competitive advantage that compounds over time.

Book Your AI Visibility Audit →
Gabe Olivares
Gabe Olivares
Founder, Raise Rank · San Antonio, TX

Gabe runs Raise Rank, an AI visibility consulting agency that helps San Antonio-area businesses get found in ChatGPT, Google AI Overviews, and Perplexity. He's completed audits for local businesses across legal, construction, and professional services.

Schema Markup JSON-LD AEO Structured Data Local SEO San Antonio