How to read a scanner result without a developer

In short

A scanner report turns into three decisions and a short list for the web team. Read the grade as a band, look at the failed checks that sit on your main task, set aside checks marked not applicable, and send the rest as a numbered list with an owner for each. Do not make the score itself the goal.

Five steps

  1. Read the grade as a band, not a number. A move between bands means something; a move of two points inside a band usually does not.
  2. Find the failed checks that sit on your main task. A failure on a page nobody needs for the task can wait.
  3. Sort each failure into a decision or a technical fix. A blocked bot is a decision; a missing sitemap is a fix.
  4. Check what the tool left out. Some scanners exclude checks that do not apply to your kind of site, so a missing check is not always a pass.
  5. Send the list to the web team with an owner and a date, and re-run the scan when they say it is done.

What to ignore

Comparing your score with another site's, unless both were scanned the same day with the same tool. Treating a scanner as proof that agents will finish a task: it checks files and settings, while only a run of an agent shows whether the job finished. Chasing bonus checks before the essentials pass.

What the evidence says

Help a leader turn a scanner report into three decisions and a short list for the web team.

  • 5 Nov 2026

    Ora's home page on 5 Nov 2026 reported an average score of 44 across 145,922 sites scanned, with 7 percent at B or above (vendor-published).

    Vendor claim. Ora home page, read 5 Nov 2026
  • Read 4 Nov 2026

    Ora grades from A+ (95 to 100) through A (86 to 94), B (70 to 85), C (48 to 69), D (28 to 47) to F (0 to 27).

    Vendor claim. Ora methodology, read 4 Nov 2026
  • Read 4 Nov 2026

    Ora excludes checks that do not apply and bonus checks not earned from the denominator, so a product is not penalised for what it does not need.

    Vendor claim. Ora llms.txt, read 4 Nov 2026
  • Read 4 Nov 2026

    Cloudflare's free scanner at isitagentready.com checks discoverability, content accessibility, bot access control, protocol discovery and commerce.

    Is Your Site Agent-Ready? (Cloudflare, isitagentready.com), read 4 Nov 2026
  • Read 4 Nov 2026

    Ora scores the payment protocols (x402, MPP, ACP, UCP, AP2) so that supporting any one is enough and the rest show as not applicable.

    Vendor claim. Ora llms.txt, read 4 Nov 2026

Sources

  1. Ora home page (ora.ai), read 5 Nov 2026. Vendor claim.
  2. Ora methodology (ora.ai/methodology), read 4 Nov 2026. Vendor claim.
  3. Ora llms.txt (ora.ai/llms.txt), read 4 Nov 2026. Vendor claim.
  4. Is Your Site Agent-Ready? (Cloudflare, isitagentready.com) (isitagentready.com), read 4 Nov 2026.

Last reviewed