Skip to content
quoxcli

Read your site's health

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. CLI 0.3.1, checked 2026-10-15.

How healthy is my site?

One line of health per crawl, every page with its search numbers, and the full record for any one, checked against the CLI.

What you get: what a crawler and Google see on your site, in your terminal, with a hash you can check for every crawl.

Ask Quox

Section titled “Ask Quox”

Ask about your latest crawl in your own words:

quox · talking to Quox

How many URLs did my most recent SEO crawl cover, and how many returned OK?

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 4ms

◐ SEO │ summary ✔ SEO │ summary │ 30 crawls · 1.6s

⛓ AEE │ envelope opened · stream_success

Your most recent crawl (14 October 2026, 05:47 to 05:51 UTC, status complete) covered
902 URLs on quox.ai, and 901 of them returned OK. One URL returned an error.

That is slightly up on the day before, which had 899 URLs and 898 OK.

I can pull the issues list to identify the one erroring URL if you'd like.

18.1s · 1 tool · 0 approvals

A real turn on our own install (CLI 0.3.0, 15 Oct 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 15 Oct 2026 · test report mv8yk3

Quox read the SEO summary from your own warehouse and compared the latest crawl with the one before it.

Do it yourself

Section titled “Do it yourself”

1. The latest crawl

Section titled “1. The latest crawl”
health at a glance 
quox seo statuscrawl #421  2026-10-13T05:41:32Z  898/899 okward: seq 405 (witnessed 2026-10-13T07:10:08Z)root: 5dede9362a982af21948128b3b0dbc1aacfdb6eed8aa4f7d4de3d3993eb9be1borphans 3 · noindex 0 · no meta 0 · discovered-not-in-sitemap 261gsc: 512 urls with data · 15200 impressions · 110 clicks (2026-07-13..2026-10-11)quox seo crawls#421 2026-10-13T05:41:32Z complete 898/899 root 5dede9362a982af2… ward seq 405#408 2026-10-12T05:49:38Z complete 898/899 root fa9bff86fe6dd0fe… ward seq 393#395 2026-10-11T05:49:33Z complete 895/896 root ef871c282b43c013… ward seq 381
From a real run on our own install. Search numbers changed.
  • 898/899 ok: pages that answered properly, out of pages crawled.
  • orphans: pages nothing links to. discovered-not-in-sitemap: pages the crawler found that your sitemap leaves out.
  • root and ward seq: the crawl’s hash and where it sits in the witness chain.

2. Every page

Section titled “2. Every page”
pages, with search data 
quox seo urls --limit 5899 rows (showing 5)200  /  imp=2400 pos=3.8 inlinks=21/896200  /about  imp=1100 pos=6.9 inlinks=7/896200  /pricing  imp=310 pos=8.2 inlinks=25/896200  /blog/getting-started  imp=90 pos=11.7 inlinks=4/896200  /terms  imp=9 pos=13.1 inlinks=1/1
From a real run on our own install. Paths and numbers changed.

imp is search impressions, pos the average position, and inlinks how many pages link to it.

3. One page in full

Section titled “3. One page in full”
one page's record 
quox seo url /about{"path": "/about","status": 200,"bytes": 86031,"title": "About us · Example","canonical": "https://example.com/about","meta_robots": "index, follow","h1_count": 1,"structured_data_types": ["Organization", "WebSite"]}
From a real run on our own install. Page and values changed; trimmed.

What just happened

Section titled “What just happened”

You read your own warehouse: crawls your Quox ran and stored, joined with Search Console data. Nothing was fetched from a third-party SEO service.

Check it yourself

Section titled “Check it yourself”

Each crawl’s ward seq is a position in the witness chain, so every crawl can be checked against the record. Check a receipt shows how.

Undo

Section titled “Undo”

Nothing to undo: these only read.

Next

Section titled “Next”