Organization schema: how to add it and what to include

Google's documentation lists recommended properties; none are strictly required, but more accurate detail helps.

Place a script element with type application/ld+json in the page head or body. Inside, use @context set to https://schema.org, @type Organization, and an @id such as your homepage URL with #organization. Add the properties above. Other structured data on the site, such as WebSite, Article publisher, or SoftwareApplication provider, can reference the organisation by the same @id rather than repeating it. That keeps every page describing the company identically.

Google recommends placing Organization markup on the homepage or a page about the organisation; it does not need to be on every page. Sites with a shared head template often include it site-wide, which is also acceptable if the values are identical everywhere. On serionflow.com the Organization, WebSite, and SoftwareApplication blocks are defined once in the shared document head, and individual pages reference them by @id.

Search engines use Organization data to connect your site with your official profiles and to understand basic facts about your company, which feeds knowledge panels. AI systems that rely on search indexes benefit from that clarity indirectly. The schema is most useful when it reinforces facts stated consistently in visible text across your site and profiles; it cannot fix inconsistent descriptions elsewhere.

Logo URLs that are blocked, redirect, or point to an SVG that cannot be processed. sameAs links to profiles you do not control or that no longer exist. Different names or descriptions on different pages. Several conflicting Organization blocks with the same @id. Validate with the Rich Results Test and the Schema.org validator. Our free schema builder and validator generates Organization JSON-LD from a form and checks existing markup on a live page.