A homepage often names itself more than once. The browser title may carry the new company name while its share card still uses the old brand. A JSON-LD block copied from another template may describe a different entity again.
These differences can have legitimate explanations: a product and its parent company need not share a name. The problem is an unexplained contradiction. MachineRead compares selected page and entity fields to help locate metadata that no longer describes the intended public identity.
Share metadata is a page claim
The Open Graph protocol describes four required properties for every page: og:title, og:type, og:image, and og:url. Its definition of og:url calls it the canonical URL of the object, used as the object's permanent ID in the graph (Open Graph protocol).
That is a strong reason to keep share metadata aligned with the visible page. If the page title says "Acme Research," og:title says "OldCo Labs," and og:url points at a retired host, the fetched HTML is carrying conflicting publisher declarations.
It is still only a publisher declaration. An Open Graph tag does not prove that a platform rendered a card, trusted the value, selected the image, or connected the page to a social account.
Entity fields need the same discipline
Schema.org gives publishers a vocabulary for saying what an item is. In the current Schema.org vocabulary, name is "The name of the item," logo is "An associated logo," and url is the "URL of the item." The vocabulary also declares og:title equivalent to name and og:url equivalent to url (Schema.org, "Current Schema").
Those equivalences make comparison reasonable. If a page publishes og:title, og:url, a canonical URL, and an Organization JSON-LD object, those fields should not contradict each other without a reason visible on the page.
Schema.org defines sameAs as a reference-page URL that unambiguously indicates the item's identity, with examples such as the item's Wikipedia page, Wikidata entry, or official website (Schema.org, "Current Schema"). Use it for pages identifying the same entity, not merely related organizations or topics. MachineRead can inspect whether those declarations are present and whether recognized platform categories overlap with visible profile links.
But a sameAs value is not account verification. It does not prove that the publisher controls the destination, that the profile is current, that the organization is notable, or that the destination agrees with the relationship. It is a field in the fetched page.
What MachineRead observes
MachineRead's Social & Entity Metadata check inspects one fetched homepage response. It parses title and description text, the canonical link, selected Open Graph and Twitter card tags, JSON-LD entity names, JSON-LD sameAs values, and JSON-LD logo or image URLs.
The check then looks for internal consistency. It compares og:title with the page title, og:description with the meta description, and og:url with the canonical URL. It checks whether Twitter card text lines up with Open Graph or page text. It checks whether schema entity names align with page or social metadata, and whether schema sameAs platform categories overlap with visible profile links.
The comparison is deliberately modest. Text alignment uses normalized equality, containment, or token overlap. URL matching normalizes HTTP and HTTPS URLs. Platform matching recognizes a fixed set of common profile URL patterns. The result is a 0 to 2 point finding inside the Essentials audit, not a social graph investigation.
How to use the finding
Start with the page source MachineRead fetched. Check the visible title, meta description, canonical link, Open Graph tags, Twitter card tags, and JSON-LD entity object side by side.
If the names disagree, decide which public name the page should publish and update the templates that emit the stale values. If og:url and the canonical URL disagree, fix the URL source rather than adding another alias. If schema name, url, logo, or sameAs came from an old organization profile, remove or update the stale field.
For profile links, keep the claim local. A GitHub, LinkedIn, YouTube, X, or other recognized URL in page markup can be a useful declared signal. Treat it as something the homepage published, then verify account control through the platform or organization process you actually use. MachineRead does not do that verification for you.
What this check can and cannot establish
The check can establish whether the fetched homepage exposes selected social and entity metadata, whether those fields are internally consistent, and whether recognized profile-link categories appear in page links or JSON-LD sameAs values.
It does not verify profile ownership or inspect the current state of third-party accounts. The observation concerns selected fields on the fetched page, not the entire site or its external reputation.
After a rebrand or template change, use the finding to check that each field describes the intended entity. Verify the external profiles separately.
Works Cited
Open Graph protocol. "The Open Graph Protocol." The Open Graph Protocol, https://ogp.me/. Accessed 9 Sept. 2026.
Schema.org. "Current Schema." Schema.org, https://schema.org/version/latest/schemaorg-current-https.jsonld. Accessed 9 Sept. 2026.
See also
- Methodology reference - documents the Social and Entity Metadata check group
- Why agents need to read your site - separates fetch, policy, delivery, and interpretation
- Related: schema.org JSON-LD and AI catalog