SiteLint documentation and guidelines

How to check if SiteLint is working

Content Security Policy

Is your site protected by the Content Security Policy (CSP)? If it is, you must add auditor.sitelint.com to the script-src directive and platform.sitelint.com to the connect-src directive.

The standard SiteLint code snippet is an inline script that injects the SiteLint auditor, so your policy must also allow the inline snippet to execute – via 'unsafe-inline', a nonce ('nonce-…'), or a hash ('sha256-…') in script-src. If you installed the snippet as a separate script file, only the auditor domain is required.

Apache example:

Header add Content-Security-Policy "script-src 'unsafe-inline' https://auditor.sitelint.com; connect-src 'self' https://platform.sitelint.com;" 

Nginx example:

add_header Content-Security-Policy "script-src 'unsafe-inline' https://auditor.sitelint.com; connect-src 'self' https://platform.sitelint.com;" always; 

What the snippet recheck reports

When you use Recheck for snippet in the SiteLint platform, SiteLint reads your site’s CSP from both the HTTP response header and the <meta http-equiv="Content-Security-Policy"> tag, then reports the first problem found, in this order:

  1. Auditor script blocked: script-src (or default-src) does not allow https://auditor.sitelint.com, or does not permit execution of the inline SiteLint snippet. Nothing else can work until this is fixed, so it is always reported first — even if your connect-src is also misconfigured.
  2. Report sending blocked: the script loads and runs, but connect-src (or default-src) does not allow https://platform.sitelint.com, so audit results never reach SiteLint. Symptoms: the snippet is installed correctly, the browser console shows “Connecting to ‘https://platform.sitelint.com/…’ violates the following Content Security Policy directive”, but no data appears in your reports.

If both directives allow SiteLint, the recheck confirms the snippet as valid.

Google Tag Manager

The SiteLint code snippet may not work when loaded by Google Tag Manager. A common reason is that Google Tag Manager is blocked by ad blockers.

Script tags type attribute hash prepended

If the SiteLint code snippet has the type attribute prepended with a hash, like <script type="ea80e272b0a1989fb2f3aa4e-text/javascript">...</script> and you’re using Cloudflare services, then the root cause is the Cloudflare Rocket Loader.

You can:

See article: Resolving the script tag type attribute hash prepending issue with Cloudflare.