Verify existing sameAs links

What does this finding mean?

The report identifies this check as entity-profiles in Authority and entity. The category carries up to 18 of the 100 rubric points. This is a category weight, not an automatic deduction for this finding. Read the scan detail for the measured state, overlapping signals and any score cap.

Open each profile and confirm it belongs to the exact entity described by that schema node.

Why does this matter for AI retrieval?

A named publisher, an official URL and accountable authorship help a reader identify who is making a claim. sameAs links can disambiguate that identity. They do not prove trust or a citation advantage in any AI engine.

How do I check and resolve it?

1. Identify the organization or person responsible for this route. Match the visible name, official URL and description to the same entity in schema.
2. Add a useful about or contact page and link it visibly. For authored articles, show a real byline and connect it to a Person node.
3. Add external profile links only after checking the identity. An organization without Wikipedia or Wikidata can still have complete identity and accountability evidence.

Adapt the example to the reported issue and the actual route. Placeholder names, URLs and dates must be replaced with facts from your site.

Copy code

<p>Published by <a href="/about/" rel="author">Actual publisher</a>.</p>
<p><a href="/contact/">Contact the publisher</a></p>
<!-- Add only profiles that belong to this exact entity. -->
<script type="application/ld+json">
{"@context":"https://schema.org","@type":"Organization",
 "@id":"https://example.com/#publisher","name":"Actual publisher",
 "url":"https://example.com/","description":"Actual publishing purpose"}
</script>

Verify the result

Read the route while signed out. Follow the about, contact and author links. Check that each sameAs page describes the same entity, then rescan.

Open the related tool or technical guide, then run a new scan of the affected URL. Keep unknown checks marked unknown until you have a complete response.

Copy a prompt for your coding agent

Paste this into Codex, Claude Code or Cursor from your own repository. Include the scan's exact URL and detail so the agent can verify the observation.

Copy prompt for coding agent

Investigate the scanner finding "Verify existing sameAs links" (entity-profiles) in this repository.
Observation: Supported external profile links were detected. Presence does not confirm ownership.
Required change: Open each profile and confirm it belongs to the exact entity described by that schema node.
Inspect the existing route, shared layouts and configuration first. Confirm the finding against the actual response before editing. Preserve intentional access restrictions, existing content and unrelated changes. Use only factual identity and date values. Make the smallest appropriate fix, verify the deployed HTML or resource response and run the relevant project checks. Explain any measurement that remains unknown. Do not promise search rankings or AI citations.
Reference: https://letthebots.in/fixes/entity-profiles/