After installing the Kukie.io script on your website, use the built-in verification tool to confirm everything is working. The verifier checks that your site loads the correct script and site key, giving you immediate confidence that your cookie banner is active.

WordPress users: If you installed via the WordPress plugin, verification is automatic. The plugin settings page shows your connection status and banner state.

Using the Verify Button

Open your site in the Kukie.io dashboard and go to the Overview tab. You will see a Verify Installation button. Click it and wait a few seconds while Kukie.io fetches your site's HTML and checks for the banner script.

If verification succeeds, a green "Verified" badge appears next to your site name. The verification timestamp is stored so you can always see when the last check was performed.

What the Verifier Checks

The verification tool performs two checks:

1. Script presence - it looks for a <script> tag whose src attribute points to the Kukie.io c.js file.
2. Site key match - it confirms that the data-site-key attribute in the script tag matches the site key assigned to your site in the dashboard.

Both checks must pass for the site to be marked as verified.

Verification Statuses

• Verified (green) - the script and site key were found. Your banner is installed correctly.
• Not verified (grey) - verification has not been attempted yet, or the previous check failed.

You can re-run verification at any time. This is useful after making changes to your site's template or moving to a new CMS.

Debug Mode

For more detailed diagnostics, add ?kukie_debug=1 to any page URL on your website and open your browser's developer console. The banner script will output debugging information including:

• The registered domain and the current hostname, along with whether they match.
• The consent model determined for the visitor's region.
• Translation and language detection details.

This is particularly helpful if the banner loads on some pages but not others, or if you are testing from a staging environment with a different hostname.

Troubleshooting

Script not found

The verifier could not find the c.js script tag in your site's HTML. Possible causes:

• The script was added to the wrong template or only to specific pages instead of the global layout.
• A caching plugin or CDN is serving a stale version of the page without the script.
• The script tag has a typo in the URL.

Site key mismatch

The script was found but the data-site-key value does not match. This usually happens when you copy the embed code from one site and paste it into another without updating the key. Copy the correct embed code from the site's overview page.

Timeout or connection error

The verifier could not reach your website. Make sure your site is publicly accessible and not behind HTTP authentication or a firewall that blocks server-side requests.

Tip: If you use Cloudflare or another WAF, ensure it is not blocking requests from the Kukie.io verification server. The request comes from a standard server-side HTTP client.

Verification Indicator on the Sites List

On the Sites index page, each site shows a small indicator next to its domain: a green checkmark if verified, or a grey dot if not yet verified. This gives you a quick overview across all of your sites.