How to Fix Missing Organization Schema (JSON-LD Guide)
This audit check fails when no page on your site has structured data typed as Organization or a LocalBusiness subtype such as Store, Restaurant, Dentist or ProfessionalService. By the end of this guide you will have one valid JSON-LD block on your homepage or global template that names your business, points to your logo, links your official social profiles and lists a contact point.

Why it matters
Organization markup is how you state who owns the site in a format machines can read. Google uses it to choose the logo and details in knowledge panels and brand results. AI assistants and answer engines use the sameAs links to connect your site with your LinkedIn, Facebook and other profiles, which reduces mix-ups with similarly named companies.
LocalBusiness subtypes also feed address, phone and opening hours into local results. Without it, search engines guess these details from scattered page text, and they often guess wrong.
What you need
Step-by-step fix
Pick the most specific @type for your business
Use Organization for online-only companies, SaaS products, publishers and non-profits. If customers visit you at a physical location, use LocalBusiness or a more specific subtype such as Dentist, Restaurant, Store, ProfessionalService, LegalService or AutoRepair. Large registered companies can use Corporation.
Any of these types passes the check, and a more specific type gives search engines more context.
Collect the exact values you will publish
Collect these before you write any markup, and make sure each value matches what the site shows to visitors:
- name: the brand name as it appears on the site
- url: the canonical homepage, including https and the trailing slash
- logo: an absolute URL to a crawlable image that is at least 112×112 px and still reads clearly on a white background
- sameAs: the official profiles you control (LinkedIn, Facebook, Instagram, YouTube, X, Wikipedia or Wikidata if you have them)
- contactPoint: a phone number in international format and/or an email address, plus the contactType
Write the Organization JSON-LD block
Copy the template below and replace every value. The @id gives the entity a stable identifier that other schema blocks can reference. Remove any property you cannot fill truthfully.
Leaving out a property is better than publishing placeholder text.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example Co",
"legalName": "Example Co Ltd",
"url": "https://example.com/",
"logo": "https://example.com/images/logo-512.png",
"description": "Example Co makes accounting software for small agencies.",
"email": "hello@example.com",
"sameAs": [
"https://www.linkedin.com/company/example-co",
"https://www.facebook.com/exampleco",
"https://www.instagram.com/exampleco",
"https://www.youtube.com/@exampleco"
],
"contactPoint": {
"@type": "ContactPoint",
"telephone": "+1-555-010-0199",
"email": "support@example.com",
"contactType": "customer support",
"availableLanguage": ["English"]
}
}
</script>Use LocalBusiness fields if you have a location
For a physical business, change @type to your subtype and add address, telephone, geo and openingHoursSpecification. The address must match your Google Business Profile exactly. If you have several branches, add a separate block with its own @id on each location page.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Dentist",
"@id": "https://example.com/#organization",
"name": "Example Co Dental",
"url": "https://example.com/",
"logo": "https://example.com/images/logo-512.png",
"image": "https://example.com/images/clinic-front.jpg",
"telephone": "+1-555-010-0199",
"priceRange": "$$",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Main Street",
"addressLocality": "Springfield",
"addressRegion": "IL",
"postalCode": "62701",
"addressCountry": "US"
},
"geo": { "@type": "GeoCoordinates", "latitude": 39.7817, "longitude": -89.6501 },
"openingHoursSpecification": [{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
"opens": "08:00",
"closes": "17:00"
}],
"sameAs": ["https://www.facebook.com/exampledental"]
}
</script>Add the block to your homepage or global head
Paste the script inside the <head> of your homepage, or in the shared layout so it loads on every page. One page with valid markup is enough to pass this check. Google recommends the homepage as the main place for Organization markup.
On a CMS, use the built-in schema settings or the theme's layout file. Details for each platform are in the notes below.
Remove duplicate or conflicting Organization blocks
SEO plugins, themes and apps often output their own Organization markup already. View the page source and search for "@type": "Organization" or your LocalBusiness type. If you find two blocks with different names or logos, keep one source and turn off the other.
com/#organization"}`.
"publisher": { "@id": "https://example.com/#organization" }Validate and re-run the audit
Paste your homepage URL into Google's Rich Results Test at search.google.com/test/rich-results and confirm it detects Organization or LocalBusiness with no errors. Then check the same URL in the Schema Markup Validator at validator.schema.org, which reports schema.org issues that Google's tool skips. Clear any page or CDN cache before testing, then re-run this audit.
curl -s https://example.com/ | grep -o '"@type": *"[A-Za-z]*"'
Platform-specific notes
WordPress
Use the SEO plugin you already run rather than hand-coding. Yoast SEO: Yoast SEO → Settings → Site representation. Choose Organization, upload the logo and add profiles under Other profiles. Rank Math: Rank Math SEO → Titles & Meta → Local SEO. Set Person or Company, the logo, the URL and contact details; the Local SEO module adds LocalBusiness fields. If you have no plugin, put the script in your child theme's header.php before </head>, or use a code snippets plugin hooked to wp_head.
Shopify
Many themes, including Dawn and other Online Store 2.0 themes, already output Organization markup on the homepage using the logo and social links from Theme settings. Fill those in first under Online Store → Themes → Customize → Theme settings → Social media and the header logo. If view-source shows no Organization type, add the block under Online Store → Themes → Edit code → layout/theme.liquid inside <head>. You can wrap it in {% if request.page_type == 'index' %} ... {% endif %} and use {{ shop.name }} and {{ shop.url }} for the values.
Wix
Open the homepage in the Editor and go to Pages & Menu → (homepage) ⋯ → SEO basics → Advanced SEO → Structured data markup → Add new markup. Paste the JSON only, without the <script> tags. Wix also adds some LocalBusiness markup automatically from Settings → Business info, so check view-source for duplicates.
Webflow
Go to Site settings → Custom code → Head code to add the block site-wide, or Page settings → Custom code → Inside <head> tag to add it to the homepage only. Custom code requires a paid site plan, and the change only goes live after you publish.
Next.js
In the App Router, render the script in app/layout.tsx (site-wide) or app/page.tsx (homepage only). Use dangerouslySetInnerHTML={{ __html: JSON.stringify(data).replace(/</g, '\\u003c') }} so the JSON is server-rendered and safely escaped. Do not inject it with client-side useEffect: crawlers and audit tools that skip JavaScript won't see it.
Check that it worked
✅ How to verify
- Google Rich Results Test on the homepage shows an Organization or LocalBusiness item with 0 errors.
- validator.schema.org lists your chosen @type with name, logo, sameAs and contactPoint parsed correctly.
- View-source (not DevTools Elements) of the live homepage contains the <script type="application/ld+json"> block, which proves it is in the server HTML.
- Re-running this audit reports: Organization (or LocalBusiness) schema found.
⚠️ Common mistakes
- Adding the markup with Google Tag Manager or client-side JavaScript. Many crawlers and AI bots never execute that script, so the schema is invisible to them.
- Using a relative or blocked logo URL (for example /logo.png, or a CDN path that robots.txt disallows) instead of an absolute, crawlable https URL.
- Leaving two conflicting Organization blocks live, typically one from a theme and one from a plugin, each with a different name or logo.
- Listing profiles you don't control, or placeholder values like "Example Co", in sameAs and contactPoint.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
Do I need Organization schema on every page?
No. Google recommends placing it on the homepage or an About page, and one valid instance is enough. Adding it site-wide through the layout is fine too, as long as the content is identical everywhere.
Should I use Organization or LocalBusiness schema?
Use LocalBusiness or a subtype like Restaurant, Store or Dentist if customers visit a physical address or you serve a defined local area. Otherwise use Organization. LocalBusiness is a subtype of Organization, so it covers both roles.
What size should the logo be in Organization schema?
Google requires at least 112×112 pixels in a supported format (PNG, JPG, GIF, SVG, WebP). A square image around 512×512 px works well, and the logo should be readable on a white background.
Will Organization schema give me a knowledge panel?
Not on its own. It helps Google confirm your logo, name and official profiles, and those signals feed knowledge panels and brand results, but whether a panel appears depends on Google's assessment of your entity.
How to Fix Missing WebSite Schema (JSON-LD Guide)
How to Fix Structured Data Errors on Your Website
How to Fix Missing Product and Article Schema (JSON-LD)
How to Fix Index Coverage Gaps in Google Search Console
How to Fix Missing Security Headers (CSP, Referrer-Policy)
How to Fix Conflicting Canonical and Noindex Tags