Brand and entity metadata: inspect self-declarations

Identity is inferred conservatively from eligible site metadata and associated Organization declarations. Where identity is available, title, description and H1 brand substring patterns are counted. Declared organization names, sameAs URLs, llms.txt brand mentions and same-origin identity/help URL patterns are observed. Nonempty titles have a separate bounded check.

Exact brand omission is not an attribution defect. Declared sameAs URLs are not verified profiles. URL patterns do not prove page purpose or site-wide absence. Wikidata/Crunchbase eligibility and identity are not evaluated. Uncertain identity disables dependent brand checks rather than fabricating a name.

Review the actual site purpose and accurate self-declarations. Correct missing nonempty titles where appropriate; add organization data only for a real applicable entity. Verify profile ownership and notability manually before proposing identifiers. Never pad metadata to imply measured AI visibility.

<meta property="og:site_name" content="Example project">

This is a self-declared site name, not verified ownership or a knowledge-graph entity. It can support a bounded name inference but cannot demonstrate an AI mention.

Public measurement separates Confirmed issue, Advisory, Unknown, Not applicable and Observed pass. An observed pass applies only to an explicit bounded rule; absence of an emitted failure is not a pass. Missing prerequisites do not earn repair credit.

Start 0. If identity is inferred, add round(25 × title-hit ratio), round(10 × description-hit ratio), round(10 × H1-hit ratio). Organization name adds 10. Declared sameAs URLs add 10 for at least three, otherwise 3 per URL. llms.txt brand mention adds 5. Identity/help URL pattern adds 5 once. Actual attainable ceiling is 75/100, not 85: 15 external-identity points and 10 unused allowance points are not evaluated.

Legacy values are clamped to 0..100 and rounded. They are not readiness certification, risk indicators or predicted citation outcomes. Method changes do not rewrite historical records.

The observations above describe the local implementation, not guarantees from these sources. Protocol and provider documents help interpret purpose and perform checks this audit does not implement.

• Schema.org Organization
• Schema.org sameAs