Why this dimension exists
JSON-LD is how a model binds your brand name, domain and product into one entity instead of inferring three unrelated strings.
Why it carries 12%
Second highest. It is deterministic and fully in your control, and it is what makes entity disambiguation possible.
The rules it is scored by
Each rule is a single question the scanner asks about a page. Passing one adds its share of this dimension; failing it takes that share away. Every rule links to what it looks for and what evidence passes it.
- At least one <script type="application/ld+json"> block parses as JSON and declares at least one @-keyword (@context, @type, @graph or @id). A block containing only {} parses but declares nothing, so it does not count.5.0%
- Parsed JSON-LD contains an @type of Organization, WebSite, Person or LocalBusiness.4.0%
- Parsed JSON-LD contains an @type of FAQPage, Article, BlogPosting, HowTo, Product, SoftwareApplication or BreadcrumbList.3.0%
What this dimension cannot tell you
A single-URL scan reads one page. It cannot see the rest of the site, it cannot see how a model behaves over time, and it cannot see whether the page is actually cited for the queries that matter. Those are the parts of the picture a score of this kind is blind to, and they are listed in full on the methodology page rather than implied here.