Structured Data

The Structured Data parameter checks whether your page ships machine-readable JSON-LD that names what your content is. friendly4AI scans the page HTML for JSON-LD blocks (<script type="application/ld+json">), reads the @type tokens in each block, and matches them against a list of high-value schema.org types. A page scores 100 when it carries at least one key type or two or more valid JSON-LD blocks, 50 when it has a single block with no key type, and 0 when no JSON-LD turns up.

What this parameter measures

JSON-LD is content an AI system reads directly rather than guessing at from prose. The processor pulls every block's @type and checks it against the key schema.org types. Microdata can be folded in through an optional extractor, but that path is gated by configuration and off by default, so your score comes down to JSON-LD. Adversarial pages get handled too: the processor caps how many distinct types it records (SEC-6) and how large each JSON-LD block can grow before it parses.

Why structured data matters for AI-readiness

Structured data spells out what your content is. It declares whether a page describes an Organization, a Product, an Article, or a set of FAQ answers, so the engine never has to infer it from the surrounding text. Schema markup drives rich results, feeds knowledge graphs, and makes your entities easier for ChatGPT, Gemini, and Perplexity to extract and cite. When a page carries clear @type declarations, it reads as well-described and trustworthy, which raises the odds your facts surface correctly. Pair it with page metadata: together they are the entity signals AI crawlers read first.

How Structured Data is scored

Under the v4.5 methodology this Discovery parameter scores in three tiers and reports only the id=3 structured_data behaviour:

• Pass (100) — the page carries at least one key schema.org type (Organization, WebSite, Product, Service, FAQPage, BreadcrumbList, Article, HowTo, VideoObject, or Event, matched case-insensitively), OR two or more valid JSON-LD blocks are present, which signals rich coverage.
• Partial (50) — at least one JSON-LD block exists, but it carries none of those key types and stands alone. Markup is there, just thin.
• Fail (0) — no JSON-LD structured data is found on the page.

Malformed blocks get counted, but they never lift the score on their own.

How to fix Structured Data issues

• Add a JSON-LD block inside a <script type="application/ld+json"> tag that describes your primary entity (for example Organization and WebSite on the homepage).
• Use at least one key type from the list above. A single generic block with no key type tops out at Partial.
• When no single key type fits, add a second valid block, such as BreadcrumbList or FAQPage, to reach the top tier.
• Run your markup through Google's Rich Results Test so malformed JSON-LD gets caught before it ships.
• Keep the @type honest to the page content. Mislabeled schema erodes trust and can be ignored outright.
• Re-scan after you publish to confirm the blocks parse and the key types register.

Related parameters

• Page metadata
• Sitemap availability
• URL stability