Skip to content
50% OFF $299 $599
Lock in
§ 3.10 ARTICLE
Published VerifiedEvery 6 weeks Sources2 named Authored bySquareRank Team

Schema · § 3.10 · How-to

Organization schema on Squarespace

Organization is the Schema.org type for the brand behind a website. Google's canonical documentation1 lists zero required fields and recommends name, url, logo (a crawlable image, 112x112 pixels minimum, clear on white), and sameAs (an array of URLs to verified social and platform profiles). The pattern installs site-wide via Settings > Advanced > Code Injection > Header. When the business has a physical address or service area, use the LocalBusiness subtype instead; for pure remote or digital businesses, plain Organization is correct.

Organization is the entity that publishes every Article (Article.publisher), owns every Service (Service.provider), and runs the site behind every Product (the implicit catalog owner). Without an Organization schema, all of those references resolve to a name string rather than an entity. With one, Google and AI engines can confidently identify and disambiguate the brand.

What Organization schema is

Organization is the Schema.org type for any group, company, association, or institution. The inheritance chain runs Thing > Organization, with subtypes for specific institutional shapes: LocalBusiness (physical location), Corporation, NGO, EducationalOrganization, MedicalOrganization, GovernmentOrganization. The properties most worth installing on a Squarespace site: name, url, logo, sameAs, description, contactPoint, foundingDate, founder.

The mental model: Organization describes the brand entity behind the site. The entity is referenced from every other schema block on the site — Article.publisher, Service.provider, Product.brand, Event.organizer all resolve to this one Organization. Installing it once site-wide means every reference elsewhere on the site has a real entity to resolve to.

When to use Organization (vs LocalBusiness)

Use Organization when the business has no physical address customers visit and no defined geographic service area — a remote consulting firm, an online education business, a digital agency serving clients globally, a SaaS company. Use LocalBusiness instead when there's a real-world address or service area — a therapy practice, a restaurant, a photographer with a studio. The two are mutually exclusive at the top level; LocalBusiness inherits from Organization, so the LocalBusiness schema implicitly carries Organization properties.

A common confusion: a remote founder running a remote business who wants the brand to show up in local search for their home city. Schema-wise, this is Organization, not LocalBusiness, because there's no customer-visitable location. The local search lift comes from Google Business Profile (as a service-area business), not from forcing LocalBusiness schema onto a non-local entity. The two channels are independent.

Rich-results status in 2026

Organization schema does not produce a specific Google rich-result enhancement. Its visible benefits are knowledge-panel surfacing for the brand (when sufficient external signal also exists) and the brand logo appearing next to the site name in search results. The bigger 2026 win is AI engine attribution: a confidently-identified Organization with a sameAs graph gives AI engines a clean entity to attribute citations to, reducing 'an article on yoursite.com' attribution to 'an article by [Your Brand]'.

Organization schema in 2026

0

required fields. Everything Google recommends is technically optional.

Google Search Central · 2025-12-10
112px

minimum logo dimension on each side per Google's documentation, crawlable and clear on white.

Google Search Central · 2025-12-10
sameAs

the property that does most of the work — verified URLs to LinkedIn, X/Twitter, Facebook, Wikidata.

Schema.org · 2026-03-19

Required and recommended fields

Schema.org and Google both define zero hard required properties on Organization. The useful minimum: name, url, logo, sameAs. Recommended expansion for serious entity wiring: description, contactPoint (a ContactPoint with email and contactType), foundingDate, founder (referencing the Person), address (when the entity has a registered address), areaServed (when relevant).

  • name — the brand name as the business uses it.
  • url — the canonical home page.
  • logo — URL to a crawlable logo image, 112x112 pixels minimum.
  • sameAs — array of URLs to verified profiles: LinkedIn company page, X/Twitter, Facebook, YouTube, GitHub, Wikidata Q-ID.
  • description — a 1-2 sentence brand description.
  • contactPoint — a ContactPoint object with email, telephone, contactType.
  • foundingDate — ISO 8601 date string.
  • founder — a Person object (or a reference to the Person at /founder/).

Copy-paste JSON-LD example

The block below is a complete Organization schema for SquareRank itself, mirroring what ships site-wide on this site. Replace name, url, logo, founder, and sameAs with your real values. The founder reference points to the canonical Person bio at /founder/ — referencing rather than redefining keeps the entity graph clean.

JSON-LD Organization schema for SquareRank — the live site-wide pattern 
 <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Organization", "name": "SquareRank", "url": "https://squareranked.com/", "logo": "https://squareranked.com/images/logo.png", "description": "Done-for-you Squarespace SEO, AEO, and GEO install. $299 one-time, 7 business days, 14-day Walk-Away Guarantee.", "founder": { "@type": "Person", "name": "Billy Reiner", "url": "https://squareranked.com/founder/" }, "sameAs": [ "https://www.linkedin.com/in/billyreiner", "https://github.com/billyrei" ], "contactPoint": { "@type": "ContactPoint", "email": "[email protected]", "contactType": "customer support" } } </script>

Where to paste it on Squarespace

Organization goes site-wide because the brand entity doesn't change page to page. Open Settings > Advanced > Code Injection > Header. Paste the entire script block including the wrapping script tags. Save. Verify by viewing source on any page (not just the home page) and confirming the Organization block appears once.

A common mis-install: pasting Organization into the home page's Page Settings Code Injection instead of the site-wide field. The schema then fires only on the home page, which means — on every deep page — the publisher and brand references in other schema blocks resolve to a name string rather than an entity. Site-wide placement is the correct pattern; the brand doesn't change per page.

Validation steps

Run the home page URL through Google's Rich Results Test. Confirm Organization is detected. Confirm the logo URL resolves and the image meets the 112x112 minimum. Warnings about missing recommended fields (no foundingDate, no contactPoint) are informational, not errors. The success signal is structural validity plus a working logo URL.

A second check worth running: click through every sameAs URL manually and confirm each one resolves to a profile that visibly identifies the brand. A LinkedIn URL pointing at a company page that doesn't exist anymore breaks the entity graph and is worse than no sameAs at all.

Common gotchas on Squarespace

Three gotchas catch most Organization installs. First: logo image too small or hosted on a domain that blocks Googlebot — the schema parses but the visible logo enhancement doesn't surface. Use a 200x200+ logo on the same domain as the site. Second: Organization vs LocalBusiness confusion — installing Organization when the business has a physical address weakens the local-search signal. Third: stale sameAs links — an abandoned Twitter account or 404'd LinkedIn profile weakens the entity graph instead of strengthening it.

A fourth gotcha worth naming for sites with both Organization and LocalBusiness needs: the two should not both be top-level entities on the same page. LocalBusiness inherits from Organization, so a single LocalBusiness block carries everything Organization does. Two parallel top-level entities (one Organization, one LocalBusiness) for the same brand confuses the entity graph and produces “which is the canonical entity” ambiguity. Pick one and link the other via @graph.

Organization is referenced from many places: Article.publisher, Service.provider, Product.brand (as a Brand object, which is an Organization subtype), Event.organizer. Internally, Organization references Person via founder and employee. The relationship is bidirectional — Person.worksFor points at Organization, Organization.founder points at Person.

Keep reading · § 3.10