WordPress And Schema Markup Errors: The Common Pitfalls

Schema markup errors are more common than site operators realize. Search Console's Enhancements section reports them; many sites ignore the reports. The errors range from minor (warnings that don't break functionality) to severe (errors that disqualify rich result eligibility).

The most common pitfalls are repetitive. Understanding them prevents recurrence and addresses existing issues efficiently.

Pitfall 1: missing required fields

Schema types have required fields. Article requires headline, image, datePublished, author, publisher. Product requires name, image, description, offers. Event requires name, location, startDate, image.

Missing a required field disqualifies the schema from rich result display. The schema is technically present but doesn't produce the intended benefit.

The diagnosis: Google's Rich Results Test shows which required fields are missing. The fix is adding the missing fields to the schema generator's configuration.

For SEO plugins (Yoast, Rank Math), the missing fields are usually due to: site Organization not fully configured, post-level fields (image, author) missing from the post, or the schema template requiring custom field values that aren't set.

Pitfall 2: image too small

Google requires images in schema to be at least 1200 pixels on the longest side. Smaller images don't qualify for rich results.

The error: schema is otherwise correct but the image specified is 800x450. The rich result test reports the size issue.

The fix: ensure featured images and any schema-referenced images meet the size requirement. Bulk-update small images if needed.

For sites that regularly publish posts with small featured images, the photographer or content team needs to know the minimum sizes.

Pitfall 3: logo missing or wrong format

Publisher schema requires a logo. Google has specific requirements: square or close to square, ImageObject format, accessible URL.

The error: the logo is configured but doesn't meet requirements. Maybe it's not a real image URL; maybe it's a CDN URL that doesn't resolve cleanly; maybe it's a small thumbnail rather than a proper logo.

The fix: ensure the site's logo is configured in the SEO plugin or theme settings as a proper image, sized appropriately (at least 112x112, preferably larger).

Pitfall 4: date format issues

Dates in schema must be ISO 8601 format: YYYY-MM-DDTHH:MM:SS+TZ. Other formats are rejected.

The error: dates appearing in unusual formats. Sometimes from custom code that didn't format correctly; sometimes from older content that has irregular date data.

The fix: ensure date emission uses get_the_date('c') or similar function that produces ISO 8601 format.

Pitfall 5: structured data describing nonexistent content

The schema claims FAQ content but the page doesn't have visible FAQ. The schema claims breadcrumbs but no breadcrumbs render. The mismatch is detected by Google's structured data validation.

The error: schema describes content that isn't actually on the page. Google may flag this and disqualify the rich result.

The fix: ensure schema reflects actual page content. If the page has visible FAQ, FAQ schema is appropriate. If not, don't include FAQ schema.

Pitfall 6: duplicate schema blocks

The page has multiple schema blocks describing the same content with potentially different data. The conflict produces ambiguity.

The cause: usually multiple plugins emitting overlapping schema. SEO plugin emits Article schema; a separate schema plugin also emits Article schema. Both run; both appear in the page source.

The fix: configure one source of schema. Disable schema features in plugins that aren't the primary source. Verify by checking page source: each schema type should appear once.

Pitfall 7: schema in iframes or after JavaScript renders

Some sites embed schema in iframes or render schema via JavaScript after page load. Google's crawler sometimes misses these.

The cause: the schema isn't in the initial HTML. Crawlers that don't fully execute JavaScript miss it.

The fix: schema should be in the page's initial HTML, in the head or body. Inline JSON-LD is the standard pattern.

Pitfall 8: invalid schema type combinations

Some schema combinations don't make sense. Combining BlogPosting with Product on the same page produces confusion about what the page actually is.

The cause: trying to emit every possible schema type that might apply.

The fix: emit schema that matches what the page primarily is. If the page is a blog post about a product, BlogPosting is appropriate; the product information is a topic, not the page's identity.

Pitfall 9: incorrect parent-child schema relationships

Schema can include nested objects (Article has an author Person, Product has an Offer, etc.). The nesting must be correct.

The error: properties at the wrong level. The author's name appearing as an Article property rather than inside the nested Person object.

The fix: validate the schema structure against the Schema.org documentation. Use the Rich Results Test to verify nesting.

Pitfall 10: rating schema without supporting content

AggregateRating schema (star ratings) requires actual reviews or ratings on the page. Schema can't fabricate ratings.

The cause: sites adding rating schema hoping for the visual benefit without having actual ratings to back it up.

The fix: only emit rating schema for pages that genuinely have ratings or reviews visible. The schema describes content, not invents it.

Google has been increasingly aggressive about penalizing this pattern. Sites caught faking ratings have lost search visibility broadly.

The diagnostic tools

Google Rich Results Test (search.google.com/test/rich-results): test any URL for rich result eligibility. Shows what schema is detected and what errors exist.

Schema.org validator: more comprehensive but less Google-specific. Useful for general validation.

Google Search Console Enhancements: aggregate view of schema errors across the site. Identifies systematic issues.

Browser extensions like Schema App that decode and visualize schema on any page.

The audit workflow

For sites with significant content and schema:

1. Search Console Enhancements: review the report. Identify error categories and counts.

2. For each error category, pick a few representative URLs and run them through Rich Results Test.

3. Identify the root cause: missing field, wrong field type, plugin configuration, theme template issue.

4. Fix at the source rather than per-URL. The fix usually addresses many URLs simultaneously.

5. Verify with Rich Results Test on a few URLs to confirm the fix.

6. Monitor Search Console Enhancements over the following weeks to see the error counts decrease.

The honest framing

Schema errors are usually fixable with moderate effort. The systematic nature of most schema generation means fixing the source fixes many URLs at once.

The benefit of correct schema: eligibility for rich results, clearer signals to search engines, better understanding of content. The cost of incorrect schema: missed rich result opportunities, sometimes algorithmic deprioritization if errors are interpreted as low quality.

For sites that haven't reviewed schema in a while, an audit is worth the time. The errors that exist are probably fixable; the fix produces both immediate improvement and signal that the site maintains quality.

The discipline: when adding new schema types, verify with Rich Results Test before assuming they work. The verification catches errors before they accumulate.