sameAs is the Organization property that tells search engines which other pages on the web are official profiles of your brand, such as social media accounts. The dependable approach has five parts: list only profiles you own, that are official and active; write the brand name, logo and site address the same way everywhere; place the markup on the home page or the About page; show the same profiles as visible links on your site; and check the result with Google's tools. Google does not require the property and does not promise any display. The purpose is a consistent identity that a person or a machine can verify.
It is written for brand owners, store managers and SEO leads who run their own website and keep accounts on several social channels. The focus is less the markup syntax than the accounts behind it: how profiles are prepared, who owns them, whether names stay consistent, and whether a marketplace store page belongs in the list. Google documentation has nothing to say on how social platforms rank or surface content; the subject is the identity link you control from your own site.
What sameAs says, in plain words
In the schema.org vocabulary, sameAs is the URL of a reference web page that unambiguously indicates the identity of the item. The definition mentions examples such as a Wikipedia page, a Wikidata entry or the official website of the item. The property is defined on Thing, so every more specific type, including Organization, inherits it. Google's Organization documentation describes the same idea in practical terms: sameAs is the URL of a page on another website with additional information about your organization, and you can give several.
Put simply, your site says "this is my organization," and sameAs adds "these other pages are about the same organization." Social profiles are natural candidates because a brand can have one or more official accounts that describe it. The markup moves those links from something a visitor sees into something a machine can read.
What it does not do
Expectations need to be set carefully. sameAs is not a ranking tool. Google says no property is required and that it does not guarantee that features using structured data will appear in search results. Getting your profile to show up in results, growing followers or having profile content indexed are not outcomes you can expect from this markup.
Not the site name mechanism
A neighboring page is easy to confuse with this one. The site name documentation (Opens in a new tab) asks for WebSite structured data on the home page, supports alternateName and does not mention Organization, sameAs or social profile links. So sameAs is not how you control the site name. For site name problems, see the guide on wrong site names and favicons in Google results.
What Google's Organization page covers
Google's Organization documentation (Opens in a new tab) says the markup helps Google understand the administrative details of an organization. There are no required properties, and sameAs is among the recommended ones. Some properties work in the background, while others, like logo, can affect visuals in Search.
Fields that connect to profiles
- sameAs: the URL of a page on another website with more information about the organization; official profile addresses go here.
- url: the organization's website; it should match the site link on each profile.
- name and alternateName: they should agree with the profile name and the short name used on profiles.
- logo: it should be the same brand mark as the profile picture. See the documentation for the technical conditions.
Which profiles belong in the list
You do not need to list every account. The list should contain pages that really represent your brand. This decision rule gives a practical filter.
- Does the brand own the profile? If you manage the account and hold the login, yes.
- Is it official? Fan pages, reseller pages and look-alike accounts stay out.
- Is it current? A long abandoned account is a weak identity signal.
- Does the profile show the brand name, the logo and the site address? If not, fix the profile first, then list it.
- Does the profile introduce the organization? A page created for one product or a finished campaign is not a good fit.
The rule follows from the definition of sameAs: the page should be a reference that shows the identity of the organization. A page that has lost that quality only lengthens the list.
Marketplace store pages
A store page on a marketplace can look like an organization page. Google's documentation says nothing specific about marketplace pages, so the call is yours. Ask whether the page clearly introduces your brand, whether your name and site address are consistent there, and whether the page is permanent. If the store name changes often, the page can be closed under a marketplace policy or it is mixed with other sellers, leaving it out is safer.
A decision table for a marketplace store page
| Question | If yes | If no |
|---|---|---|
| Does the store page introduce your brand by name and logo? | Candidate for the list | Leave it out |
| Does it show your site address, and does the store name match the name on your site? | Consistency is in place | Fix the store details first |
| Is the store address permanent and free of redirects? | Write the final address | Wait until it settles |
| Do you control the account? | Ownership is clear | Leave it out |
| Can the page be mixed up with other sellers? | Leaving it out is safer | It stays a candidate |
This table is not a Google rule; the documentation says nothing about marketplace pages. The questions come from the idea in the sameAs definition that the page should be a reference showing the identity of the item. Record the decision with a date and a reason, and ask the same questions again if the store name changes.
How many is enough
The documentation sets no upper limit and says several URLs may be given. Keep the list lean with active, official accounts only. A longer list does not mean more information, it means more upkeep.
Making the profiles match the site
The markup alone does not do the work; the profiles must tell the same story. Identity matching runs in both directions: the site points to the profiles, and the profiles point back to the site.
Profile preparation checklist
- Write the brand name identically on the site, in the Organization name field and on every profile. If you use a short name, declare it as alternateName.
- Use the same brand mark as the site logo for the profile picture.
- State what the brand does in the profile bio and include the site address.
- Make the site link in the profile identical to the url value in the markup, including the https and www choice.
- Keep usernames as similar as possible across channels; entirely different handles weaken the identity trail.
- If the brand has an account for each language, note the language in the account description.
From the profile to the site
The site link on a profile is the mirror image of the sameAs markup. You say on the site "this profile is mine," and the profile says "this site is mine." A two way link paints a more consistent picture than a one way claim. Adding tracking tags to that profile link is a separate measurement topic; for identity purposes the address on the profile should be clean and permanent.
From the site to the profiles
Put visible links to the social profiles on your site, for example a row of icons in the footer. A visible link serves visitors and creates no conflict with the markup. The structured data policy tells you not to mark up content readers cannot see. It does not state a visibility rule for sameAs addresses specifically, yet listing a profile only in the markup and nowhere on the site is a weak practice. A simple rule follows: if a profile is in the markup, show it on the site too.
Keeping an official profile register
Which accounts are official is often knowledge that sits in a few people's heads. Writing it into one register gives the markup, the footer links and the profile updates a single source of truth. The register is an internal document of the brand; it does not have to be published on the site.
What to record for each profile
| Field | What goes in | Why keep it |
|---|---|---|
| Platform and address | The final profile address without redirects | sameAs and the footer use the same address |
| Username and display name | As written on the platform | A name change shows what else needs updating |
| Profile bio | The text that carries the brand name and site address | Lets you spot a leftover old domain |
| Admin account | The owner, tied to a company email | Access is removed when someone leaves |
| Last check date | The day the address opened and the content looked current | An abandoned channel is noticed early |
Choosing a username
Derive the username from the brand name and keep it as close as you can across channels. If the name you wanted is taken on one channel, add a word or an abbreviation to the brand name rather than picking an unrelated handle, and note the difference in the register. If you declare a short name as alternateName, check that the username fits it. Handles that look nothing alike make it harder to confirm that the accounts belong to one brand.
A short note on the markup itself
Writing the sameAs block, choosing a subtype and deciding between the home page and an About page are part of Organization markup in general; the JSON-LD guide to Organization, Breadcrumb and Article goes through them. Only the account rule matters here: write each address in full, with https and as the final form without a redirect. Shortened links and addresses with session parameters do not work well as identity references.
The name and logo in the markup should match the name and logo visible on the page. Adding information that is not on the page goes against the structured data policy. For the format, follow Google documentation and check the current page before you implement.
Quality rules and risks
Google's structured data policies set a few principles. Do not mark up content that is not visible to readers. Do not mark up irrelevant or misleading content. The markup must be a true representation of the page. Pages carrying structured data must not be blocked from Googlebot by robots.txt, noindex or other access controls. A violation can lead to a manual action, which removes rich result eligibility but does not affect ranking in web search, and valid markup does not guarantee display.
Applied to sameAs: listing a profile you do not own as if it were yours is a misleading claim and puts the markup at risk. Listing the big account of another brand to suggest a relationship falls in the same category. Keeping the list honest and verifiable is both the safest policy choice and the best long term habit.
Validation tools
The documentation suggests testing the markup with the Rich Results Test, using the URL Inspection tool to confirm that Google can see the live page and keeping Google informed of changes through a sitemap. If you suspect a manual action, the Manual Actions report in Search Console is the place to look. If you use the interface in another language, menu names may look different. These tools show technical validity; they do not produce a display result.
One brand, two languages
On a Turkish and English site the sameAs decision depends on how the accounts are organized. If the brand runs one international account, the same profile addresses appear on both language versions. If each language has its own official account, the Turkish page can carry the Turkish account and the English page the English account, with the shared account staying in both.
Two rules help here. The name and description fields should match the language of the page. And the url field should consistently point to the home page of that language version or to the brand's canonical home page. Language versions are declared with hreflang, which sameAs does not replace.
When the brand name is spelled differently
If you use different spellings in the Turkish and English markets, keep them identical on the profiles and tie them together with alternateName. An inconsistent spelling can make one organization look like two separate entities. The general logic of the entity approach is covered in the entity SEO guide.
When the name belongs to someone else too
If your brand name is common or close to another organization's name, sameAs alone distinguishes little. Put distinguishing facts into the markup and the profiles together: full legal name, founding year, address and a clear descriptive sentence. Google's page lists legalName, foundingDate, address and several identifier fields among recommended properties. None of them is mandatory; add only details that are accurate and also visible on the page.
A distinguishing profile name
Adding a short qualifier to the profile name, such as the sector or the city, can reduce confusion. Check the result against the name on the site and in the name property, because different spellings break consistency. A reasonable balance is the full name in name and the short name in alternateName.
Controlling the accounts you list
A sameAs list points to accounts you claim to own, so those accounts must stay in your hands. If an account is taken over or you lose access while its address stays in the markup, your brand identity points at a page controlled by someone else. A few habits reduce that risk.
- Tie the administrator email of each official account to a company address, not a personal one.
- Turn on the extra verification option the platform offers; the option names differ by platform.
- Keep a list of people with access and remove a departing person the same day.
- Write ownership into the contract when an account is handed over or an agency changes.
- Remove an unused account from the markup and from site links before you delete it.
Accounts run by an agency
If an agency runs the account, the brand should appear as the owner. Presenting an agency account as the brand's official profile in the markup would be misleading. Bind the administrator role to your own address at the start so that the account stays with you if the agency changes.
Keeping the list current
Profile addresses are not fixed. A username can change, an account can be closed, the brand can be renamed or a channel can be abandoned. If the markup is not updated, it ends up pointing to an outdated or foreign address. The table summarizes what to do per event.
| Event | Action | Timing |
|---|---|---|
| Username changed | Update the markup and the footer link | Same day |
| Account closed | Remove from sameAs and remove the footer icon | Same day |
| Brand renamed | Update name, alternateName, logo and profile names together | One release |
| New official channel opened | Prepare the profile, then add it | When the profile is ready |
| Channel abandoned | Consider removing it | Review every quarter |
The quarterly review
Opening every profile address once a quarter is enough. In the same review, check that the logo address still opens and that the footer icons go to the right place. That small habit keeps the markup from aging quietly.
sameAs, canonical and hreflang are different jobs
Identity, address and language work are handled by three mechanisms that people often mix up.
| Mechanism | Job | Relation to sameAs |
|---|---|---|
| sameAs | Declares official pages of the organization on other sites | Used for identity matching |
| rel canonical | Names the preferred address among duplicate or very similar pages | Manages your own pages, not profiles elsewhere |
| hreflang | Declares language and region versions of a page | sameAs does not declare language versions |
In practice: do not try to fit profile addresses into canonical, do not push language declarations into sameAs and do not treat the list as a substitute for the site name mechanism. Each job has its own tool, and mixing them makes both the markup and its upkeep harder.
A check before you publish
- Open each profile address in a private window and see whether it belongs to your brand, loads and avoids redirects.
- Confirm that the brand name, logo and site address on each profile match the values in the markup.
- Compare the visible profile links in the footer with the list in the markup.
- Place the JSON-LD block on the home page or the About page and avoid repeating it on every product page.
- Validate with the Rich Results Test and look at the live page with the URL Inspection tool.
- Confirm that the page is not blocked by robots.txt, noindex or another control.
- Search your brand name and note the results as a starting record for later comparison, not as a promise of display.
Comparing with your brand search
Recording which profiles and pages appear when you search the brand name lets you see later whether anything changed. How to keep and read that record is covered in the guide on auditing brand search results. If a result does not change after you add the markup, that is not an error, since Google does not guarantee display.
Example scenario: a small bicycle workshop
Example scenario: A small bicycle workshop has its own site and three social accounts. The name is "Northfield Cycles" on the site, "Northfield Cycles Repair" on one profile and only "northfieldcyc" on another. One profile links to an old domain. The site has no social icons and no markup.
The work goes in order. First the brand name and short name are decided: "Northfield Cycles" and "Northfield". The three profile names and bios are corrected, the profile picture is replaced with the site logo and the old domain link is updated. Next three visible profile links are added to the site footer. Then an Organization block carrying the three profile addresses as sameAs is placed on the About page. Finally the Rich Results Test confirms validity and the URL Inspection tool confirms that the live page is accessible.
The result is a record of identity matching: the same name, the same logo, the same site address and links in both directions. No display or ranking outcome is expected; the gain is a brand identity that is consistent and easy to maintain.
Common mistakes and fixes
| Mistake | Result | Fix |
|---|---|---|
| Organization block on every product page | Needless repetition | The home or About page is enough |
| Listing abandoned profiles | Weak identity signal | Limit the list to active official accounts |
| Different brand spellings per channel | One organization looks like two | Align name and alternateName |
| Old site address on a profile | Identity link breaks | Write the current canonical address |
| A profile in the markup but not on the site | Inconsistent picture | Add a visible footer link |
| Shortened or parameter address | Weak identity reference | Write the final profile address |
| Listing someone else's account | Misleading claim, policy risk | List only your own accounts |
| Blocking the page with robots | Google cannot read the markup | Keep the page accessible |
Frequently Asked Questions
Does sameAs make my social profiles appear in Google results?
The documentation makes no such promise. Google states that it does not guarantee features that use structured data will appear in search results. sameAs points to another page with additional information about your organization; whether anything is shown is Google's decision.
Is sameAs markup required?
No. Google's Organization documentation says there are no required properties, and lists sameAs among the recommended ones.
Which profiles should I list?
List official, current profiles that your brand controls. Avoid abandoned pages, accounts that someone could confuse with yours and pages you do not own. The documentation says nothing specific about marketplace store pages, so judge each one on whether it clearly identifies your organization.
Do I need to add the markup to every page?
No. Google says the markup belongs on the home page or on a single page that describes the organization, such as an About page, and is not needed on every page.
What if a profile username changes?
Update the address in the markup and the visible link on your site the same day, and check whether the old address still redirects. If it is no longer yours, remove it from the list.
Can I list different profiles for the TR and EN versions?
Yes. If the brand runs a separate official account per language, each language version can carry its own account in its Organization block. Keep the brand name and site address consistent across the accounts.
Related guides: Reduce Marketplace Dependence in 90 Days, How to Build a Link-in-Bio Page, Open Graph Tags: Get the Shared Link Preview Right.
Conclusion
sameAs is a small, orderly job that ties a brand site to its official social profiles. In short: list only profiles you own that are official and current; write the brand name, logo and site address consistently everywhere; place the markup on the home page or the About page; show the same profiles as visible links on the site; verify with the Rich Results Test and the URL Inspection tool; and update the list when a profile changes. Google does not require the property and does not guarantee display, and the schema.org definition (Opens in a new tab) speaks only of a reference page that shows identity. Under the structured data policies (Opens in a new tab) nothing should be marked up that readers cannot see. Documentation and policies can change, so check the current pages before you implement.
If you also want your brand to gain visibility through content on publisher sites, you can browse the guest post listings on Akua Adforce; scope and terms are stated on the relevant product page.
Post a comment
Please log in to leave a comment. Login