To connect a recruiter profile on your website with that recruiter’s LinkedIn profile, add a Person entity to the recruiter page and put the person’s direct LinkedIn profile URL in its sameAs property. Give the person a stable @id, describe their current role on the visible page, and use worksFor to connect them to the recruiting firm’s separate Organization entity.

The distinction matters: a recruiter is a person, while a recruiting firm is an organization. An individual’s LinkedIn profile belongs in the person’s sameAs; the firm’s LinkedIn company page belongs in the organization’s sameAs. At Rank For AI Search, we treat that separation as part of entity alignment: first make each identity accurate, then connect the identities with the right relationship.

This markup helps search systems interpret who a recruiter is and where they work. It does not guarantee a Google ranking, a rich result, or an AI recommendation. The strongest implementation pairs accurate JSON-LD with a useful recruiter biography, a working LinkedIn link, consistent company information, and regular updates when roles change.

What does `sameAs` mean on a recruiter profile?

Schema.org defines sameAs as a URL for a reference page that unambiguously indicates an item’s identity. On a recruiter profile, it answers a narrow question: which external page identifies this same person? A direct LinkedIn member profile can serve that purpose when you have confirmed it belongs to the recruiter.

Think of sameAs as an identity assertion, not a general-purpose outbound link. A recruiting firm’s LinkedIn page, an article that quotes the recruiter, and a search results page for the recruiter’s name are different kinds of pages. They may be useful to readers, but they do not all identify the same individual. For a broader explanation of this distinction, see our guide to sameAs and brand identity.

The other properties in the markup do different jobs:

@id identifies the recruiter entity within your site’s structured data. Keep it stable wherever you refer to that person.
url identifies the recruiter’s page on your website.
sameAs points to an external identity page, such as that person’s LinkedIn profile.
worksFor connects the person to the employer. It is not interchangeable with sameAs.

If two people share a name, these distinctions become especially useful. The website profile describes the recruiter in your firm’s own words; the LinkedIn URL adds a specific external identity reference; and worksFor states the employment relationship. Together, they are clearer than repeating a name and job title without explaining how the pages relate.

Why connect recruiter identities across your site and LinkedIn?

Recruitment depends on trust in both a firm and its people. A hiring manager may know the agency but want to assess the recruiter’s specialty. A candidate may find an individual on LinkedIn and look for confirmation that the recruiter represents the firm they claim to work for. A well-maintained website profile gives both audiences a place to check the details.

For search systems, consistent identity information helps reduce ambiguity. If your site calls someone a healthcare recruiter, their LinkedIn profile identifies the same person, and the employer relationship is current, the connection is easier to interpret than a thin team page with no individual context. This is particularly important when a firm employs recruiters with different industries, roles, or locations.

There is also a practical limit to what structured data can do. A sameAs reference does not make LinkedIn confirm your markup, give you control of LinkedIn’s content, or substitute for evidence of professional expertise. It is one part of a larger identity footprint that includes readable biographies, relevant service pages, accurate off-site profiles, and accessible site content.

Build the recruiter page before adding schema

A structured data block should describe a real page, not compensate for an empty one. Give each recruiter you intend to feature a useful profile with a stable address. The page should make it easy for a visitor to tell who the person is, what recruiting work they do, and how to contact the firm.

A strong recruiter profile can include:

The recruiter’s full professional name and current title.
A biography explaining the types of roles, industries, or hiring needs they handle.
The firm’s name and a link to the relevant recruiting service or team page.
A professional photograph, if the recruiter and firm use one publicly.
A visible link to the correct LinkedIn member profile.
Specific experience, qualifications, or professional writing that the firm can substantiate.
A clear contact route for candidates or hiring teams.

Specificity beats generic claims. A biography that explains whether someone handles technical hiring, executive search, or another specialty gives readers more useful information than saying they are passionate about connecting talent with opportunity. Write what the recruiter actually does, and keep the title and employer current.

If your site has only a short team directory, you can still add individual Person markup where the identity is clear. A dedicated profile page is often more useful, though, because it gives the person a stable URL, room for a meaningful biography, and a straightforward place to maintain their LinkedIn link. Our employee and expert profile markup guide covers the same principle across other professions.

How to add `sameAs` schema step by step

1. Confirm the recruiter’s LinkedIn identity

Ask the recruiter to confirm the exact URL for their own LinkedIn member profile. Check that it resolves to the intended person rather than a namesake, a search page, a company page, or a tracking link. If the visible profile details have changed, reconcile them before publishing the connection.

Use the direct profile address the recruiter recognizes and maintains. Do not copy a search URL merely because it appears in search results, and do not guess a profile address from a name. If you cannot confidently establish that a LinkedIn page identifies the person on your site, leave that URL out of sameAs until you can.

2. Create a stable identifier for the person

Use a distinct @id for each recruiter. A common pattern is the recruiter’s profile URL with a #person fragment. That identifier belongs to the person entity; the page’s address remains the value of url. Keep the same @id if you later refer to that recruiter from an article or another structured data block on your site.

A stable identifier helps prevent your publishing system from describing the same recruiter as unrelated people across different pages. If you move the recruiter’s profile to a new address, plan the page redirect and update references deliberately rather than generating conflicting identities by accident.

3. Reference the firm’s organization entity

Your recruiter and your firm are separate entities. Represent the firm with Organization markup and a consistent organization @id. On the recruiter entity, use worksFor to refer to that identifier. If the firm has an official LinkedIn company page, that URL can appear in the organization’s own sameAs, not in the recruiter’s.

You do not need to repeat every organization detail inside every recruiter profile. A shared identifier lets you connect people to the same firm without introducing slight variations in the company name or website URL. This approach also supports the broader work of connecting organization and service entities where those relationships are relevant to the site.

4. Publish JSON-LD that matches the page

The example below uses clearly fictional names and reserved example domains to illustrate the structure. Replace every sample value with your firm’s real page, your recruiter’s confirmed LinkedIn URL, and accurate visible profile information before publishing. In this example, the firm’s LinkedIn address belongs to Organization; the individual’s belongs to Person.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://example.com/#organization",
      "name": "Example Recruiting Firm",
      "url": "https://example.com/",
      "sameAs": "https://www.linkedin.com/company/example-recruiting-firm/"
    },
    {
      "@type": "Person",
      "@id": "https://example.com/team/jane-doe/#person",
      "name": "Jane Doe",
      "url": "https://example.com/team/jane-doe/",
      "jobTitle": "Recruiter",
      "worksFor": {
        "@id": "https://example.com/#organization"
      },
      "sameAs": "https://www.linkedin.com/in/jane-doe-example/"
    }
  ]
}
</script>

The example shows the relationships, not a list of required fields. Add an image, description, or areas of expertise only when they accurately describe the recruiter and the visible page supports them. If your site already defines the organization under a different @id, reference that existing identifier instead of creating a second organization identity.

5. Add a normal LinkedIn link for readers

The JSON-LD is for machine-readable identity; the visible link is for people. Place a clearly labeled LinkedIn link near the recruiter’s biography or contact information so a visitor can check it directly. Do not hide an identity assertion in schema while displaying a different professional profile on the page.

6. Validate the result and review the rendered page

After publishing, check that the page loads, its canonical address is correct, and the JSON-LD appears in the HTML that search systems can access. Parse the JSON-LD with a structured data validator, then manually inspect the resulting Person and Organization entities. General validation checks syntax and structure; it cannot determine whether the LinkedIn profile belongs to the right human. That final check requires an editorial review.

Review both desktop and mobile page output if your site uses different templates. Some content management systems add profile markup through plugins while a separate template adds another Person entity. Multiple blocks are not inherently a problem when they describe the same entity consistently, but contradictory names, URLs, and employer relationships need to be resolved. For a practical testing workflow, see our structured data testing guide.

Choose the right relationship for each URL

A frequent source of schema errors is using sameAs whenever two pages are somehow connected. Ask what relationship you actually intend to state before you add a URL.

The recruiter’s LinkedIn member profile: Use sameAs on the recruiter’s Person entity when it clearly identifies that person.
The firm’s LinkedIn company page: Use sameAs on the firm’s Organization entity when it identifies that organization.
The recruiting firm that employs the person: Use worksFor on the person’s entity to connect them to the organization.
An article written by the recruiter: Use an authorship relationship on the article where appropriate; the article itself is not automatically the recruiter’s identity page.
A press mention or event recap: A page that discusses a person is not necessarily a page that unambiguously identifies them. Do not add it to sameAs just to collect more references.

This distinction keeps your entity graph readable. It also makes future maintenance easier. When a recruiter changes employers, you know the employer relationship needs attention, but the person’s identity and confirmed LinkedIn member profile may remain the same.

Best practices for a recruiting firm’s profile system

When you manage multiple recruiter pages, the hardest part is usually not writing the JSON-LD. It is keeping page copy, employment status, and external identities aligned as people and responsibilities change. We recommend treating structured data as an output of an approved profile record, rather than a separate set of facts someone must remember to edit.

Maintain a profile inventory. Record each recruiter’s name, website profile URL, schema @id, confirmed LinkedIn URL, current title, and employment status in one place.
Assign an owner for changes. Make someone responsible for updating the profile when a recruiter joins, changes specialty, changes their LinkedIn URL, or leaves.
Keep public claims consistent. The site, visible LinkedIn link, and structured data should identify the same person. When a title differs because one profile has not been updated, fix the underlying information rather than disguising the inconsistency in schema.
Use only relevant external identities. A small set of clearly matching profiles is more useful than an indiscriminate list of mentions, abandoned accounts, and directory pages.
Check access and discoverability. The website profile should be accessible to visitors and search crawlers. Schema on a blocked or unavailable page cannot do much to clarify a recruiter’s identity in search.
Review departures promptly. Do not leave a former employee marked as currently working for the firm. Decide whether to remove the page, update it, or preserve it with accurate historical wording, then adjust the structured data accordingly.

For recruiters whose names are common, add useful distinguishing context to the visible profile, such as a genuine area of recruiting expertise or location served. Do not create artificial distinctions in markup alone. If the biography cannot answer why this person is the right match for a hiring need, the schema cannot answer it either.

How does this fit into AI search and Google SEO?

Connecting a recruiter profile to LinkedIn is one piece of entity reconciliation. It helps describe a person and their relationship to a firm, while the rest of the website explains the firm’s services and areas of expertise. Search engines and AI assistants may encounter those sources in different ways, so the aim is not to force a recommendation through one property. The aim is to make the public information accurate, coherent, and easy to interpret.

We approach this in a practical order: establish the firm’s identity, publish useful service and expert content, connect individual people to the firm with appropriate schema, then review off-site profiles for conflicting details. Entity reconciliation becomes particularly important when names, locations, or roles could describe more than one person or business.

Rank For AI Search works on this wider foundation through entity and knowledge graph alignment, JSON-LD structured data, content architecture, off-site profile alignment, and ongoing AI visibility monitoring. For a recruiting firm, that means the sameAs link should be evaluated alongside the quality of recruiter biographies, the accuracy of the firm’s profiles, and the questions prospective clients actually ask, not treated as a standalone shortcut.

Common mistakes to catch before publishing

Putting a company page in a person’s `sameAs`

A firm may encourage every recruiter to link to its LinkedIn company page, but that does not make the company page an identity page for each employee. Keep the member profile on Person, the company page on Organization, and the employment connection in worksFor.

Choosing a LinkedIn result by name alone

Names are not unique. A search result might belong to another recruiter, a former colleague, or an unrelated person. Confirm the address with the recruiter or a firm-approved source before publishing it. A wrong identity connection is worse than omitting an uncertain one.

Publishing richer schema than the page supports

A detailed knowsAbout list does not establish expertise if the biography says nothing about those subjects. Add specialties and experience only when you can describe them clearly and accurately to readers. Prioritize the actual page over an impressive-looking JSON-LD block.

Leaving employment relationships unchanged after a move

A profile that still says someone works for your firm after they leave can mislead both users and systems interpreting the page. Set an internal process for reviewing recruiter pages as part of staff changes, not only during a general SEO audit.

Assuming validation means a recommendation is coming

A validator can tell you whether markup parses and whether supported types or properties are present. It does not certify professional credentials or promise inclusion in an AI answer. Measure your wider search visibility separately, and investigate whether your pages and business information answer the questions people ask.

Frequently asked questions

Should each recruiter have their own `Person` schema?

When a recruiter has a distinct profile page, describe that individual with a distinct Person entity and a stable @id. Connect the person to the firm’s Organization entity through worksFor. Do not reuse another recruiter’s identifier simply because they share an employer.

Can a recruiter have more than one `sameAs` URL?

Yes. The property can hold multiple identity references. Include an additional profile only if it unambiguously identifies the same person and remains accurate. There is no need to fill an array with every page that mentions them.

Should the recruiter page link visibly to LinkedIn too?

Yes, when the firm and recruiter want visitors to use that profile. A visible link helps people verify the connection. The JSON-LD describes the identity relationship for systems reading structured data; it is not a replacement for a useful page.

Does `sameAs` create a backlink from LinkedIn?

No. It is a reference from your website’s structured data to a LinkedIn URL. It does not add a link to the recruiter’s LinkedIn page or create a reciprocal endorsement.

What if a recruiter changes their LinkedIn profile URL?

Confirm the new address with the recruiter, update the visible link and the sameAs value, then check that the destination resolves to the right profile. Keep the person’s on-site @id stable if the underlying person and site profile have not changed.

What if a recruiter leaves the firm?

Update or remove the current worksFor relationship as appropriate, and make the visible page accurate. If you keep an archived profile, do not present it as a current staff page. A LinkedIn sameAs reference should also be reconsidered in light of how you maintain that archive.

Will this make a recruiter appear in ChatGPT, Gemini, Perplexity, or Google results?

It can help clarify identity, but no single schema property guarantees visibility or recommendation in any search system. Useful profile content, clear service relevance, accessible pages, consistent off-site information, and reputation all matter to the broader picture.

The practical takeaway

Start with a real recruiter biography and a confirmed LinkedIn member URL. Give the recruiter a Person entity with a stable @id, put that member URL in sameAs, and connect the person to the firm’s separate Organization entity with worksFor. Make the same relationship clear to readers on the page, validate the markup, and revisit it whenever the recruiter’s role changes.

If you want to connect people, company information, structured data, and off-site profiles into a coherent search presence, book a consultation with Rank For AI Search. We can help you assess how clearly your website and public profiles represent the business behind the experts.

What does sameAs mean on a recruiter profile?