Organization

Name: Organization
Author: thedaviddias

thedaviddias/frontendchecklist

1 installs
73.4k repo stars
Updated June 18, 2026
thedaviddias/frontendchecklist

Checks the homepage for Organization JSON-LD with name, url, logo, and sameAs, and adds a valid schema block for the Knowledge Panel.

About

Audits the homepage for Organization schema markup that helps Google populate the Knowledge Panel with logo, social links, and contact details. A developer uses it when auditing structured data on a business or brand homepage.

Add Organization JSON-LD to the homepage only
Include name, url, logo, and sameAs social profiles

Organization by the numbers

1 all-time installs (skills.sh)
Ranked #1,710 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
Data as of Aug 5, 2026 (Skillselion catalog sync)

npx skills add https://github.com/thedaviddias/frontendchecklist --skill organization

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/thedaviddias/frontendchecklist/organization.svg)](https://skillselion.com/skills/thedaviddias/frontendchecklist/organization)

Installs	1
repo stars	★ 73.4k
Last updated	June 18, 2026
Repository	thedaviddias/frontendchecklist ↗

What it does

Checks the homepage for Organization JSON-LD with name, url, logo, and sameAs, and adds a valid schema block for the Knowledge Panel.

Files

SKILL.mdMarkdownGitHub ↗

Add Organization schema markup

Organization schema helps Google understand your brand, populate your Knowledge Panel with accurate information (logo, social links, contact details), and improve brand-related search appearance.

Quick Reference

Add Organization JSON-LD schema to your homepage (and only the homepage)
Required: name, url, logo — all other properties strengthen your Knowledge Panel
sameAs links to social profiles help Google confirm your brand identity
Use a persistent logo URL that won't change; it appears in Google's Knowledge Panel

Check

Check the homepage for a JSON-LD script block with @type 'Organization' or 'Corporation'. Verify it includes: name, url, logo (with @type ImageObject), and sameAs array with social profile URLs. Validate with Google's Rich Results Test.

Fix

Add an Organization schema JSON-LD block to the homepage <head>. Include name, url, logo (ImageObject with url, width, height), contactPoint, and sameAs array pointing to your official social media profiles and Wikipedia/Wikidata entries if available.

Explain

Organization structured data tells Google who you are as a brand. Google uses it to populate the Knowledge Panel in search results—the box showing your logo, social profiles, and contact info that appears for branded queries. Without it, Google has to guess this information from unstructured content.

Code Review

Check the homepage for a JSON-LD script with @type 'Organization' or 'Corporation'. Verify: name matches the site's official brand name, url matches the site's canonical-url homepage URL, logo.url is an absolute HTTPS URL pointing to an actual image, sameAs array contains at least 2 verified social profiles. Validate with Google's Rich Results Test. Confirm Organization schema is NOT duplicated on interior pages.

---

For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/en/rules/seo/organization

Add Organization schema markup

Validates Organization schema for brand presence

Priority: medium · Difficulty: intermediate · Time: 15 min

--- Organization schema is JSON-LD markup that describes your brand to search engines. Google uses it to populate the Knowledge Panel for branded searches — the info box that appears on the right side of search results.

Code Examples

<!-- ✅ Good: Complete Organization schema on homepage -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Acme Corporation",
  "url": "https://acme.com",
  "logo": {
    "@type": "ImageObject",
    "url": "https://acme.com/images/logo.png",
    "width": 200,
    "height": 60
  },
  "description": "Acme Corporation makes innovative tools for professionals.",
  "foundingDate": "2010",
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-555-000-0000",
    "contactType": "customer service",
    "availableLanguage": ["English", "Spanish"]
  },
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "1 Acme Way",
    "addressLocality": "San Francisco",
    "addressRegion": "CA",
    "postalCode": "94105",
    "addressCountry": "US"
  },
  "sameAs": [
    "https://www.linkedin.com/company/acme",
    "https://twitter.com/acme",
    "https://www.facebook.com/acme",
    "https://www.youtube.com/@acme",
    "https://en.wikipedia.org/wiki/Acme_Corporation"
  ]
}
</script>

<!-- ❌ Bad: Missing logo and sameAs — minimal value -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Acme"
}
</script>

Why It Matters

Organization schema helps Google understand your brand, populate your Knowledge Panel with accurate information (logo, social links, contact details), and improve brand-related search appearance.

Required Properties

Property	Type	Example
`@type`	Text	`"Organization"` or `"Corporation"`
`name`	Text	`"Acme Corporation"`
`url`	URL	`"https://acme.com"`
`logo`	ImageObject	see below

Recommended Properties

Property	Purpose
`sameAs`	Links to social profiles — helps Google verify identity
`contactPoint`	Customer service phone/email
`foundingDate`	Year founded
`numberOfEmployees`	Company size
`address`	Headquarters address
`description`	Short organisation description

Logo Requirements

Google's logo guidelines for Organization schema:

Recommended size: at least 112×112 px, up to 1000×1000 px
Aspect ratio should be square-ish (not extremely wide banners)
Use a stable, permanent URL (no CDN versioning that changes frequently)
JPEG, PNG, or WebP formats

Next.js Implementation

// app/page.tsx (homepage only)

  const orgSchema = {
    '@context': 'https://schema.org',
    '@type': 'Organization',
    name: 'Acme Corporation',
    url: 'https://acme.com',
    logo: {
      '@type': 'ImageObject',
      url: 'https://acme.com/logo.png',
      width: 200,
      height: 60,
    },
    sameAs: [
      'https://www.linkedin.com/company/acme',
      'https://twitter.com/acme',
    ],
  }

  return (
    <>
      <script
        type="application/ld+json"
        dangerouslySetInnerHTML={{ __html: JSON.stringify(orgSchema) }}
      />
      {/* page content */}
    </>
  )
}

Placement

Place Organization schema only on the homepage. Adding it to every page dilutes its signal and may confuse crawlers. If you also use LocalBusiness schema, it can coexist on the same page.

Validation

Test with Google's Rich Results Test to confirm valid markup.

Exceptions

Only add or enforce schema types that the page can truthfully support; irrelevant structured data is worse than no structured data.
A technically valid schema block can still be misleading if the page content does not visibly back it up; audit rendered content and schema together.
If indexability, canonical-url, or main content quality is wrong, fix that foundation before optimizing schema details.

Verification

Automated Checks

Inspect rendered HTML and HTTP headers to confirm the expected metadata or crawlability signal is present.
Test the affected URL with Google Search Console or equivalent tooling where relevant.
Re-crawl a representative page set after deployment.