Technical SEO specialists
Audit a site, read the evidence behind every finding, and spend your time on the ones that are both severe and certain.
Technical SEO, made verifiable
From SEO findings to fixes you can verify.
Audit your website, turn real evidence into developer-ready tasks, and check whether each fix actually worked, all in one workspace.
- No sign-up
- Respects robots.txt
- Evidence for every finding
Northwind Outdoor
www.northwind-outdoor.example
Site health
1
High
2
Medium
6
Low
Issue groups · 356 pages crawled · 139 checks
Top issues
- Issue shared by 90%+ of a template group (one fix)2 pages
- Required property missing for Google-supported type50 pages
- Product without offers/price50 pages
- Near-duplicate content (SimHash ≥ 90%)62 pages
Health by audit
Reads the HTML any platform serves
- WordPress
- Shopify
- Webflow
- Wix
- Squarespace
- Next.js
Features
Everything you need for complete SEO operations
From technical audits to verified fixes, SiteSentry helps you find issues, coordinate improvements and maintain your website's technical health.
Technical SEO audits
Crawl public pages safely and find technical issues, each backed by the HTML and HTTP responses SiteSentry actually received.
Learn morePlain-language explanations
Every finding says what was observed, why it matters and what to change, in plain words. Hypotheses are labelled and kept apart from measurements.
Learn moreFix queue
Turn findings into developer-ready tasks with an owner, notes and frozen acceptance criteria, then track them to done.
Learn moreVerification and comparison
Re-fetch a fixed page and judge it against its criteria. Compare audits to see what was resolved, what regressed and what wasn't re-checked.
Learn moreMulti-site workspace
Keep several websites, their important URLs, audit history and outstanding work in one place.
Learn moreReports and exports
Hand off audit summaries and developer briefs as CSV, JSON or a print-friendly report.
Learn moreHow it works
A simple four-step workflow from audit to verified results
Go from finding issues to fixing them and proving the improvements.
- 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.
In-Depth Inspection
Find it, fix it, prove it.
One issue from the sample workspace, as SiteSentry shows it: what was observed, what the developer must change, and the re-check that confirms it.
Northwind Outdoorhttps://www.northwind-outdoor.example/tents/alpine-2pSample data
01 · Find
HighVerified
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
Verification
Marking a task done isn't the same as fixing it.
SiteSentry keeps two separate statuses, so a closed ticket never passes for a fixed page.
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.
Who it's for
For the people who find, fix and report.
Agencies
Run several client sites from one workspace, export what you found, and show clients which fixes were verified after each release.
Developers
Get tasks with the offending HTML, the expected result and a check you can re-run yourself, instead of a screenshot in a ticket.
Methodology
It reports what it can observe, and says when it can't.
Every audit lists the pages it inspected, the ones it couldn't reach, and the limits it hit.
What it observes
- The HTML and headers each page returns
- robots.txt, XML sitemaps and redirect chains
- The status of internal link and image targets
What it marks as unknown
- Pages that timed out, failed or were blocked
- Pages over the size limit (truncated)
- Issues the latest audit didn't re-examine
What it doesn't claim
- Content added by JavaScript after load
- Rankings, traffic or Core Web Vitals field data
- That a change caused a ranking movement
FAQ
Questions, answered plainly.
What happens when I run a quick audit?
SiteSentry adds the site to your workspace and inspects up to 10 pages, one click deep from the address you entered. You watch it run page by page, then land on the results. For larger crawls, URL lists or sitemaps, use New audit in the workspace.
Is the sample audit real?
The websites are fictional and bundled with SiteSentry, but every finding, task and verification result in the sample was produced by the same engine that audits real sites. Sample data is labelled everywhere and never mixed into your own numbers.
Does SiteSentry render JavaScript?
No. It reads the HTML the server returns, as a crawler does on first fetch. Content inserted later by client-side JavaScript isn't seen, and the methodology page says which checks that affects.
Can it prove that a fix improved my rankings?
No. It can prove the page now meets the criteria the fix was meant to satisfy. Whether rankings move depends on things page HTML can't show; search-performance data would be needed for that.
Which addresses can it fetch?
Only public http and https sites on standard ports. Private, loopback and cloud-metadata addresses are refused, every redirect is re-checked, and response sizes and timeouts are capped.
Who can see my workspace?
This deployment has no user accounts: anyone who can reach it shares the same workspace. Run it privately for client work.
See what your site is actually serving.
Run a quick audit on a public URL, or explore the sample workspace first.