Features · Monitoring
The crawl nobody has to remember to run
Put a site on a daily, weekly or monthly schedule in your own timezone and PixyScan re-crawls it without anyone opening the app. Each run is compared against the previous run on the same branch and split into new, resolved and still open.
The parts
What this is made of
Each of these corresponds to a screen or an endpoint you can open today.
- The value starts with the second scan: that is the first time a finding means something changed.
- A score threshold per site, used by both the alert and the CI gate.
- Schedules survive a failed run — the next one goes ahead.
- 01
A schedule per site
Daily, weekly or monthly, set in the timezone you work in rather than the server's. Sites on different cadences do not have to share one.
- 02
Compared per branch
A scan records the branch it ran against and is only ever compared with the previous scan on the same branch. A staging crawl cannot pollute production's trend.
- 03
In-app alerts
Scan started, finished or failed; score dropped; score below your threshold. They land on the bell and on the Alerts screen.
- 04
Concurrency by plan
One scan at a time on the smaller plans, up to five on Pro — which is what stops a portfolio re-crawl from queueing behind itself.
In the product
Where you meet it
Captured from the running app, against a real crawl.
Where the line is
What this does not do
You would find out on the trial either way. This is cheaper for both of us.
Alerts are in-app only. Email and webhook delivery are not built — the mail service sends signup codes, resets, invitations and billing notices, and nothing else.
One of these a blocker for you? Tell us — it is the most useful thing we can hear.
Keep going
The other five capabilities
Each is a page like this one, with its own list of what it will not do.
The technical audit
Every discipline runs on every crawled page, producing a health score out of 100 weighted by severity.
Read itInventory you can interrogate
Pages, structure, crawlability, links, images and AI readiness are lenses on the same dataset — not separate scans and not separate products.
Read itA gate in your pipeline
Issue a per-site client secret, run one CLI command from CI, and read an exit code.
Read itReports and exports
Any completed scan renders on the server as a PDF, in three cuts: the problems, the strengths, or both.
Read itWorkspaces, sites and roles
A workspace holds sites, members and the subscription.
Read it
Run it against your own site
One site free, 500 URLs a month, no card. The second scan is where this starts being useful.
Free plan · 1 site · 500 URLs a month · all 100+ checks · no card