Semantec SEO

Entity Identity Across Pages for Schema and SEO

Entity identity across pages is the practice of describing the same company, person, product, or software entity in a consistent way across the whole site.

That sounds simple, but it is where many schema setups drift. One page calls the company one thing, another page uses a shorter label, a third page treats the software like the company, and a fourth page points to no clear primary entity at all.

Google says structured data gives explicit clues about page meaning and also helps it gather information about the people, books, companies, and other things included in the markup. Schema.org also gives you properties such as sameAs, mainEntity, and mainEntityOfPage to clarify identity and page focus.

If you want the wider cluster first, start with Schema for SEO. If you need the syntax first, read JSON LD Basics. If you are working on homepage identity, pair this page with Organization Schema and sameAs and Entity Identity.

The short answer

Pick one canonical identity for each entity, keep the name and role stable, point the right page at the right primary entity, and reuse the same references across the site. In Schema.org terms, that often means using sameAs for external identity references and mainEntity or mainEntityOfPage to state which thing a page is mainly about. Google also says organization markup on the home page can help disambiguate the organization in search results.

What this page is really about

This is not just a schema formatting task.

It is a site wide identity task. The goal is to stop one entity from being split into several weak versions across different URLs. Schema.org’s data model notes that many pages have a clear primary topic, and that mainEntity and mainEntityOfPage let you express the relationship between a page and that primary entity. It also notes that sameAs, url, and mainEntityOfPage are related but not identical signals.

On a site like Semantec SEO, that can include:

  • the company behind the site
  • the product at MIRENA
  • the founder page at Kevin Maguire
  • supporting pages that refer back to those entities through Entity Markup and page specific schema

Where identity drift starts

Identity drift tends to show up in four places.

1. The name changes from page to page

The company name, product name, or founder name shifts across the site. Google’s profile page and organization docs both lean on a clear name field as the primary way the person or organization is identified.

2. The wrong page owns the entity

A page mentions an entity, but it is not the main thing the page is about. Schema.org draws a clear line here: mainEntity is for the primary entity described in a page, while about can refer to several topics.

3. The site never states the outside identity

Schema.org defines sameAs as a URL for a reference page that unambiguously indicates the item’s identity, such as an official site, Wikidata entry, or similar reference. Without those references, the entity graph is often thinner than it needs to be.

4. The product, person, and company blur together

A software page can drift into company identity. A founder page can drift into brand identity. A company page can drift into product identity. Google’s structured data docs keep coming back to one rule: the markup should describe the content of the page it sits on.

The core schema pieces

sameAs

Use sameAs for external references that clearly identify the entity. Schema.org describes it as a URL of a reference page that unambiguously indicates the item’s identity. This is the property that helps connect your on site entity to its wider web identity.

A company page can point to official social profiles or knowledge base references. A founder page can point to external profile pages. A product page can point to an official product home if the page itself is not the canonical product URL.

For the surrounding topic, read sameAs and Entity Identity.

mainEntity

Use mainEntity on the page level object when the page itself is a WebPage, ProfilePage, or another CreativeWork that is mainly about one thing. Schema.org describes mainEntity as the primary entity described in a page or other creative work.

This is a strong fit for:

  • a product page that is mainly about one software product
  • a founder page that is mainly about one person
  • a company page that is mainly about one organization

mainEntityOfPage

Use mainEntityOfPage on the entity when you want to point back to the page that primarily describes it. Schema.org defines it as the page for which the thing is the main entity being described.

This is the inverse side of the same relationship. You do not need to force both directions everywhere, but the concept is useful: one page, one main thing.

Homepage organization markup

Google says adding organization structured data to the home page can help it better understand the organization’s administrative details and disambiguate the organization in search results. That makes the home page the clean anchor for company identity.

For Semantec SEO, that means the company level identity should be rooted at the site home page and tied back into Organization Schema.

Profile pages for people and organizations

Google’s profile page documentation says ProfilePage markup is for pages where the primary focus is a single person or organization affiliated with the site, and it uses mainEntity for that page focus. It also supports sameAs for external profile or home page references.

That makes profile style identity pages a strong fit for founder and author pages.

Product and software pages

Google supports product markup on product pages, and Schema.org gives SoftwareApplication its own type plus properties such as provider and publisher. That is why a software product page should carry its own product or software identity while still connecting back to the company entity.

For that layer, keep Product Schema for SaaS and SoftwareApplication Schema close.

A clean site pattern

A simple site pattern works well here.

The home page anchors the organization.

The product page anchors the software.

The founder page anchors the person.

Other pages refer back to those same entities instead of inventing new versions.

That pattern lines up with Google’s home page organization markup, profile page markup for person or organization pages, and Schema.org’s page to entity relationship model with mainEntity and mainEntityOfPage.

A practical example

On Semantec SEO, a clean identity map could look like this:

  • the home page describes Semantec SEO as the organization
  • MIRENA describes MIRENA as the software product
  • Kevin Maguire describes Kevin Maguire as the person
  • support pages such as Markup Prioritization or Schema Debugging mention those entities, but they do not take ownership of them as the main page entity unless that is truly the page’s focus

A simple JSON LD pattern

Below is a compact example that shows one company entity reused inside a software page.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://semantecseo.com/#organization",
      "name": "Semantec SEO",
      "url": "https://semantecseo.com/",
      "sameAs": [
        "https://www.linkedin.com/company/semantec-seo/"
      ]
    },
    {
      "@type": "WebPage",
      "@id": "https://semantecseo.com/mirena/#webpage",
      "url": "https://semantecseo.com/mirena/",
      "name": "MIRENA",
      "mainEntity": {
        "@id": "https://semantecseo.com/mirena/#software"
      }
    },
    {
      "@type": "SoftwareApplication",
      "@id": "https://semantecseo.com/mirena/#software",
      "name": "MIRENA",
      "url": "https://semantecseo.com/mirena/",
      "applicationCategory": "BusinessApplication",
      "operatingSystem": "Web",
      "provider": {
        "@id": "https://semantecseo.com/#organization"
      }
    }
  ]
}

This pattern follows the same logic described by Schema.org’s data model and Google’s page focused structured data rules: the page states its main entity, and the software entity points back to the organization rather than creating a separate company node inside the same site.

What to keep consistent across the site

When you describe the same entity on more than one URL, keep these fields stable unless there is a real reason to change them:

  • name
  • the main canonical page for that entity
  • sameAs references
  • the relationship to the company, product, or person
  • the page that owns the entity as its primary focus

Those recommendations follow directly from Schema.org’s identity properties and Google’s page relevance rules.

Common mistakes

Treating every mention as a primary entity

Schema.org’s own notes separate about from mainEntity. A page can mention many things, but it should name only one main entity when one clear primary focus exists.

Giving the same entity new labels on different pages

That weakens the site’s own graph. Google’s organization and profile docs both rely on a stable name field for identification.

Leaving the organization unanchored

Google says the home page is the place where organization markup can help disambiguate the business in search. If that layer is missing, the rest of the site has a weaker identity base.

Turning support pages into entity owners

A how to page, a docs page, or a schema explainer may mention the product or company often. That still does not make the page the main home for that entity. Google says the structured data on the page should describe the content of that page.

A short review checklist

Before you publish identity markup across several pages, check this:

  1. each key entity has one clear canonical page
  2. the home page carries the organization layer
  3. person pages use person or profile style logic where that fits
  4. product or software pages own their own product identity
  5. support pages point back to those entities instead of replacing them
  6. sameAs, mainEntity, and mainEntityOfPage are used for the role they were built for
  7. the markup is tested with the Rich Results Test and reviewed again through Schema Debugging after release

How this fits the wider workflow

Entity identity across pages is one of the layers that keeps a site graph clean.

It sits close to Entity Markup, Markup Prioritization, and Schema Debugging. It also feeds directly into product, person, and company page decisions across the site.

If the identity layer is loose, the rest of the schema stack gets harder to maintain.

Final take

Entity identity across pages is about consistency, ownership, and page focus.

Give each key entity one stable home. Use the home page for the organization layer. Use person pages for people. Use product or software pages for the product itself. Use sameAs for outside identity references, and use mainEntity or mainEntityOfPage to show which thing each page is mainly about.

That is the cleaner route for a schema graph that holds together across the site.

FAQ

What is entity identity across pages?

It is the practice of describing the same entity consistently across multiple URLs so the site keeps one clear graph for that company, person, product, or software item. Schema.org’s page to entity properties are built for this kind of relationship work.

Should every page use mainEntity?

No. Use it when the page has one clear primary entity. Schema.org notes that some pages have one clear primary topic, while others refer to several things and are better described with broader topic relationships such as about.

What is the difference between sameAs and mainEntityOfPage?

sameAs points to an outside reference page that unambiguously indicates identity. mainEntityOfPage points to the page for which the thing is the main entity being described. They are related, but they do different jobs.

Where should organization identity start?

Google says organization structured data on the home page can help disambiguate the organization in search results, so the home page is the clean anchor for that layer.

What should I read next?

Go to Organization Schema, sameAs and Entity Identity, or Entity Markup.

Written by

Kevin Maguire

in