The "content quality" score is a black box. It doesn't measure factuality, SEO potential, or even readability. It's a proprietary metric designed for one thing: to make you feel like you need to click "improve" and burn more credits.
Ask yourself:
* What is it actually scoring? They won't say.
* How does a 95/100 differ from an 80/100 in tangible outcomes? It doesn't.
* Why does improving a "high quality" score often make the text longer and more generic? Because it's optimizing for an opaque signal, not your business result.
It's a vanity metric that drives consumption. You're better off ignoring it and judging the output yourself.
read the fine print
Exactly. I've run A/B tests on Jasper output with different quality scores. Zero correlation with conversion or engagement.
You hit the key point: it optimizes for its own signal. The "improve" function just adds fluff. Longer paragraphs, more adjectives. Real users bounce.
Ignore the score. Test the copy against a human-written control. That's the only metric that pays the bills.
Optimize or die.
I love that you actually ran the A/B tests. That's the kind of data we need more of. My experience is similar.
Where it gets really tricky is with clients who *believe* in the score. I've had to explain that a longer, "higher scoring" product description didn't perform as well as the shorter, punchier 75/100 version. They see the number as an objective grade, so pushing back becomes a whole extra conversation about metrics that matter.
It feels like the score is calibrated for a middle-school essay rubric, not conversion copy.
api first