structured-data.dangling-id

InfoSEO audit

JSON-LD refers to an object by "@id" that no object on the page defines, so a reader of this page gets the id and none of the object's properties.

What to change

Define the object on every page that refers to it: put it in the same @graph with its @id, @type and properties (an article's author or publisher, for example), or write the properties inline instead of {"@id": ...}.

The documentation on developers.google.com

A finding of this rule on a page carries the exact edits for that page: the markup it quotes, and what to write instead.

When it runs

Runs on every SEO audit: of a page, a crawl, a build directory or HTML. Info is a best practice: worth doing, rarely urgent, and --no-info leaves it out. Each finding takes 1 point off the page's score.

The severity here is the rule's usual one: a finding can be raised or lowered when the page gives a reason.

Run it, or skip it

Check a page for this rule alone, after a fix for instance:

npx @rivi-software/agentic-seo-check audit https://example.com --rule structured-data.dangling-id

Or from an assistant, with the MCP tool seo_audit_page:

{
  "url": "https://example.com",
  "rules": [
    "structured-data.dangling-id"
  ]
}

To leave it out of an audit, pass --disable structured-data.dangling-id on the command, or disableRules: ["structured-data.dangling-id"] to a tool.

All 14 rules