Organization schema markup: Crawl Audit check 7

Short answer: Organization structured data is a small block of JSON-LD that states, in a form machines read directly, who runs the site: name, logo, address, phone and the profiles that belong to you. Google says it helps it understand your organisation and tell it apart from others with similar names, and it can influence the logo shown in Search and in your knowledge panel. Crawl Audit check 7 passes when a page carries any Organization-type node.

What Crawl Audit checks

Crawl Audit reads every <script type="application/ld+json"> block on the page, plus any microdata itemtype, and walks into nested nodes and @graph arrays. The check passes if it finds a node whose @type is one of these: Organization, Corporation, LocalBusiness, OnlineStore, OnlineBusiness, NGO, EducationalOrganization, MedicalOrganization, ProfessionalService, Store, Restaurant or NewsMediaOrganization. Otherwise it fails.

One thing to know: the match is on those exact names. schema.org has hundreds of narrower types, such as Plumber or Dentist, and a node typed only as one of those won't count here. The fix is easy and valid schema.org: give the node both types, for example "@type": ["LocalBusiness", "Plumber"].

What Google does with it

Google's Organization documentation says the markup "can help Google better understand your organization's administrative details and disambiguate your organization in search results", and that it can influence "which logo is shown in Search results and your knowledge panel".

There are no required properties. Google's words: "There are no required properties; instead, we recommend adding as many properties that are relevant to your organization." The ones worth your time for a small business:

• name, url and logo. Google says the logo "must be 112x112px, at minimum."
• sameAs: links to your real profiles, such as LinkedIn or Instagram. Google describes it as "a URL to your organization's profile page on a social media or review site", and you can list several.
• telephone and address. For the phone, Google says: "Be sure to include the country code and area code."
• legalName if your trading name differs from the registered company.

A minimal block, from Google's own example:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "url": "https://www.example.com",
  "name": "Example Corporation",
  "logo": "https://www.example.com/images/logo.png"
}
</script>

On this site we go one step further and give the node an @id (https://devmarde.com#organization). Every page, article and product then points to that one ID instead of describing the company again. It's how one company stays one entity across all 310 URLs in our sitemap, instead of 310 slightly different descriptions.

How to add it on your platform

• WordPress with Yoast SEO: go to Yoast SEO › Settings › Site representation and choose whether the site represents an organisation or a person. Then fill in the name, logo and social profiles. Yoast outputs the Organization node on every page.
• WordPress with Rank Math: make sure the Schema (Structured Data) module is on under Rank Math SEO › Dashboard, then fill in your organisation details in its settings.
• Shopify: Shopify's Dawn theme outputs an Organization node from header.liquid, using your shop name, logo and the social links in your theme settings. Fill those settings in; there's no code to write.
• Wix: Wix adds Local Business markup to your homepage automatically. To add your own, open the page's SEO settings, then the Advanced SEO tab, then Structured Data Markup. Wix accepts JSON-LD only, up to five markups per page.
• Squarespace: Squarespace generates Organization markup automatically, and you can't edit or remove it. Keep your business name, logo and social links in site settings up to date, because that's what it uses.
• Next.js: render a <script type="application/ld+json"> tag in your root layout. The Next.js docs recommend escaping < in the JSON (JSON.stringify(data).replace(/</g, "\\u003c")) to prevent script injection.

Common mistakes

• A logo smaller than 112 by 112 pixels. Google's minimum.
• Phone numbers without a country code. Use the full international form, such as +92 306 072 0072.
• sameAs pointing at someone else's profile. Only list profiles you own. If a similar-looking handle belongs to someone else, leave it out.
• Two different Organization nodes on one page, often one from a plugin and one from the theme, each with a different name or logo. Pick one source.
• Marking up content that isn't on the page. Google's structured data policies say: "Don't mark up content that is not visible to readers of the page." Your name, phone and address should be visible on the site too.

To see what Google reads, paste your homepage into Google's Rich Results Test.

Sources

• Google Search Central, Organization structured data (updated 8 September 2026), checked 3 October 2026.
• Google Search Central, General structured data guidelines.
• Yoast, Site representation: organization or person; Rank Math, Rich snippets.
• Wix, Adding structured data markup; Squarespace, Structured data; Next.js, JSON-LD.