There are two primary reasons why your website scan might fail:

One of the most common issues causing a failed or incomplete cookie scan is an incorrect URL.

Check if your site's URL was typed correctly in your dashboard's Website Information, found under Settings in the left-side menu.

For example, some sites that redirect immediately require that "www" is included with the URL for all cookies to be detected.

If you are still receiving a failed scan message when using the Cookie Consent Manager, it may be because your website disallows scanning either in your robots.txt or through other security mechanisms such as a firewall or blockers put in place by your hosting provider.

If you disallow scanning from certain bots in your robots.txt, you can try removing the entire Disallow: line.

If you wish to only remove it temporarily, you can wait for the cookie scan to finish, then add the Disallow: line back in. However, this could prevent future scans.

If you want to continue to disallow scanning from certain bots, you can specifically allow Termly's bot by adding an Allow condition for the TermlyBot user-agent:

If the scanner continues to fail, it may be blocked by your hosting provider. Whitelist the following IP addresses to allow the scanner to run: 54.188.91.132, 44.241.76.145, 54.149.84.59, 54.71.228.250, 34.217.4.132, 35.80.252.61

Find out more about how to recognize and allow traffic Termly's scanner.