JSON-LD entities have no @id
@id is a schema property that gives each entity, your organisation, a person, an article, a stable, unique web address acting as its canonical identifier. This check found none of your structured-data blocks declare an @id, so nothing on your site has this stable identifier attached. AI knowledge graphs (the systems that link mentions of the same real-world entity together across different pages and sites) use @id to recognise that a mention on one page and a mention on another refer to the same organisation or person. Without it, your entities are harder to de-duplicate and connect, weakening how confidently AI systems tie separate mentions of your business back to one identity. Your developer needs about 30 minutes. Add a canonical @id, for example https://yoursite.com/#organization, to your Organization, WebSite and Article JSON-LD blocks, and reuse that exact same @id consistently across every page rather than generating a new one per page. Consistency matters more than the exact format, so pick one pattern and apply it everywhere.
Why this matters
AI knowledge graphs (the systems that link mentions of the same real-world entity together across different pages and sites) use @id to recognise that a mention on one page and a mention on another refer to the same organisation or person. Without it, your entities are harder to de-duplicate and connect, weakening how confidently AI systems tie separate mentions of your business back to one identity.
How to fix it
Your developer needs about 30 minutes. Add a canonical @id, for example https://yoursite.com/#organization, to your Organization, WebSite and Article JSON-LD blocks, and reuse that exact same @id consistently across every page rather than generating a new one per page. Consistency matters more than the exact format, so pick one pattern and apply it everywhere.