How to add Organization and LocalBusiness schema that AI can read
Add Organization or LocalBusiness markup as JSON-LD in the <head> of your site, keep it on one canonical URL (usually the homepage or the location page), and make every fact in it match what visitors see on the page. The goal is not a rich result – it is giving machines one unambiguous, machine-readable description of who you are, where you are and how to verify it. Use Organization for the company as an entity, LocalBusiness (or a more specific subtype) for a physical place customers can visit.
Why does schema matter for AI answers, not just for Google?
Classic search engines have used structured data for years to build rich results and knowledge panels. Google and Bing both document structured data support, and Bing's index feeds Copilot and parts of other AI products – so markup you add for search is not wasted on AI.
For LLM-based answer engines the picture is less certain. Several AI crawlers fetch raw HTML without executing JavaScript, and none of them publishes a precise statement like "we parse JSON-LD into facts." What is well established is that JSON-LD is plain text inside the HTML, so a crawler that reads your HTML reads your markup too, in a compact and unambiguous form: name, address, phone, founding date, official profiles.
The practical benefit is entity disambiguation. If three companies share your brand name, the model has to guess which one the page is about. Explicit sameAs links to Wikipedia, LinkedIn, Crunchbase or an official register, plus a consistent address and legal identifiers, make that guess much easier – and make the answer more likely to describe you correctly.
Organization or LocalBusiness – which one do I need?
LocalBusiness is a subtype of Organization. You never need both as separate blocks for the same entity, but a company with a head office and several branches often publishes one Organization for the brand and one LocalBusiness per location.
| Question | Organization | LocalBusiness |
|---|---|---|
| Who is it for | Any company, brand, nonprofit, agency | A business with a physical address customers visit |
| Where to put it | Homepage or About page | Contact page or each location page |
| Address required | Recommended, not required | Yes – full PostalAddress |
| Opening hours | Not applicable | openingHoursSpecification strongly recommended |
| Typical extras | sameAs, logo, foundingDate, vatID | geo, telephone, priceRange, areaServed |
| Online-only business | Use this | Do not use |
Online-only businesses should stay with Organization. Marking up a coworking desk or a registered address you never meet clients at as a LocalBusiness is the kind of mismatch that gets ignored at best.
What does a correct Organization block look like?
Put this in the <head> of your homepage. Every value should appear somewhere in your visible content too.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example Analytics",
"legalName": "Example Analytics Ltd.",
"url": "https://example.com/",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/img/logo.png",
"width": 512,
"height": 512
},
"description": "Example Analytics builds product analytics dashboards for B2B SaaS teams.",
"foundingDate": "2016-04-11",
"vatID": "GB123456789",
"email": "hello@example.com",
"telephone": "+44-20-7946-0958",
"address": {
"@type": "PostalAddress",
"streetAddress": "14 Hanover Street",
"addressLocality": "London",
"postalCode": "W1S 1YH",
"addressCountry": "GB"
},
"contactPoint": [{
"@type": "ContactPoint",
"contactType": "customer support",
"telephone": "+44-20-7946-0958",
"email": "support@example.com",
"availableLanguage": ["en", "de"]
}],
"sameAs": [
"https://www.linkedin.com/company/example-analytics",
"https://x.com/exampleanalytics",
"https://github.com/exampleanalytics",
"https://en.wikipedia.org/wiki/Example_Analytics"
]
}
</script>
Three fields do most of the work for AI visibility. description gives a one-sentence definition of the company that a model can reuse. sameAs ties your site to profiles that already exist in training data and in search indexes. @id gives the entity a stable identifier you can reference from every other block on the site.
What does a correct LocalBusiness block look like?
Use the most specific subtype that fits: Restaurant, Dentist, AutoRepair, HairSalon, ProfessionalService, Store. Specific types carry more meaning than the generic parent.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Dentist",
"@id": "https://example-dental.com/clinics/kreuzberg#localbusiness",
"name": "Example Dental – Kreuzberg",
"url": "https://example-dental.com/clinics/kreuzberg",
"image": "https://example-dental.com/img/kreuzberg-reception.jpg",
"telephone": "+49-30-12345678",
"priceRange": "€€",
"currenciesAccepted": "EUR",
"paymentAccepted": "Cash, Credit Card, Debit Card",
"address": {
"@type": "PostalAddress",
"streetAddress": "Oranienstraße 12",
"addressLocality": "Berlin",
"addressRegion": "BE",
"postalCode": "10999",
"addressCountry": "DE"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 52.5027,
"longitude": 13.4210
},
"areaServed": {
"@type": "City",
"name": "Berlin"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday"],
"opens": "08:00",
"closes": "19:00"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Friday",
"opens": "08:00",
"closes": "15:00"
}
],
"parentOrganization": { "@id": "https://example-dental.com/#organization" },
"sameAs": [
"https://www.google.com/maps/place/?q=place_id:ChIJexample",
"https://www.yelp.com/biz/example-dental-berlin"
]
}
</script>
Note parentOrganization pointing at the brand-level @id. That single line tells a parser that this clinic belongs to a larger company instead of being an unrelated business with a similar name.
How do I connect the blocks so machines see one entity?
Scattering unconnected JSON-LD snippets across pages produces duplicates: the same company described five slightly different ways. The fix is a @graph with stable @id values and references between nodes.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example Analytics",
"url": "https://example.com/"
},
{
"@type": "WebSite",
"@id": "https://example.com/#website",
"url": "https://example.com/",
"name": "Example Analytics",
"publisher": { "@id": "https://example.com/#organization" },
"inLanguage": "en"
},
{
"@type": "WebPage",
"@id": "https://example.com/pricing#webpage",
"url": "https://example.com/pricing",
"name": "Pricing",
"isPartOf": { "@id": "https://example.com/#website" },
"about": { "@id": "https://example.com/#organization" }
}
]
}
</script>
Rules that keep this clean: define the full Organization once, on the homepage; everywhere else reference it by @id only; never change an @id after publishing; always use absolute HTTPS URLs that match your canonical domain (with or without www, but pick one).
How do I handle multiple locations?
Give each location its own URL and put one LocalBusiness block on that page. Do not stack ten locations into the homepage markup – it dilutes the page and makes every location look equally relevant to every query.
- Create
/locations/city-name/pages with real content: address, hours, photos, staff, parking, directions. - Add one
LocalBusinesssubtype block per page, each with its own@idending in#localbusiness. - Link each one to the brand with
parentOrganization. - On the brand's
Organizationblock, list the branch URLs indepartmentor simply link them in the HTML navigation. - Keep name, address and phone identical to what you publish on your Google Business Profile and directory listings.
That last point matters more than the markup itself. AI answers about "dentist in Kreuzberg" are assembled from many sources; conflicting phone numbers across your site, your map profile and aggregators create doubt that no amount of JSON-LD removes.
How do I check that AI crawlers can actually read it?
- Validate syntax with the Schema Markup Validator (validator.schema.org) and Google's Rich Results Test. Fix every error; treat warnings as a checklist.
- View the page source with JavaScript disabled, or run
curl -A "GPTBot" https://example.com/ | grep ld+json. If the block disappears, it is injected client-side and some crawlers will miss it. - Check Google Search Console's "Enhancements" reports for structured data errors across the whole site.
- Confirm your robots.txt does not block the crawlers you want:
User-agent: GPTBot
Allow: /
User-agent: OAI-SearchBot
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Google-Extended
Allow: /
Sitemap: https://example.com/sitemap.xml
- Ask the AI engines directly: "What is Example Analytics and where is it based?" If the answer is vague, wrong or about another company, your entity signals are too weak – that is a content and citation problem, not only a markup one.
Server-side rendering is the single most important technical condition. If your framework injects JSON-LD through a tag manager or a client-side hook, move it to the server-rendered HTML.
What are the most common mistakes?
Markup that contradicts the page. Hours in JSON-LD say 09:00–18:00, the footer says 10:00–19:00. Parsers that notice the conflict discount both.
Invented review stars. aggregateRating on an Organization or LocalBusiness with no visible, verifiable reviews on the page violates Google's guidelines and can trigger a manual action.
Generic types everywhere. "@type": "LocalBusiness" when Restaurant or Plumber exists wastes meaning you could have provided for free.
Unstable or relative @id values. "@id": "#org" or IDs that change on each deploy break every reference pointing at them.
One huge block on every page. Repeating the full Organization description on 400 pages invites duplicate-entity confusion. Define once, reference everywhere.
Empty strings and placeholders. "telephone": "" or "description": "Lorem ipsum" in production is worse than omitting the field.
FAQ
Do I need both Organization and LocalBusiness on the same page?
No. On a single-location business's homepage, one LocalBusiness block is enough – it inherits everything Organization offers. Use two linked blocks only when a multi-location brand needs a company-level entity plus separate place entities.
Does JSON-LD help if ChatGPT does not confirm it reads structured data?
It helps indirectly and costs little. Google and Bing documented support feeds AI Overviews and Copilot, and JSON-LD is plain text in your HTML that any crawler reading the page encounters. Treat it as cheap insurance plus guaranteed classic-search value rather than a guaranteed LLM ranking factor.
Should I use Microdata or RDFa instead?
JSON-LD is the format Google recommends and the easiest to maintain because it lives in one block instead of being woven through your HTML. Only keep Microdata if you have a legacy system that cannot output a script tag.
How long until changes show up?
It depends on recrawl frequency, which varies by site. Structured data changes typically surface in Search Console within days of the next crawl; references inside AI answers can lag much longer because many models blend cached and live sources. [check: typical lag for AI answer refresh]
What should go in sameAs?
Only profiles you control or authoritative references about you: LinkedIn, X, GitHub, YouTube, Crunchbase, Wikipedia, Wikidata, an official business register entry, your Google Business Profile map link. Do not list news articles, random directories or pages about someone else.
If you want to know whether your current markup is visible to AI crawlers and whether answer engines describe your company correctly, you can run a free check of your site in Zgadka – it returns GEO and SEO scores plus a report with ready-made schema.org, robots.txt and llms.txt files to fix what is missing.