If your page “has schema” but rich results still don’t show, you’re in the most common WordPress situation: the markup exists, but it’s wrong, duplicated, or incomplete. One small issue—like an invalid URL or mismatched breadcrumbs—can trigger rich results test errors and quietly make Google ignore the entire set.
This schema markup guide 2026 walks through the failures I see most in real sites, and how to fix them without breaking your theme or plugins. We’ll cover structured data WordPress basics, the usual faq schema errors, common mistakes in localbusiness schema and organization schema, and a simple QA checklist you can reuse.
First: what “breaks” rich results (and what doesn’t)
A quick mindset shift:
- Warnings don’t always block rich results.
- Errors often do.
- Duplicates can confuse Google enough that it chooses none.
That’s why you can pass “some” tests and still get no rich results in the wild.
Step 1: Confirm the problem on the exact URL
Before you change anything, test the page itself (not your homepage, not a staging URL).
Run these two tests:
- Google’s Rich Results Test (best for eligibility)
- Schema Markup Validator (best for seeing the full graph)
If the Rich Results Test shows no eligible items, that usually means the markup isn’t valid for rich results, is missing required fields, or is being ignored due to conflicts.
The most common schema markup errors (and how to fix each one)
1) Missing required fields (the silent killer)
This is the classic: the schema type is correct, but required fields are missing.
Examples:
- FAQPage missing proper Question/Answer structure
- LocalBusiness missing address fields
- Article/BlogPosting missing headline, image, datePublished
Fix (WordPress-friendly):
- Identify which item has the error (the tool will name it)
- Add only what’s required—don’t pad the markup with random fields
- Re-test the same URL
Tip: If a plugin generates the schema, don’t “patch” it in three places. Fix it at the source or replace it.
2) Wrong schema type (good data, wrong label)
Google is picky about what types are eligible for what features. You may have perfectly valid JSON-LD, but the wrong @type.
Common examples:
- Using
Organizationwhere the page is clearly a local storefront and should beLocalBusiness - Marking a service page as
BlogPosting - Using
Productmarkup for a service (not a product listing)
Fix:
- Match type to the page’s real purpose
- Blog post → BlogPosting/Article
- Local business homepage → LocalBusiness + Organization (often together in a graph)
- Service page → Service + WebPage (and optionally FAQPage if you show FAQs)
If you’re not sure, keep it simple. One correct type beats five mismatched ones.
3) Duplicate schema plugins (two tools outputting the same thing)
This is the #1 WordPress cause of schema markup errors.
Common collisions:
- Yoast outputs WebPage + Organization
- A schema plugin outputs WebPage + Organization again
- A theme outputs breadcrumb schema on top of a plugin’s breadcrumb schema
- Rank Math Local SEO outputs LocalBusiness, while another plugin outputs LocalBusiness too
Result: duplicates, conflicting @id values, and Google choosing the wrong “primary” entity.
Fix: pick one source of truth.
- Decide which tool owns:
- Organization/LocalBusiness
- Breadcrumbs
- Articles/BlogPosting
- FAQs
Then disable schema modules everywhere else.
How to confirm duplicates fast:
- View Source → search
application/ld+json - If you see multiple JSON-LD blocks that repeat Organization/WebPage/BreadcrumbList, you’ve found it.
4) Invalid URLs (tiny typo, big impact)
Schema validators are strict. One malformed URL can throw an error that blocks the item.
Examples:
www.example.comwithout protocol (https://)- image URLs with spaces
- a
sameAslink that isn’t a real profile URL - telephone links formatted incorrectly
Fix:
- Ensure every URL is fully qualified:
https://… - Remove tracking parameters in schema URLs (keep them clean)
- For images: use the final, direct URL to the file
5) Image size issues (and missing image fields)
Images are a common reason rich results don’t show consistently. Sometimes the page has images, but schema references a tiny thumbnail or an image that blocks bots.
Common problems:
- image is too small
- image URL redirects
- hotlinked or blocked image host
- missing width/height (not always required, but helps)
Fix:
- Use a stable, crawlable image URL (hosted on your domain is safest)
- Use a reasonably large image (at least 1200px wide is a safe standard for article-style results)
- If you’re using ImageObject, include width/height when possible
6) “Review” schema misuse (this can get ignored fast)
One of the most common “looks fine” mistakes is adding ratings where they don’t belong.
Examples:
- Adding AggregateRating to a service page that doesn’t show real reviews on that page
- Marking testimonials as product reviews
- Marking a business’s overall rating on every single page
Google has been strict for years about review markup: it must reflect what’s visibly present and match the correct subject. If it’s misleading, Google may ignore it.
Fix:
- Only add review/rating markup when:
- the reviews are visible on the page
- the schema subject matches what’s being reviewed
- For local businesses, it’s often safer to show reviews on the page and mark up cautiously rather than sprinkling ratings everywhere.
When in doubt, remove review markup first. You can still rank without stars.
7) Breadcrumb mismatch (your breadcrumbs don’t match the page)
Breadcrumb schema problems often come from:
- breadcrumbs showing one structure in the UI, but schema showing another
- missing breadcrumb item positions
- breadcrumb URLs that don’t match canonical URLs
- multiple breadcrumb blocks from plugin + theme
Fix:
- Ensure only one BreadcrumbList is output
- Make sure breadcrumb URLs match the canonical URLs of those pages
- Confirm the breadcrumb trail matches what a user sees
If you use Yoast breadcrumbs, don’t also output breadcrumbs via another plugin or theme function.
A clean recommended stack (WordPress)
You don’t need a complicated setup. You need a consistent one.
Option A: One SEO plugin owns schema (simple and stable)
Choose one primary SEO plugin for most schema output:
- Organization/WebSite/WebPage
- BlogPosting/Article
- Breadcrumbs
Then add custom JSON-LD only where needed, like:
- a specific Service schema on a service page
- a custom FAQPage block on a FAQ-heavy page
This works well when you want control without fighting multiple tools.
Option B: Custom JSON-LD for key pages + minimal plugin schema
If your site has frequent conflicts, another clean approach is:
- Keep the SEO plugin for basic meta/SEO
- Disable its schema modules where possible
- Output custom JSON-LD on:
- homepage (Organization/LocalBusiness)
- key service pages (Service + FAQPage if needed)
- blog posts (BlogPosting)
This is the cleanest for technical teams, but it requires discipline so nobody adds a second schema plugin later “just to test it.”
The WordPress fix process (follow-along)
Step 1: Identify what item is failing
In the Rich Results Test:
- Find the exact item with errors (FAQPage, LocalBusiness, Article, etc.)
- Note the required fields missing or invalid properties
Step 2: Find where schema is generated
Common sources:
- SEO plugin (Yoast, Rank Math, etc.)
- Schema plugin
- Theme (some themes output breadcrumbs or organization data)
- Header/footer injection plugins
- Page builder templates
Step 3: Remove duplicates before you “repair”
Fixing fields while duplicates remain is like patching a leak while the faucet is still running.
Step 4: Re-test the same URL
Always re-test the same page after each change. Don’t change 10 things and hope.
QA checklist (copy/paste)
Use this before you ship changes:
Schema basics
- Only one tool outputs Organization/WebSite/WebPage
- @id values are consistent and unique
- All schema URLs are valid
https://URLs - No staging domains in schema
- No duplicate LocalBusiness or duplicate BreadcrumbList
Rich results
- Rich Results Test shows eligible items (where relevant)
- FAQPage has valid Q/A pairs and matches visible FAQs
- Article/BlogPosting has headline, image, datePublished, dateModified
- Breadcrumb schema matches on-page breadcrumbs and canonical URLs
Images
- Main image is crawlable and not blocked
- Image is large enough for rich results use
- No redirect chains on image URLs
Reviews
- No rating/review markup unless reviews are visible on the page
- The review subject matches the page (no misleading AggregateRating)
Need a second set of eyes?
If you’re stuck in a loop of rich results test errors, it usually comes down to duplicates, wrong types, or small invalid details that are easy to miss when you’re staring at JSON-LD.
If you want help with a clean, stable setup (without breaking your current site), DollySEO can audit the page, identify the exact schema source, and give you a fix plan that you can implement safely—especially if you need miami seo services.
If you want a quick mini-audit, send us the URL you tested and a screenshot of the error output, and we’ll tell you what to fix first. Our Miami SEO agency is here to help. Contact us today!