Organization Schema Markup: Set Up Your Business Identity

Key takeaways

• Confirm which business or group the site represents before adding code.
• Choose the most specific type that fits the actual organization.
• Keep business facts and publisher references consistent across templates.
• Pair dedicated schema tests with a broader review of page quality.

Organization schema markup describes the business or group behind a website. Start with correct business facts. Choose the right type and link the markup to a clear source. Then test the live page. Add more fields only when they say something true and useful.

This guide covers the business behind the site. Each blog post has its own data too. For a guide to the main types and formats, read our structured data for SEO guide.

Decide which organization the site represents

Before writing code, ask who runs this site. A brand name, legal company name, and product name can differ. Work out those roles with the business owner. A product with a landing page is not always a company of its own.

Think of a small firm that posts repair tips under the brand Example Repair Guides. The firm has a longer legal name. Both names refer to the same firm. The team needs a clear rule for when to use each name. This is a made-up example, not a claim about a real firm.

Build a short facts sheet with the owner. List the public name, legal name if needed, main website, logo file, and public contact route. Add links to the firm’s own profiles. Give each fact a source. Name the person who can approve changes. That sheet is more useful than a long block of guessed data.

Choose Organization or a more specific subtype

Organization is a broad Schema.org type. Google recommends the most specific suitable subtype. Its Organization guidance points online stores toward OnlineStore and local businesses toward the relevant LocalBusiness subtype and its own rules. For the items sold by an online store, choose and test Product and Offer data as a separate task from the store identity.

Choose based on the real business. A blog that reviews tools is not an online store just because it links to products. A firm with local clients should check how it works before choosing a local type.

Write down why the type fits. Your wish for more traffic should not drive this choice. The code should describe the business you run today. If the site adds a store or a new branch, review the model then.

Find the existing source before adding markup

Check the homepage and About page for Organization output. Look inside an @graph too. Your CMS, theme, or SEO plugin may already create it. Find the settings for the name, logo, and main URL before adding a new block.

Compare the output with your facts sheet. A common review task is to find an old logo path or a staging domain left after launch. Fix the shared setting that produces the wrong value. Pasting a correct version beside it can leave two competing descriptions.

Use our WordPress schema conflict guide when several tools disagree. The goal here is a stable business identity, not to replace every other kind of markup on the site.

Build a small Organization JSON-LD example

This sample describes the firm in our made-up example. The name, website, logo, and contact details are not real. It leaves out a street address and business ID codes. Add such details only when they apply and you can check them.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.com/#organization",
  "name": "Example Repair Guides",
  "legalName": "Example Repair Guides Company",
  "url": "https://example.com/",
  "logo": "https://example.com/assets/logo.png",
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer support",
    "email": "support@example.com"
  }
}

A developer can put this object in a script element with type application/ld+json. In a CMS, use the built-in setup if it can read the right business fields. Do not paste made-up details into a live template.

The @id gives this entity a stable reference in the data model. Other items can refer to the same firm. You do not need a new company for every post. Agree on this ID with the developer. Use the same one when you edit templates.

Review names, logos, and profile links

Google has no required Organization properties in this guide. Add applicable facts. It recommends the homepage or one page about the organization; every page does not need a full copy. For logos, Google specifies at least 112 by 112 pixels, crawler access, and a supported image format. It also advises checking the logo on white.

Open your actual logo file, not just the filename in the editor. Check that it is the approved brand asset. A transparent white mark may work in your dark site header yet vanish on a white background. Ask the brand owner which version to use rather than changing the colors by guesswork.

The sameAs property links to pages that identify the same entity. Add a genuine company profile when it belongs to this business. Do not fill it with clients, suppliers, or articles that merely mention your brand. It is not a list of backlinks to build.

Keep a note of who runs each profile. The firm may change its name, domain, or social account. Your note then gives the team a clear list to update. Before you remove an old link, check what took its place.

Connect the publisher to articles without mixing roles

An organization can publish a blog while a named person writes a post. Those are different roles. Do not replace every writer with the company name just to make the markup uniform. Check the visible byline and the intended publisher separately. For the people who write the posts, connect author profiles to their articles rather than treating each writer as the company.

A developer may use the organization’s stable reference when connecting an article to its publisher. Confirm that the reference points to the same business identity across templates. Our Article schema markup guide covers the post-level fields.

For pages in other languages, keep the same business identity. Use the right local page content too. A site with three languages does not need three made-up firms. Ask the owner to check any local brand names before you change shared fields.

Test the live output and keep an update record

Use the Schema Markup Validator to review the entities and their values. Use Google’s Rich Results Test for supported search features, then inspect the public URL. These checks have different scopes. A valid Organization description does not guarantee a knowledge panel or a chosen logo in search. When checking the wider page template, also build and test a breadcrumb trail as a separate navigation task. If a report flags the business markup, fix and validate Search Console schema issues against the live output.

Save the tested URL, date, expected name, logo path, and findings. Recheck the homepage after a template change. Compare one post that refers to the publisher too. This small set helps catch gaps between site settings and post templates.

DEX Health can help you review the wider page quality and SEO, including on the free plan. Pair that review with dedicated schema tests. A strong Health score is not proof that a search engine has accepted the business identity or will display it in a certain way.

Put one person in charge of the business facts sheet. Update it when the firm changes its public contact route, logo, or main website. Then check the live output again. Explore DEX if you want page checks alongside your content work. Keep the focus on clear pages with facts that readers can trust.

FAQ

Should I add private company details to complete the example?

+

Use accurate, applicable information intended for public use. A long sample is not a reason to expose private contact details or guess an identifier you cannot verify.

Who should approve a change to the organization name?

+

Ask the business owner or person responsible for the brand. Record the approved name and where it is used before editing shared site settings.

What should I check after replacing the logo?

+

Open the new image file, review it on the page, and confirm that the live markup points to it. Check one article template as well if it uses the same publisher data.

Sources

1. Organization structured data · Google

Dex SEO

Dex SEO is an AI SEO agent for small businesses. Every article here is planned from search data, drafted by Dex, fact-checked against the sources it cites, and reviewed by the team before it is published.

How this article was made: planned and drafted by Dex from search data, fact-checked by Dex (6 claims checked), then approved by the Dex SEO team.