Organization Schema: What to Add to Your Home Page (And What Google Does With It)

Organization schema is a block of structured data, usually JSON-LD on your home page, that states who is behind a website: its name, URL, logo, and the profiles that belong to it elsewhere on the web. Google's documentation says the markup can help it "better understand your organization's administrative details and disambiguate your organization in search results." It has no required properties, it belongs on one page rather than all of them, and it is site-level information rather than a per-post enhancement. For most blogs it is a fifteen-minute job that is worth doing once and then leaving alone.

What Organization Schema Actually Does

Most structured data describes a page: this is an article, this is a recipe, this is a breadcrumb trail. Organization markup describes the publisher instead. That difference explains both its value and its limits.

Google lists two uses. The first is disambiguation — connecting your site to the right entity when your name is shared with other companies, products, or people. The second is presentation: the logo property, in Google's words, helps it understand "which logo you want to show, for example in Search results and knowledge panels."

What it does not do is hand you a visible upgrade on demand. Google's structured data guidelines are blunt about this: "Google does not guarantee that your structured data will show up in search results, even if your page is marked up correctly." A new blog should not expect a knowledge panel because it added twelve lines of JSON-LD. The markup removes ambiguity about who you are; it does not create prominence you haven't earned yet.

Which Properties Should a Blog Include?

Google's instruction is short: "There are no required properties; instead, add the properties that apply to your organization." The documented list is long because it also serves retailers and large companies — tax IDs, employee counts, return policies, shipping services. A blog needs only a handful.

| Property | What it holds | Worth adding for a blog? | |---|---|---| | name | The name you publish under | Yes — keep it identical to your site name | | url | Your home page URL | Yes | | logo | An image URL for your logo | Yes, if you have one | | sameAs | Your profiles on other sites | Yes — one entry per profile | | description | A plain description of what you publish | Optional | | alternateName | An acronym or shorter name | Only if people really use it | | contactPoint / email | How readers can reach you | Only if it is shown on the site | | address, telephone, taxID, numberOfEmployees | Business details | Skip unless you are a registered business that publishes them |

Two of these have rules attached. The logo must be at least 112x112 pixels, sit at a crawlable and indexable URL, and look right on a pure white background — a white or pale gray logo exported with transparency can all but vanish. And for name, Google asks you to use the same name and alternateName that you use for your site name, so the organization and the site name shown in results don't disagree.

A Minimal Organization JSON-LD Example

This covers everything a typical blog needs. Swap in your own values and place it in the HTML of your home page:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Blog",
  "url": "https://www.example.com",
  "logo": "https://www.example.com/images/logo.png",
  "description": "Practical guides to growing a small blog with search traffic.",
  "sameAs": [
    "https://x.com/exampleblog",
    "https://www.youtube.com/@exampleblog",
    "https://www.linkedin.com/company/exampleblog"
  ]
}
</script>

On WordPress you rarely need to write this by hand. Yoast SEO generates it from Yoast SEO → Settings → Site representation, where you choose between an organization and a person, then enter a name, a logo, and social profiles. Rank Math has the equivalent under Rank Math SEO → Titles & Meta → Local SEO, with a Person or Company choice. If one of those is already filled in, view your home page source before adding anything — a second, hand-written block with slightly different values is worse than none.

Organization or Person: Which One Fits a Blog?

If a company, a team, or a brand name publishes the blog, use Organization. If the site is you, writing under your own name, schema.org's Person type describes that more honestly, and both major WordPress SEO plugins offer it as the alternative choice. Don't declare an organization that doesn't exist just because the documentation is written for one.

The same distinction shows up in Google's Article guidance, which tells you to "use the Person type for people, and the Organization type for organizations" when marking up an author. A consistent setup for a solo blogger is a Person on the home page or about page, with each post's author pointing to that same person and a URL that identifies them.

Google also recommends "the most specific schema.org subtype of Organization that matches your organization." A blog that is really the content arm of a shop should use OnlineStore; a clinic, studio, or restaurant should use the matching LocalBusiness subtype. Plain Organization is the right answer only when nothing narrower fits.

Where Does the Markup Go?

One page. Google recommends "placing this information on your home page, or a single page that describes your organization, for example the about us page," and adds: "You don't need to include it on every page of your site."

That is a real difference from breadcrumb or article markup, which belongs on every page it describes. Repeating full organization details site-wide doesn't break anything, but it multiplies the places where the name, logo URL, or profile list can drift out of sync after a redesign.

Common Organization Schema Mistakes

1. Two blocks that disagree. A theme, an SEO plugin, and a hand-pasted snippet can each emit their own Organization. Search your home page source for "@type": "Organization" and make sure there is one definition.
2. A logo Google can't use. Too small, blocked by robots.txt, or invisible on white. Open the logo URL in a private window to confirm it loads without a login.
3. A name that doesn't match the site. If the title tag, the visible header, and the markup each use a different spelling, you have added ambiguity instead of removing it. The same care applies to duplicate title tags.
4. Details that aren't on the page. Google's guidelines say "Don't mark up content that is not visible to readers of the page." A phone number or address that exists only inside the JSON-LD doesn't belong there.
5. Dead sameAs links. An abandoned profile or a renamed handle points Google at a page that no longer describes you. Prune the list when you close an account.

How to Test It and Tell Whether It Worked

Run the home page URL through Google's Rich Results Test to catch syntax errors and unreadable properties, and use a general-purpose schema markup validator if you want the full schema.org vocabulary checked rather than only what Google consumes. Test the live URL, not a pasted snippet, so you see what a crawler actually receives.

Measuring the effect is harder, because there is no before-and-after snippet to compare. The signal to watch is branded search: in Search Console's Performance report, filter queries by your blog's name and look at impressions, clicks, and CTR over the following months. Traffic Monitor collects those Search Console numbers daily, so a change in how your brand queries perform shows up as a trend instead of something you have to remember to check.

Is Organization Schema Worth Adding?

Yes, with modest expectations. It costs minutes, it is supported by current Google documentation, and unlike FAQ schema — whose rich result Google retired in 2026 — it isn't built around a single rich result that can be switched off. It simply states facts about who publishes the site.

Don't expect it to lift rankings on its own, or to produce a knowledge panel for a site nobody searches for by name. Add one accurate block to your home page, keep the name and logo consistent everywhere else, and spend the rest of your effort on what makes people search for you in the first place.