How it works
A simple four-step workflow from audit to verified results
Go from finding issues to fixing them and proving the improvements.
Workflow
Scan, understand, take action, verify
- 1
Scan
Enter a website or supported sitemap and inspect public pages safely.
- 2
Understand
See clear explanations, evidence, affected pages and why each issue needs attention.
- 3
Take Action
Create developer-ready tasks, specify acceptance criteria and track the fix.
- 4
Verify
Rescan and confirm the fix worked. Identify unresolved findings and new regressions.
- Bounded, resumable crawls
- Audits run in short steps that save their progress, so a closed tab or a server restart doesn't lose work. Open the audit again and it continues.
- Coverage you can see
- Each audit lists what it couldn't do: page limits reached, pages that failed, sitemaps it didn't read. Results are never presented as more complete than they are.
- Comparisons that respect scope
- Comparing two audits separates regressions, resolved issues, first detections and issues the newer audit didn't re-check.
Worked example
One issue, start to finish
01 · Find
Canonical points to the wrong URL
- Observed
- Canonical is https://www.northwind-outdoor.example/tents/alpine-2p?utm_source=newsletter
- Expected
- Exactly one <link rel="canonical" href="https://www.northwind-outdoor.example/tents/alpine-2p">
<link rel="canonical" href="https://www.northwind-outdoor.example/tents/alpine-2p?utm_source=newsletter">
02 · Fix
rel=canonical tells search engines which URL should represent this content. Conflicting or wrong canonicals can lead them to index a different URL than intended.
Recommended action
- Output a single <link rel="canonical" href="https://www.northwind-outdoor.example/tents/alpine-2p"> in <head>.
- Check whether tracking parameters or a staging hostname are leaking into the canonical template.
Acceptance criteria, frozen on the task
- The page has exactly one rel=canonical link
- The canonical points to https://www.northwind-outdoor.example/tents/alpine-2pcanonical.equals(expected=https://www.northwind-outdoor.example/tents/alpine-2p)
03 · Prove
Before the fix
- The page has exactly one rel=canonical linkSaw: 1 canonical link(s)
- The canonical points to https://www.northwind-outdoor.example/tents/alpine-2pSaw: https://www.northwind-outdoor.example/tents/alpine-2p?utm_source=newslettercanonical.equals(expected=https://www.northwind-outdoor.example/tents/alpine-2p)
After the fix, re-fetched
- The page has exactly one rel=canonical linkSaw: 1 canonical link(s)
- The canonical points to https://www.northwind-outdoor.example/tents/alpine-2pSaw: https://www.northwind-outdoor.example/tents/alpine-2pcanonical.equals(expected=https://www.northwind-outdoor.example/tents/alpine-2p)
Verification passing
Two statuses
People move the work. Re-checks decide if it's fixed.
Set by your team
Workflow status
Where the work is. Moving a task to “Resolved” records a decision; it doesn't prove anything about the site.
- Open
- Triaged
- In progress
- Ready to verify
- Resolved
Set only by SiteSentry
Verification status
What the live page actually shows when it is re-fetched and judged against the task's frozen criteria.
- PassingEvery acceptance criterion holds on the live page.
- FailingAt least one criterion still fails. The task stays open.
- InconclusiveThe page timed out, was blocked or was truncated. Never counted as fixed.
Between audits the same rule applies: an issue counts as resolved only when a later audit re-examined its page and check and no longer found it. If the later audit skipped the page, the issue is shown as not re-checked, not fixed.
See what your site is actually serving.
Run a quick audit on a public URL, or explore the sample workspace first.