Entity & sameAs FinderFrom Wikidata To Schema Markup
Find your brand, person, product, or place on Wikidata, review the Wikipedia and profile links it knows about, and turn the ones you verify into sameAs JSON-LD.
1. Find your entity
Search Wikidata for matching entities. Verify each profile before including it in your markup.
2. Choose links and copy your schema
Search for your entity on the left. The profile links Wikidata knows about will appear here for you to check.
Step-by-step
How to build sameAs schema markup for your brand
Six steps from a name search to JSON-LD you can review and publish.
1.Search for your brand, person, product, or place
Type the name exactly as people know it and choose a language. Review matching Wikidata entries, then choose the correct entity.
2.Pick the entry that is genuinely yours
Many names are shared, so read each short description before choosing. Selecting the wrong entry would point your markup at someone else's profiles.
3.Review the profile links Wikidata knows about
The tool lists the official website, Wikipedia page, Wikidata page, and any social or reference profiles stored for that entry. Open each link to confirm it still works and belongs to you, then untick anything that doesn't.
4.Add profiles Wikidata doesn't have
Paste your own official profile URLs, one per line, such as LinkedIn, YouTube, or GitHub pages. Invalid entries are flagged and ignored.
5.Set the schema type, name, and website, then copy the JSON-LD
Choose Organization, Person, Brand, Product, or Place, check the name and URL, and optionally add a description in your own words. Copy the finished JSON-LD or download it.
6.Publish it and test it
Add the markup to the page it describes, usually your homepage or About page. Check it with the Schema Markup Validator or Google's Rich Results Test, and revisit it when your profiles change.
sameAs best practices
- Link only to pages about the same entity. Every sameAs URL should clearly describe your brand or person, not a similarly named one.
- Keep it current. Remove links to closed accounts and add new official profiles when you create them.
- Match the on-page facts. The name, website, and description in your markup should agree with what the page visibly says.
- Put it where it belongs. Organization markup usually goes on the homepage or About page, and Person markup on an author or About page.
- Pair it with consistent naming. Use the same name and spelling across your site, profiles, and directories so the entity is easy to recognise.
Common mistakes to avoid
- Adding unverified or unrelated profile URLs just to make the list longer.
- Treating sameAs as a ranking factor. It helps systems recognise who or what you are; it doesn't guarantee rankings or a Knowledge Panel.
- Creating a Wikidata or Wikipedia entry purely for SEO. Both have notability and neutrality rules, and promotional entries are often removed.
Learn the method
What is sameAs schema and why do entities matter?
In structured data, sameAs is a property that lists URLs of other pages that identify the same real-world entity as the one you are describing, such as your Wikidata entry or official social profiles. Search engines and AI systems work with entities — things like brands, people, and places — rather than just keywords, and sameAs links are one clear way to say “this page is about the same thing as these profiles.” It helps with disambiguation. It is not a ranking shortcut.
Where entity information comes from
- Wikidata
- A free, structured knowledge base that anyone can read. Entries have a Q-number and can store official websites and profile IDs.
- Wikipedia
- An encyclopedia with its own notability and neutrality rules. Not every brand or person qualifies for an article.
- Official profiles
- Verified social or professional pages you control, such as LinkedIn, YouTube, or GitHub.
- Reference databases
- Third-party directories such as Crunchbase that describe your organization.
Which schema type should you use?
| Type | Describes | Usual placement |
|---|---|---|
| Organization | Companies, publishers, nonprofits, and other groups | Homepage or About page |
| Person | A named individual such as an author, founder, or expert | Author page or personal About page |
| Brand | A brand name that is distinct from the company that owns it | Brand or product-line page |
| Product | A specific product you make or sell | The product's own page |
| Place | A location, venue, or landmark | The location's page |
What the finished markup looks like
A minimal Organization example with a few sameAs links. The tool produces the same shape from the links you tick.
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example Co",
"url": "https://example.com/",
"sameAs": [
"https://www.wikidata.org/wiki/Q00000000",
"https://www.linkedin.com/company/example-co/",
"https://www.youtube.com/channel/UCxxxxxxxxxxxxxxxx"
]
}If you're not on Wikidata
Many legitimate brands have no Wikidata or Wikipedia entry, and that's fine. Build your entity from sources you control: consistent naming across your site, a clear About page, and a short list of official profile URLs in your sameAs property. Entries on Wikidata and Wikipedia generally need independent, reliable coverage of the subject, so they tend to follow real-world recognition rather than create it.
Wikidata is edited by volunteers and can be incomplete or out of date, so always verify each link the tool surfaces before you publish it.
Put your entity markup to work
Add more structured data to the same page with the Schema Markup Generator. Then see how answer-ready your content is with the AI Citation Readiness Checker and describe your site for AI systems with the llms.txt Generator.
Browse all toolsCommon questions
Entity & sameAs finder FAQ
What does sameAs do in schema markup?
It lists URLs of other pages that identify the same real-world entity, such as a Wikidata entry or an official social profile. It helps search engines and AI systems connect your page to the right entity.
Will adding sameAs improve my rankings?
Not directly. It supports disambiguation and entity recognition, but it is not a ranking shortcut and it does not guarantee a Knowledge Panel or any other search feature.
Where does the data come from?
From Wikidata, a public knowledge base. Wikidata is maintained by volunteers, so the information can be incomplete or out of date. Always open and verify each link before using it.
Is my search sent to your servers?
No. Your search text goes from your browser straight to Wikidata. The JSON-LD is built in your browser, and nothing you enter is stored by this tool.
What if my brand isn't on Wikidata?
That is common for newer or smaller brands. Don't create an entry just for SEO, since Wikidata has notability rules. Instead, paste your own official profile URLs into the tool and generate sameAs markup from those.
Where should I put the generated JSON-LD?
On the page that describes the entity — usually the homepage or About page for an Organization, or an author or About page for a Person. After publishing, test it with the Schema Markup Validator or Google's Rich Results Test.