Title, meta, OG, schema
Schema.org / JSON-LD
Invalid JSON-LD, missing Organization, or Rich Results Test errors — fix in Puluno SEO.
Typical symptom
Explorer reports schema_invalid, Rich Results Test fails, console JSON parse error.
Puluno modules
SEO
Undo change
Partial — see article
Issue codes
schema_invalid, schema_organization_incomplete
What you see
- Finding
schema_invalidorschema_organization_incomplete. - Rich Results Test — syntax error.
<script type="application/ld+json">with two JSON objects without an array (syntax error).- Client wanted “stars in Google” — schema without rating / product data.
Why it happens
JSON-LD must be valid JSON and types must match page content.
Common causes:
- Two SEO plugins output schema (Yoast + theme).
- Hand-pasted footer block with trailing comma.
- Organization missing
name,url, or logo. - Product schema without
offerson a shop. - Migration leftover blocks from another plugin.
What Puluno does
| Phase | Module | Action |
|---|---|---|
| Diagnose | Explorer | parse JSON-LD, block types |
| Apply | SEO | unify Organization / WebSite, remove duplicates where possible |
| Verify | Explorer + Rich Results | same URL — finding cleared |
Puluno does not guarantee rich snippets — only technically valid data.
Step by step
- Explorer → schema section — copy the failing block.
- Rich Results Test on homepage.
- Disable duplicate schema in theme / old plugin (see Yoast / Rank Math migration).
- Puluno SEO Center → fill Organization / LocalBusiness required fields.
- Verify: Explorer + Rich Results again.
- For Woo products: Product schema per template — gradually, not bulk without QA.
More: Schema & IndexNow.
Rollback — undo the change
Schema Apply can be reverted in Center.
Back up hand-written footer JSON before deletion.
When it is not Puluno
- Google declines rich result with valid JSON — Google policy, not a bug.
- FAQ schema on pages without FAQ — content issue.
- Non-WP site — schema in the build pipeline, not Puluno SEO.
Related situations
Module manual