Free website identity diagnostic
Check how clearly your website identifies the business and its entities
Enter a public hostname to compare the visible business name and opening copy with the Organization, WebSite, Person, or SoftwareApplication entities declared in the homepage JSON-LD.
The result shows public identity and consistency signals that a retrieval system can inspect. It does not prove external knowledge-graph recognition, profile ownership, trust, ranking, citation, or recommendation.
Observed website result
Check result
More free checks
Try the other free AI discovery checks
Each check looks at a different layer of AI discovery readiness. Run them together for a fuller picture, or open the complete audit for all of it at once.
Enter a public hostname to test whether its deployed robots.txt policy allows, blocks, or has no matching restriction for documented AI crawler tokens at the root path.
Enter a public hostname to inspect its root-level llms.txt response, title, introduction, sections, links, malformed Markdown, duplicate destinations, and insecure URLs.
Enter a public hostname to inspect Recipe entities declared in its homepage JSON-LD and see which of Google’s documented required and recommended Recipe properties were observed.
Fill in a title, short context, and the resource links you want to list, and this page builds a valid llms.txt file for you to review, edit, and publish.
Choose a declared policy goal and this page builds robots.txt groups for the documented AI crawler tokens that goal has an explicit preference for, which you can review, edit, and publish.
Fill in your business name, canonical URL, logo, and official profile links, and this page builds a valid Organization JSON-LD block for you to review, edit, and publish.
Paste a prompt and the source an AI answer cited. See which public evidence differs from your site, what is worth testing, and what no external audit can prove.
What this check looks for
See the public evidence behind the result
OpenForBots examines the relevant public page or resource, shows what it found, and explains what to review next.
- 1
Retrieves the deployed homepage and inspects its initial server-delivered HTML.
- 2
Reviews whether the title, H1, and opening copy expose a clear public identity and offer.
- 3
Parses JSON-LD and identifies supported Organization, WebSite, Person, and SoftwareApplication entities.
- 4
Checks stable @id values, visible-name alignment, logo or image properties, and sameAs profile links.
- 5
Shows common About, Contact, Privacy, Legal, publisher, and author relationship signals when present.
Example evidence result
The visible brand and Organization entity align, but the entity lacks a stable identifier
The live result uses the deployed page or resource and exact check time. This example shows the evidence structure, not a claim about a real domain.
- Visible homepage name: Example Product
- Primary structured entity: Organization — Example Product
- Name consistency: aligned
- Opportunity: add a canonical @id such as https://example.com/#organization
Confirm the public name is intentional, add only accurate entity properties and relationships, then re-run the check after the deployed homepage changes.
Understand the result
What the check confirms—and what it cannot tell you
What it can confirm
- Which visible identity and business-clarity signals were present in the retrieved homepage HTML.
- Which supported JSON-LD entities, names, types, properties, and stable identifiers were observed.
- Which public profile relationships and common trust-page links were exposed at check time.
What remains unknown
- A consistent public identity does not prove that an external provider recognizes the entity.
- Structured data validity does not guarantee indexing, rich results, ranking, retrieval, or citation.
- sameAs links are declared relationships; this check does not verify ownership of every external profile.
- Business-clarity findings use bounded language heuristics and still require human review.
Learn and take action
Related guides and methodology
Generate a starting Organization JSON-LD block from your business name, URL, logo, and profile links.
Read more AI discovery readiness checklistReview identity together with access, retrieval, content, remediation, and fresh verification.
Read more What is AI discovery?Understand how public identity and source clarity fit into discovery, retrieval, and answer formation.
Read more How the audit worksReview evidence labels, language heuristics, structured-data limits, and retrieval boundaries.
Read moreCommon questions
Questions about this check
Does valid Organization schema guarantee that AI systems understand my business?
No. The checker confirms what the deployed page declares and whether selected fields are internally consistent. It cannot prove external entity recognition, indexing, retrieval, citation, ranking, or recommendation.
What is a stable structured-data identifier?
A stable @id is usually a canonical URL with a fragment, such as https://example.com/#organization. It helps connect references inside structured data when it accurately identifies the same entity.
Are sameAs links required?
No. They are useful only when official, maintained profiles strengthen identity clarity. Adding unrelated or unverified profiles can make the public entity less trustworthy rather than more complete.