Structured data (schema) · Playbook
Structured-data remediation — high-level pointers (local fallback)
porygon’s audit tells you what is wrong with a page’s JSON-LD. The detailed, current
standards — exact required/recommended properties per type, rich-result eligibility rules,
worked examples — live in the team wiki (set OUTLINE + OUTLINE_API_URL and the report links them
directly). This file is the minimal high-level fallback for when the wiki isn’t configured:
direction only, deliberately not step-by-step, so there’s no detailed content to drift out of sync.
- Invalid JSON-LD — a
<script type="application/ld+json">block doesn’t parse; fix the JSON (trailing commas, unescaped quotes, HTML entities) so search engines can read it at all. - Missing required properties — the
@typeis present but lacks a property rich results require; add it or the item won’t be eligible. - Missing recommended properties — eligible but incomplete; fill the recommended fields to strengthen and enrich the result.
- Unrecognised
@type— the type name isn’t in the schema.org vocabulary (likely a typo); correct it to a valid type. - No structured data — the page emits none; add the JSON-LD for the types that page represents.
Full playbook → the team wiki’s structured-data reference (per-type standards, rich-result rules, examples). Configure the wiki to have porygon surface the live versions in its report.