Common Mistakes

The 7 mistakes that kill your rich snippets

Most schema problems aren't technical — they're about understanding how Google reads and uses structured data. These are the mistakes that prevent rich results even when everything looks correct.

---

Mistake #1 — Creating a schema but not assigning it to a page

This is the most common mistake. You create a schema in Smart Builder, it looks great — but you forget to assign it to a URL. Schemafy stores it in the database but never injects it into any page.

How to spot it: In Rich Snippets Manager, the schema shows as "Active" but has no URL in the "Assigned to" column.

Fix: Edit the schema → scroll to "Assign to URL" → search for the page → save.

---

Mistake #2 — Schema that doesn't match the page content

If your FAQPage schema lists 5 questions but the actual page only shows 2 of them, Google may penalize or ignore the schema. The same goes for prices, ratings, availability — if it's in the schema but not visible on the page, Google considers it misleading.

The rule: Only put in the schema what a user can actually see on the page.

Fix: Review each schema against the live page. If the content changed, update the schema. If a field isn't on the page, remove it from the schema.

---

Mistake #3 — Letting two plugins output the same schema type

If you have Schemafy AND Yoast SEO both outputting an Article schema on your blog posts, Google sees two conflicting descriptions of the same page. This triggers Search Console warnings and can cause Google to ignore both.

How to spot it: Google Search Console → Enhancements → look for "Duplicate items" warnings. Or view page source and count how many application/ld+json blocks appear.

Fix: Go to Schemafy Dashboard → the conflict detector identifies which plugin is competing. Suppress that plugin's schema output from there.

---

Mistake #4 — Leaving required fields empty

Every schema type has required fields — fields that Google needs to even consider the schema valid. A Product schema without a name, a FAQPage schema with answers but no questions, a Recipe schema without a name — all of these fail validation silently.

How to spot it: Rich Snippets Manager → Validate All → look for red errors.

Common required fields by type:

• Product: name, offers (with price and priceCurrency)
• FAQPage: at least one Question with an acceptedAnswer
• Event: name, startDate, location
• Recipe: name, recipeIngredient, recipeInstructions
• Article: headline, author, datePublished

Fix: Edit the schema → fill in any empty required fields.

---

Mistake #5 — Adding schema to pages Google can't index

If a page is set to "noindex" (either in Yoast, Rank Math, or via a meta robots tag), Google won't index it. A page that isn't indexed can't have rich results, no matter how perfect its schema is.

Common pages with noindex by default: thank-you pages, checkout pages, admin pages, search results pages, paginated archives.

Fix: Don't waste time adding schema to noindex pages. Focus on your indexable content.

---

Mistake #6 — Using schema types that don't match the actual content

Using a Recipe schema on a blog post because it has a list and numbered steps, or using a Product schema on a services page — Google detects mismatches and ignores the schema.

The right schema is always the one that most accurately describes the content:

• Article/BlogPosting: for blog posts and editorial content
• Service: for services pages (not Product)
• FAQPage: only if the page literally has questions and answers
• HowTo: only if the page teaches how to do something step by step

Fix: If you're unsure which schema type fits, check the Schema Types section of these docs.

---

Mistake #7 — Creating schemas and never validating them

Many users create schemas and assume they're working. Schemas can break when you update page content, change URLs, or install new plugins. Without periodic validation, you might have errors that have been silently blocking your rich results for months.

Fix: Go to Rich Snippets Manager → Validate All → once a month. It takes 2 minutes and catches everything.