Launching a website is only the start. New pages get published, content changes and small mistakes creep in. Marker.io Monitoring keeps watch over your whole website and tells you when something breaks, so you can fix it before your visitors notice.
Why use Monitoring
Monitoring scans the pages you choose, on a schedule you set, and tests them against a list of standard rules called checks. You get:
Site-wide coverage, not a one-page snapshot.
History, so you can see how your website changes over time.
Ownership, so the owner of each check gets alerted when it starts failing again.
Clear fixes, with a screenshot, the affected element and a recommended fix for every issue.
Monitoring works best for websites that change often, like content-heavy sites, online stores and university sites. Marker.io feedback helps you catch issues before launch. Monitoring keeps catching them after.
If you're an agency, Monitoring fits your client work too. Your team fixes the development issues, and your client's team fixes the content issues, all in the same project.
What you can monitor today
Monitoring currently covers accessibility. Marker.io tests your pages against WCAG 2.1 AA or WCAG 2.2 AA, plus optional best practices, and gives you an accessibility score out of 100.
In the Monitor menu, you'll also see Content quality, Uptime monitoring, SEO & AEO and Compliance vault marked Soon. These modules are on the way.
ℹ The accessibility score is automated. It doesn't certify legal compliance or full WCAG conformance, and manual testing is still required. Learn more in Understanding your accessibility score and checks.
How Monitoring works
Domain: each project monitors one domain. To monitor another domain, create a new project, or replace the domain on this one.
Pages: you choose how many and which pages to monitor, from your sitemap or a list of URLs.
Scans: Marker.io scans your pages monthly by default. Depending on your plan, you can also scan weekly or daily, or only when you ask.
Checks: each scan tests your pages against a set of checks. Every element that fails a check becomes an issue.
You'll find Monitoring under Monitor in the left sidebar of your project.
Get started
Get started with Monitoring: set up monitoring and resolve your first issue.
Configure your monitoring settings: scheduling, site access, pages and accessibility level.
Understanding checks and issues: checks, issues, severity, fields and states in every module.
Understanding your accessibility score and checks: what your accessibility score means, and what's specific to accessibility checks.
How Marker.io calculates your accessibility score: the scoring method, weights and score levels.
Accessibility checks and their weights: every check and how much it counts.
How to manage checks and issues: owners, ignoring, resolving, rescanning and integrations.
Create reports with the Marker.io MCP server: client-ready reports from your monitoring data.
Troubleshooting
Scanner errors: what to do when Marker.io can't reach your website.
Troubleshooting scans and results: stuck scans, missing pages and issues that won't resolve.
Need Help?
If you have any questions, comments, or corrections, chat with us at the bottom right of our web pages.

