Verified against the live portal · 12 September 2026

Running scans

Five ways to scan, and when to use each.

The Pages list#

Pages in the sidebar lists every page Zylyn discovered on your site, with its score, issue count, trend, and when it was last scanned.

The Pages list. Each row shows score, issues, trend and last scan, with a Scan button per page.
The Pages list. Each row shows score, issues, trend and last scan, with a Scan button per page.

Pages that have never been scanned show — and read "Not scanned yet".

1. Scan a single page — 1 credit#

Click Scan on any row. Takes about ten seconds. Best for checking one fix or trying the product.

2. Scan the whole site — 1 credit per page#

Click Scan all pages at the top of the Pages list. You'll get a confirmation first:

Nothing is charged until you confirm. Scans run in the background — leave the page if you like.

3. Scan any URL on demand — 1 credit#

New scan in the top bar accepts any URL, including one on a domain you haven't added.

A page behind a login can't be reached from our servers. Mark it with This page is behind a login when you Add page on the Pages list, and scan it with the browser extension.

4. Ad-hoc scans#

A scan of a URL you haven't added as a tracked site is called an ad-hoc scan and appears under Ad-hoc scans. Handy for spot-checking a page before committing a site.

When you later add that domain as a site, existing ad-hoc scans fold into it automatically. A page you scanned on a site you already track, but that isn't in its Pages list yet, joins it with Add to its pages, which is free.

5. Re-audit after a fix — 1 credit#

Open any report and click Re-audit. This is how you confirm a fix worked. The page keeps its history, so the trend column shows the improvement.

Schedule automatic re-scans#

Settings → Scanning. Choose Change on a site, then Off, Daily, Weekly or Monthly.

Scan scheduling, set per site. Manual is the default until you change it.
Scan scheduling, set per site. Manual is the default until you change it.

Scheduling is off by default — nothing recurring happens until you turn it on.

Cost: ~1 credit per page per run. Budget carefully:

Site sizeWeeklyDaily
50 pages~215 credits/mo~1,500 credits/mo
500 pages~2,150 credits/mo~15,000 credits/mo

Weekly is the right default for most sites. Daily only makes sense if you deploy constantly.

Scans pause automatically when credits run out rather than failing silently or overbilling.

Looking for new pages — 2 credits#

Sitemaps shows where your pages came from (the sitemap, or links from the homepage when there is none), what the last look added or found no longer listed, and every look so far.

The Sitemaps screen. Sitemap-first with a shallow crawl fallback.
The Sitemaps screen. Sitemap-first with a shallow crawl fallback.

Click Look for new pages after launching new sections so they enter monitoring. New pages are not picked up automatically between looks. A look that finds nothing new is refunded, once an hour per site. A page the sitemap no longer lists stays on your Pages list until you remove it.

If a scan fails#

Failed scans are refunded automatically — in credit history the scan shows as one entry, marked Refunded. You don't need to ask.

Pages that are login-gated, JavaScript-only shells, or blocked by robots rules are the usual failures. Use the extension for the first case.