Why is my schema not showing review stars or rich results?

It’s usually one of three things: either your JSON has a small syntax error (like a missing comma), you're missing a field Google considers mandatory (like an image for articles), or your schema data doesn't match the actual text on your page. Google is very protective of its user experience and won't show results it thinks are broken or misleading.

Can I just put a comma after every item in JSON?

Unfortunately, no. Standard JSON is strict: the very last item in a list or object must NOT have a comma after it. It's one of the most annoying errors to catch because it looks fine to the human eye but makes the machine give up.

Common Schema Errors (and why Google is ignoring you)

We've all been there: you spend an hour meticulously crafting structured data, only to find that Google Search Console is still throwing errors or, worse, your review stars aren't showing up. Don't worry—most schema issues come down to a few tiny details that are easy to overlook.

1. The "Invisible Comma" and Syntax Traps

JSON is like that one friend who is incredibly picky about grammar. A single missing quote or an extra comma can make the entire block unreadable to search engines.

The usual suspects

The Trailing Comma: Putting a comma after the last item in a list. It’s fine in some languages, but it breaks standard JSON.
Quotes Matter: Always use double quotes ("). JSON hates single quotes (').
Messy Copy-Paste: Sometimes, hidden "smart quotes" from Word or Slack can sneak in and ruin your code.

2. The "Must-Haves" Google Demands

Think of Schema like a job application. If you don't fill out the required fields, you're not getting the job. Each type has "Recommended" fields (which are nice to have) and "Required" fields (which are deal-breakers).

Common Trip-up: If you're marking up an Article, Google needs an image and a headline. If either is missing, you won't see those rich snippets in search results.

3. Reality vs. Markup (The Data Mismatch)

Google doesn't like being lied to. If your schema says your product costs $19, but your page text clearly says $49, Google will likely ignore your markup entirely. Always make sure your code matches what a human sees on the screen.

4. The "Russian Doll" Problem (Improper Nesting)

Schema is often nested—like putting a Review inside a Product. If you don't close your curly brackets {} in the right order, it's like failing to close a box inside a box. It makes a mess that crawlers can't understand.

Tired of manual errors? Let us generate a clean block for you:

Try the Schema Generator →