Something not looking right in Monitoring? Find your question below. If the scanner showed you an error message, go to Scanner errors instead.
My scan is stuck
First, give it a few minutes and refresh the page. Scans sometimes take a moment to start.
If your scan is still stuck, at 0% or any other percentage, cancel it and start a new scan.
If it stays at 0%, the scanner hasn't started scanning your website. Something is usually stopping it from reaching your website:
Bot protection: services like Cloudflare, Akamai or AWS WAF are blocking the scanner.
Authentication: your website is behind a login, a password prompt or session cookies.
Rate limiting: your website or CDN is throttling the scanner's requests.
Scanner errors explains how to fix each one.
Still stuck after a few tries? Chat with us and include the URL you're scanning.
Why isn't Marker.io scanning all my pages?
Marker.io only scans the pages in your page list. It doesn't follow links to find new pages.
Check how your pages are selected:
Go to Project → Settings → Monitor.
Open the Pages tab.
Under Page management, see whether Sitemap or List of URLs is selected.
If you use List of URLs, Marker.io only scans the URLs in that list. Add the missing pages to your list.
If you use Sitemap, Marker.io only scans pages listed in your sitemap. Check these:
Is the page in your sitemap? If not, add it to your sitemap, or add it under Forced pages.
Is it new? Marker.io checks your sitemap every 15 minutes, so a new page can take a little while to appear.
Is it excluded? Check your URL exclusions. A rule like "URL contains /blog" skips every blog page.
Have you reached your page limit? Marker.io won't add new pages once your limit is full. To raise it, click Manage page limit on the Pages tab of your monitoring settings.
To see every page Marker.io scans, go to Monitor → Pages.
I fixed an issue, but it's still showing
Issues stay open until a scan checks them again. Rescan to update the result:
One issue: open the issue and click Rescan.
One page: go to Monitor → Pages and click Rescan next to the page.
Every page: click Rescan website on the Overview page.
Still showing after a rescan? Check these:
Is the fix live? Marker.io scans your published website, not your local or staging copy.
Is the page cached? If your site uses a CDN or caching plugin, clear the cache and rescan.
Does it appear on other pages? One issue can occur on several pages, like an element in your navigation. Rescan every affected page, or the whole website.
Does it need manual review? Potential issues marked Needs manual review don't resolve on their own after a rescan. Check it, then mark it as resolved or ignore it. See How to manage checks and issues.
My score didn't change after I rescanned a page
Your score only updates after a full website scan. When you rescan one page or one issue, your score shows a simulated value, and the latest bar in your score history is dashed and marked Pending audit.
To get an accurate score, click Rescan website on the Overview or Accessibility page.
My scans aren't running automatically
Your scan schedule is set to Never. You'll see No scan scheduled on your Overview page.
To turn on scheduled scans:
Go to Monitor → Overview.
Click Change scheduling.
Choose Monthly, Weekly or Daily.
Weekly is available on Team and Enterprise plans, and Daily on Enterprise plans.
You can also change this under Scheduling in Project → Settings → Monitor.
Why is my website score lower than my page scores?
This is expected. Your website score isn't an average of your page scores. A problem repeated across many pages counts more site-wide than on any single page, so your website score can be lower than all of them. How Marker.io calculates your accessibility score explains how this works.
Can I export or share an accessibility report?
Not from Marker.io yet. In the meantime, all your current and historical monitoring data is available through the Marker.io MCP server, and you can use it to create reports with your own branding. See Create reports with the Marker.io MCP server.
Can I scan my staging website?
Yes. Each project monitors one domain, so create a separate project for your staging website.
The same goes for subdomains. A subdomain like staging.example.com counts as a separate domain. If your project already monitors your production domain, create a new project, add the subdomain and choose its pages.
You can't edit the domain on an existing project. To switch a project to a different domain, remove the current domain and add the new one. See Configure your monitoring settings.
Staging websites are often password-protected. If yours is, add the username and password under Auth prompt in Site access. See Scanner errors for details.
The screenshot doesn't show the problem
Screenshots are taken remotely by the scanner, so they aren't always perfect. Use the element's Selector and HTML in the issue panel to find it on your page.
To help us improve, click Report screenshot at the top of the issue panel.
Need Help?
If you have any questions, comments, or corrections, chat with us at the bottom right of our web pages.