I shipped a fake AggregateRating to my own site. Then I caught myself.

Six days into launching Vantage I had zero users. I added an AggregateRating schema with fake numbers anyway.

It was day 6 after launch. The site had three signups, none of them paying. I was looking at how Jobscan and Resume Worded ranked, copying patterns, and I added an AggregateRating schema to my Organization markup.

The numbers I made up were small. "ratingValue": 4.7. "reviewCount": 23. Nothing flashy. Just enough to feel real.

I committed it. Pushed it. Then I went to make coffee, came back, and reread the diff before opening the next task.

And it hit me, very simply: I had just lied in JSON-LD on a page where the second visible bullet on my pricing page is "no fabrication." A user shopping me against Jobscan would not see those numbers — Google would. But Google was not the audience I had spent six months building for. The audience was the one person about to spend £5 trusting me.

I removed it the same hour. The commit message is in my git log if you want to read it: fix(seo): remove fabricated AggregateRating + Review schemas. Not subtle.

Why fake social proof is the easiest thing to build and the worst thing to ship

Schema.org markup is invisible to your users by default. It only renders if Google decides to. So the temptation is: a small lie in a hidden file gives me rich-snippet stars in search results, which gives me clicks, which gives me real users, which eventually backfills the lie into truth.

Three things break that logic.

1. Google's manual review team specifically looks for this

Google's structured-data quality guidelines explicitly forbid review markup that does not match user-visible reviews on the page. They treat fabricated AggregateRating as a manual-action offense, and "manual action" means a human at Google can deindex you. For a six-day-old site, deindexing is fatal.

2. The lie compounds the moment it works

If the fake stars worked and brought five extra users to the site, every one of them is now operating under a false impression. The product they bought from is "the one with 4.7 stars from 23 reviews." Refunds, complaints, and chargebacks land harder when the customer feels deceived than when they just feel disappointed.

3. You will forget where you put it

I made the change in a hurry. I did not document it. If I had not caught it on the same-day reread, it would have shipped to production and stayed there for months while I forgot the specific number I picked. Future-me would not remember whether 4.7 was true.

What I built instead — a live transparency counter from Supabase

The fix is not "be more careful with schema." The fix is "make social proof verifiable." So I built a homepage strip that pulls real numbers from Supabase: total signups, total analyses run, waitlist size. Cached at the edge for 10 minutes so the homepage hit is cheap.

When I shipped it, the numbers were 4 signups, 0 analyses, 1 on the waitlist. They are still small as I write this. The strip is on the live site at aimvantage.uk if you want to verify.

The math: 4 real signups beats 23 fake reviews. 0 fake numbers means the product cannot be fact-checked into shame.

The framing on the strip says "Live transparency · Updated every 10 minutes" with a small green pulse-dot. It is intentional. The pulse signals freshness; the framing signals "yes the number is small, no I am not hiding it."

The lesson I had to learn the hard way

You do not get to fake your way to legitimate growth. The temptation is largest when growth is smallest, which is exactly when faking is most likely to compound into a credibility hole you cannot dig out of.

The growth tactics I have shipped since (programmatic SEO, FAQ schema, IndexNow submission, brand disambiguation in Organization markup, comparison pages, sample analyses) are all real. They are slow. They will not 10x my traffic this week. They will compound.

If you are a solo founder five days from running out of money, none of this is a moral lecture. It is a mechanics warning. Faking is not a shortcut. It is a delayed self-inflicted ban.

Vantage is the AI job preparation tool I built to compress two hours of manual application prep into 90 seconds. £5 starter pack, never expires. Real signup count visible on the homepage if you want to verify how big or small we actually are.

For other founders building in public

• Audit your own schema for AggregateRating, Review, and FAQPage that does not match visible page content. Run it through Google Rich Results Test to see what Google sees.
• Replace fake "trusted by 10,000+ teams" lines with the real number, even when the real number is 4. Frame the smallness — "be one of the first thousand" beats "10,000+ users" because it is true.
• Keep one screenshot of every fake-looking thing you considered shipping, so future-you remembers what almost happened.
• If you have already shipped fake schema, remove it the same day you read this and let Google recrawl. The deletion is logged in your commit history, which is exactly the receipt you want.

I am not pretending I will never be tempted again. I am saying I caught it once and I want the receipt visible.