Example data
What a weekly report looks like
This page is not written by hand. It was produced by running Tidypage's own scanner against a small example site, and every number below comes from that run. The site, the pages and the forms are fictional.
Site checked https://example-site.test/
Checked 18 October 2026
Links checked 7 · Forms found 4
Summary
Broken 2 links Could not tell 1 link Fine 4 links
On a bigger page we work through the links in turns and the report says how many we checked. A link we cannot see is never counted as broken.
What this check found
1. The status endpoint answers with a server error
What we saw. Requesting /api/status returns 500.
Why it matters. A 500 means the server tried and failed. If that endpoint feeds a status badge, visitors are seeing an error.
What to do. Check the server log for that route around the time of the check.
2. A pricing link points at a page that no longer exists
What we saw. The “Pricing (2025)” link answers 404.
Why it matters. Anyone who follows it from the footer, a bookmark or an old email lands on a dead end with no way onward.
What to do. Point it at /pricing, or delete it and let the redirect do the work.
3. One page refused our check, so we say we could not tell
What we saw. /partners answers 403 to a read-only request.
Why it matters. That is usually a bot rule or a login wall, not a broken link. We will not call it broken, because we cannot see it.
What to do. Nothing, if the page is meant to be private. If it should be public, check your bot rules.
4. The newsletter form posts to an endpoint that is gone
What we saw. The form posts to /api/newsletter, which answers 404.
Why it matters. A visitor who types an address and presses Subscribe gets nothing, and you never see the address.
What to do. Point the action at your live list, or restore the endpoint.
Smaller notes on the forms
- Check booking: form uses mailto:, which fails for visitors without a mail app
- Check search: no submit button found (may be added by JavaScript)
- Note question: submits through JavaScript, endpoint cannot be checked without a test submission
The report itself
The email is plain text, so it reads the same on a phone, in a client that blocks images, and in a plain-text archive. This is the body of the email for the run above.
Weekly check for https://example-site.test/ Run: 18 October 2026 09:12 UTC Links checked: 7. Problems: 2. Could not tell (site blocked our check): 1. Forms found: 4. With problems: 1. Link problems: - https://example-site.test/api/status [server-error 500] - https://example-site.test/pricing-old [broken 404] Form notes: - form "newsletter" (post, action /api/newsletter): error: endpoint broken (HTTP 404) - form "booking" (get, action mailto:[email protected]): warn: form uses mailto:, which fails for visitors without a mail app - form "search" (get, action /search): warn: no submit button found (may be added by JavaScript) - form "question" (get, action javascript:void(0)): info: submits through JavaScript, endpoint cannot be checked without a test submission We only read your pages. We never submit your forms. A form endpoint that answers is not proof the form works end to end.
What this report does not claim
- A page that refuses our check is reported as “could not tell”, never as broken.
- A form endpoint that answers is not proof the form works end to end. We never submit your forms.
- We check the one page you give us, without running JavaScript, so links that only appear after scripts load are not seen.
One page, checked every week
$12 a month. Cancel any time, full refund within 14 days of your first payment.
Questions? Write to [email protected].