First, a screen we measured ourselves
96 / 100 grade A · our own home page, same scorecard we give you
The deduction sits on Snippet directives. We are not on 100 either, and the check names the line that costs us the rest.
Scoring rules v1.0
Here is how the number was reached. What each item is worth, what sends a page straight to the bottom grade, and where this scoring stops. Take the same table, open your own page, and check the result yourself.
| Item | Points |
|---|---|
| Indexing directives | 14 |
| Title tag | 12 |
| Meta description | 8 |
| One main heading (H1) | 8 |
| Canonical address | 8 |
| Snippet directives | 8 |
| Structured data (JSON-LD) | 8 |
| Share card tags | 6 |
| Image alt text | 6 |
| Mixed content | 6 |
| Heading order | 6 |
| HTML weight | 5 |
| Response time | 5 |
| Total | 100 |
What each verdict earns
- OK 100%
- Check 50%
- Fix 0%
Grade bands
- A · 90+
- B · 80+
- C · 70+
- D · 60+
- E · 0+
The first band a score reaches, reading down, is the grade.
What sends a page straight to the bottom
Indexing directives — Trip this one and the page lands at the bottom grade even if everything else is clean. It keeps the page out of results altogether rather than merely dimming it, so it sets the grade on its own instead of being averaged in with the rest.
Where this scoring stops
A scorecard that hides its own edges is hiding how much it knows. So we print them here.
- It checks whether something is there, not whether it worked.
- It reads one address. Site-wide structure and links between pages are out of range.
- It reads the HTML as delivered. Values filled in later by JavaScript are invisible to it.
- It does not predict rankings or AI answer citations. A perfect score here is a separate question.
- The weights are ours. They are not the weights a search engine uses.
Our own score, on this same table
We put our own home page through the same ruler and print what came back that day.
Score 96
Grade A
Weight actually measured 100 / 100 points' worth
Where points came off Snippet directives
Page measured https://citeangle.com/en/ · Measured on 2026-08-04
Our number comes out of this table too. Change the page and the number moves with it.
Who built this scoring
A name, and the things that name made. Open a link and there is something on the other side.
What you saw here / what the paid tier adds
| Free ends here | On the paid tier |
|---|---|
|
|
What splits them — How many pages, and who does the fixing
The first paid rung is $399. See the diagnostic ladder →
That is the free read. Working out which fix moves the needle first, making the change and measuring it again is what the paid audit and the improvement programs are for.
Two free things — what is different
| This page check | Free CMO check | Paid audit | |
|---|---|---|---|
| What gets read | One URL, the basics search and AI read first | One brand, up to 3 questions, 6 AI answer surfaces, competitors on the same row | More questions, more surfaces |
| How long | Right here on this screen | We run it and mail you the results page | Typically 1–3 business days from measurement start |
| What it takes | Just the URL | An email address. No card, no call. | Payment |
| What you get | This screen | A results page in your inbox | The same questions repeated seven times, with confidence intervals |
| How often | 3 a day, 10 when you sign in | Once a month | Every round |
Get your free AI visibility check
Start the free check here
One minute, no card, no meeting. Three questions are on us — write the ones your buyers would put to an AI, and we run them exactly as you wrote them and mail you the results page.
Each question goes to 6 AI answer surfaces. Send 3 and that is 18 observations in all, and we count how many of them came back with your name.