sameAs · Recommended · Critical for AEO
The sameAs field is an array of URLs pointing to official profiles and pages that represent your organization across the web. LinkedIn company page, Wikipedia article, Crunchbase profile, Twitter/X account, GitHub organization, Clutch listing, Google Business Profile, and any other authoritative page where your brand has a verified presence.
Google uses sameAs to populate the social links section of your Knowledge Panel. AI answer engines use it for something more fundamental: verifying that your organization is a real, known entity with a presence beyond your own website.
sameAs is the proof layer of your entity graph. When an AI retrieval system evaluates whether to cite your content, it checks if the publisher entity resolves to a known organization in its knowledge base. The name field makes a claim ("We are Stripe"). The sameAs array provides the evidence ("Here is our LinkedIn with 500K followers, our Wikipedia article, our Crunchbase profile with funding data"). Without sameAs, your Organization schema is an unverified assertion. With it, AI engines can cross-reference your entity across multiple trusted sources and assign a higher confidence score for citation.
This is the structured data version of E-E-A-T. Google talks about Experience, Expertise, Authoritativeness, and Trust as qualitative concepts. sameAs is how you express authoritativeness in machine-readable format.
Schema.org defines sameAs as a property of Thing (inherited by Organization) that accepts an array of URLs.
Google explicitly documents sameAs in their Organization structured data guidelines and uses it for Knowledge Panel social links and entity verification.
Collect URLs for every official profile your organization maintains. Only include profiles you control and that are actively maintained.
| Platform | URL format |
|---|---|
https://www.linkedin.com/company/your-company | |
| Wikipedia | https://en.wikipedia.org/wiki/Your_Company |
| Crunchbase | https://www.crunchbase.com/organization/your-company |
| Twitter/X | https://twitter.com/yourcompany |
| GitHub | https://github.com/yourcompany |
| Platform | URL format |
|---|---|
https://www.facebook.com/yourcompany | |
https://www.instagram.com/yourcompany | |
| YouTube | https://www.youtube.com/@yourcompany |
| Clutch | https://clutch.co/profile/your-company |
| G2 | https://www.g2.com/products/your-product |
| Platform | Best for |
|---|---|
| Webflow Partner Directory | Webflow agencies |
| Dribbble | Design agencies |
| Behance | Creative agencies |
| AngelList | Startups |
| Glassdoor | Employers |
Type: Array of URLs
Pattern: Each element is a full HTTPS URL to an authoritative profile
"sameAs": [
"https://www.linkedin.com/company/stripe",
"https://twitter.com/stripe",
"https://en.wikipedia.org/wiki/Stripe_(company)",
"https://github.com/stripe"
]Single profile (still use array format):
"sameAs": ["https://www.linkedin.com/company/your-company"]Add the sameAs array inside your Organization schema in Page Settings > Custom Code > Inside <head> tag:
{
"@type": "Organization",
"@id": "https://www.karpi.studio/#organization",
"name": "Karpi Studio",
"url": "https://www.karpi.studio",
"sameAs": [
"https://www.linkedin.com/company/76125840",
"https://www.instagram.com/karpistudio",
"https://www.behance.net/karpistudio",
"https://dribbble.com/KarpiStudio",
"https://webflow.com/@karpi-studio",
"https://clutch.co/profile/karpi-studio"
]
}Do not repeat sameAs on CMS pages. Reference the Organization via @id. The sameAs links are part of the Organization entity defined once on the homepage.
Schema HQ stores all your sameAs URLs in the dashboard. Add, remove, or reorder profiles without editing JSON-LD. Schema HQ injects the array on every page that references your Organization.
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://stripe.com/#organization",
"name": "Stripe",
"url": "https://stripe.com",
"sameAs": [
"https://www.linkedin.com/company/stripe",
"https://twitter.com/stripe",
"https://en.wikipedia.org/wiki/Stripe_(company)",
"https://www.crunchbase.com/organization/stripe",
"https://github.com/stripe",
"https://www.youtube.com/@StripeDev"
]
}{
"@context": "https://schema.org",
"@type": "ProfessionalService",
"@id": "https://www.karpi.studio/#organization",
"name": "Karpi Studio",
"url": "https://www.karpi.studio",
"sameAs": [
"https://www.linkedin.com/company/76125840",
"https://www.instagram.com/karpistudio",
"https://www.behance.net/karpistudio",
"https://dribbble.com/KarpiStudio",
"https://webflow.com/@karpi-studio",
"https://clutch.co/profile/karpi-studio"
]
}❌ Including your own website URL in sameAs:
"sameAs": [
"https://www.example.com",
"https://www.linkedin.com/company/example"
]✅ Only external profiles (your own site goes in the url field):
"url": "https://www.example.com",
"sameAs": [
"https://www.linkedin.com/company/example"
]❌ Including personal profiles instead of company profiles:
"sameAs": ["https://www.linkedin.com/in/john-doe"]✅ Using the company profile:
"sameAs": ["https://www.linkedin.com/company/your-company"]Personal LinkedIn profiles belong in Person schema for individual team members, not in Organization sameAs.
❌ Including dead or unclaimed profiles:
Every URL must load a real, active page. Broken links in sameAs signal neglect to AI engines.
❌ Using platform-specific short URLs or redirects:
"sameAs": ["https://lnkd.in/abc123"]✅ Using canonical profile URLs:
"sameAs": ["https://www.linkedin.com/company/your-company"]sameAs verifies the entity that name identifies. Name is the claim; sameAs is the evidence.sameAs array lives inside the entity block identified by @id. Other pages reference this entity (including its sameAs) through the @id URI.sameAs.sameAs helps with entity verification. They serve different purposes.Schema HQ manages all your sameAs URLs from a single dashboard. Add a new social profile, remove an old one, or reorder them without touching any JSON-LD. The array is injected on every page that references your Organization through @id.
Include every active, official profile your organization maintains. There is no maximum in the schema specification. Most organizations include 4 to 10 links. Quality matters more than quantity. A single LinkedIn profile that matches your Organization name is more valuable than ten abandoned social accounts.
Yes. A Wikipedia article is one of the strongest signals for Knowledge Panel creation and entity verification. Google's Knowledge Graph heavily relies on Wikipedia/Wikidata for entity data. If your organization has a legitimate Wikipedia article (not a stub or draft), include it in sameAs. Do not create a Wikipedia article solely for this purpose. Wikipedia editors will delete promotional or non-notable articles.
Yes, if you have one. Use the full URL of your Google Business Profile page. This helps Google connect your Organization schema to your GBP listing, which strengthens entity verification for both traditional search and AI results.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
"address": { "@type": "PostalAddress", "streetAddress": "1600 Amphitheatre Parkway", "addressLocality": "Mountain View", "addressRegion": "CA", "postalCode": "94043", "addressCountry": "US"}Block quote
Ordered list
Unordered list
Bold text
Emphasis
Superscript
Subscript