Weak entity clarity: inventory owned contradictions
A weak-entity-clarity inventory compares explicit brand, product, operator, category, and URL relationships across visible copy, metadata, JSON-LD, and frozen authoritative records. It can identify contradictions and missing relationships the site operator controls; it cannot inspect an answer system's internal entity representation or explain a mention, citation, recommendation, or absence. Site traffic is a separate outcome and is not required.
What is the scope of a weak-entity-clarity inventory?
Use this method only after the operator can freeze supported identity relationships and capture the exact owned surfaces being compared. The unit is one assertion at one locator, not a domain-wide clarity score.
A contradiction means two inspectable records disagree under the declared reference. It does not mean an AI provider is confused, has ingested either record, or used the discrepancy in an answer.
Which reference relationships are frozen first?
SYNTHETIC EXAMPLE — Harborlight, Harborlight Systems, Inc., Harborlight Atlas, every URL, prompt, surface, assertion, patch, and outcome below are fictional; this is not RankEcho data, customer data, provider evidence, or a benchmark.
The fictional reference set separates the brand name, product name, legal operator relationship, category relationship, and brand-to-product URL relationship. Each has an effective time and a synthetic evidence pointer.
| Reference | Relationship | Frozen value | Authority and evidence |
|---|---|---|---|
| R01 | brand-name | Harborlight | Synthetic brand register signed by the fictional operator · synthetic-evidence/entity/reference/R01 |
| R02 | product-name | Harborlight Atlas | Synthetic product register signed by the fictional operator · synthetic-evidence/entity/reference/R02 |
| R03 | operator-relationship | Harborlight Atlas is operated by Harborlight Systems, Inc. | Synthetic corporate record and product register · synthetic-evidence/entity/reference/R03 |
| R04 | category-relationship | Harborlight Atlas is a supplier evidence workspace. | Synthetic approved product description · synthetic-evidence/entity/reference/R04 |
| R05 | url-relationship | Harborlight → https://harborlight.example/; Harborlight Atlas → https://harborlight.example/atlas | Synthetic domain and canonical-page register · synthetic-evidence/entity/reference/R05 |
Which surfaces and channels are inspected?
Capture the same deployed versions of the homepage, About page, product page, and documentation page. Inspect visible copy, metadata, and JSON-LD separately so agreement in one channel cannot hide a contradiction in another.
Do not invent an authoritative value from majority wording. When the underlying operator record is missing or disputed, mark the reference unresolved and stop the repair handoff.
What does the worked synthetic assertion ledger show?
Fifteen assertions cover the five frozen relationships. Nine align, five contradict their declared reference, and one locally predeclared product URL relationship is missing. All six actionable assertions remain attached to their locators and captures.
| Assertion | Surface and channel | Relationship | Observed value | State |
|---|---|---|---|---|
| I01 | homepage · visible-copy · main h1 | R01 · brand-name | Harborlight | aligned |
| I02 | homepage · metadata · meta[property='og:site_name'] | R01 · brand-name | Harbor Light | contradictory |
| I03 | homepage · json-ld · Organization.name | R01 · brand-name | Harborlight | aligned |
| I04 | product-page · visible-copy · main h1 | R02 · product-name | Atlas AI | contradictory |
| I05 | product-page · metadata · title | R02 · product-name | Harborlight Atlas | aligned |
| I06 | product-page · json-ld · SoftwareApplication.name | R02 · product-name | Harborlight Atlas | aligned |
| I07 | about-page · visible-copy · main p[data-operator] | R03 · operator-relationship | Atlas is operated by Harborlight Analytics LLC. | contradictory |
| I08 | about-page · metadata · meta[name='description'] | R03 · operator-relationship | Harborlight Atlas is operated by Harborlight Systems, Inc. | aligned |
| I09 | about-page · json-ld · Organization.legalName | R03 · operator-relationship | Harborlight Analytics LLC | contradictory |
| I10 | product-page · visible-copy · main p[data-category] | R04 · category-relationship | Harborlight Atlas is a supplier evidence workspace. | aligned |
| I11 | product-page · metadata · meta[name='description'] | R04 · category-relationship | Harborlight Atlas is a supplier evidence workspace. | aligned |
| I12 | product-page · json-ld · SoftwareApplication.applicationCategory | R04 · category-relationship | supplier evidence workspace | aligned |
| I13 | documentation-page · visible-copy · main a[data-product] | R05 · url-relationship | Harborlight Atlas → https://harborlight.example/atlas | aligned |
| I14 | product-page · metadata · meta[property='og:url'] | R05 · url-relationship | https://harborlight.example/platform/atlas | contradictory |
| I15 | product-page · json-ld · SoftwareApplication.url | R05 · url-relationship | Missing | missing |
How does the inventory arithmetic reconcile?
The projection records 4 surfaces, 5 reference relationships, and 15 assertions: 9 aligned, 5 contradictory, and 1 missing. The 6 contradiction-or-missing rows form the bounded Fix input.
These are record counts, not a quality percentage, provider confidence score, or prediction of an answer outcome.
Which false positives stop the diagnosis?
Stop when spelling variants are declared aliases, products legitimately have separate operators, a category statement is merely more specific rather than contradictory, a URL redirects under the frozen normalization rule, or the compared records have different effective dates.
Schema.org supplies a vocabulary and Google documents Search uses of structured data and site names. Neither source supplies a universal answer-system entity graph or confirms that a provider consumed the page.
What deterministic validation completes Find?
Another person must be able to reproduce every state from the reference, deployed version, locator, observed value, and evidence pointer. Unavailable captures stay unavailable rather than becoming contradictions.
Find completes on reproducible owned-publication evidence. A crawl, impression, mention, citation, recommendation, referral, or traffic observation is not required.
| Check | Pass condition | Evidence |
|---|---|---|
| Reference | Five supported relationships are frozen before site inspection | R01–R05 and effective times |
| Surface | Four exact deployed versions and URLs are captured | S01–S04 snapshots |
| Locator | Every assertion names one visible, metadata, or JSON-LD locator | I01–I15 locator fields |
| State | Aligned, contradictory, missing, unavailable, and failed remain distinct | Assertion values and state reasons |
| Arithmetic | Nine aligned, five contradictory, one missing, and six actionable rows recompute | Inventory projection |
| Boundary | No discrepancy is labeled provider confusion or cause | Interpretation record |
How does Find hand off to Fix and Prove?
Inspect the supporting records alongside the AI Visibility Audit, then hand only I02, I04, I07, I09, I14, and I15 to the bounded identity patch. Keep the aligned assertions unchanged.
After deterministic acceptance, the Prove route classifies four nonexclusive outcomes on the frozen prompt-surface panel. It does not treat later movement as evidence that an identity patch caused it.
What does RankEcho handle and what remains a companion record?
RankEcho can surface entity-clarity hypotheses and preserve prompt observations and sources. This cross-page operator-reference ledger is a companion method; the product does not currently calculate its 15-row projection or infer a provider's internal identity state.
Who maintains this guide?
Written and maintained by Abiot Y. Derbie. Published 2026-09-07; sources checked 2026-09-07; last updated 2026-09-07. The worked records are synthetic.
Recheck the operator's effective records and the linked documentation before applying the method. Send material corrections through the contact page.
Sources reviewed
Provider eligibility and measurement claims below were checked against primary documentation. These records do not establish a universal selection formula, causation, or a guaranteed ranking, impression, recommendation, or citation.
4 claim-level source records
| Claim reviewed | Official source | Review record |
|---|---|---|
| Google's Organization structured-data documentation defines properties including name, alternateName, legalName, url, logo, and sameAs, and advises using the same organization name and alternate name used for the site name. | Google Search: Organization structured data | Checked 2026-09-07 · Current Google Search Organization documentation · Primary-source Search documentation; it supports a bounded consistency check, not a universal entity graph, an AI-system identity verdict, or a citation mechanism. · Confidence: High |
| Google's site-name documentation recommends WebSite structured data on the home page and defines name, alternateName, and url properties for expressing a preferred site name. | Google Search: site names | Checked 2026-09-07 · Current Google Search site-name documentation · Search-specific documentation; it does not define a universal brand identity graph, provider confidence, or an answer-system ingestion or selection mechanism. · Confidence: High |
| Schema.org defines Organization properties including name, legalName, url, and sameAs for describing an organization and identity references. | Schema.org: Organization | Checked 2026-09-07 · Current Schema.org Organization vocabulary · Vocabulary definition only; using these properties does not verify a record or establish provider ingestion, ranking, citation, or recommendation. · Confidence: High |
| The Open Graph protocol defines og:site_name as the overall site name and og:url as the page object's canonical or permanent graph identifier. | Open Graph protocol | Checked 2026-09-07 · Current Open Graph protocol vocabulary · Protocol-field semantics only; the vocabulary does not establish provider consumption, entity resolution, ranking, mention, citation, recommendation, or another outcome effect. · Confidence: High |
Frequently asked questions
Two inspectable values disagree with a frozen authoritative relationship under the same effective date and normalization rule. A wording variation or narrower description is not automatically contradictory.
No. It proves only that the inspected publications disagree. It does not reveal ingestion, retrieval, an internal entity representation, or an answer-selection cause.
No. Freeze a supported operator or authoritative record first. Majority wording can repeat the same error.
No. Missing markup is one inspectable publication state. Add markup only when it truthfully matches visible content and serves a documented use.
No. It retains aligned, contradictory, and missing assertion counts and their evidence; it does not produce provider confidence or outcome probability.