The Kukie.io scanner visits your website pages with a real browser, detects every cookie and tracker that is set, and automatically categorises the results. Running a scan is the fastest way to build a complete picture of your site's cookie footprint.

How to Trigger a Scan

Open your site in the Kukie.io dashboard and navigate to the Cookies & Scripts tab. Click Run Scan. The scanner is queued immediately and you can monitor progress in real time without leaving the page.

If another scan is already running for a different site in your organisation, your scan is placed in a queue and will start automatically when a slot becomes available.

What the Scanner Detects

The scanner uses a headless Chromium browser to load each page. It collects:

• First-party cookies - set by your own domain via JavaScript or HTTP headers.
• Third-party cookies - set by external services such as Google Analytics, Facebook Pixel, or Hotjar.
• localStorage and sessionStorage - browser storage used by many analytics and advertising tools.
• HttpOnly cookies - cookies that cannot be read by JavaScript, detected via the browser context.

Tip: The scanner automatically simulates consent for 8+ common consent management platforms, so cookies that are normally blocked until consent are still discovered.

Page Discovery

The scanner first looks for a sitemap.xml file on your domain. If found, it extracts page URLs from the sitemap (and follows sitemap index files). If no sitemap is available, it falls back to crawling internal links from your homepage. Your homepage is always included.

The number of pages scanned per run depends on your plan. Free plans scan up to 100 pages, Pro plans up to 600, and Business plans up to 2,000. You can see your plan limit on the Account & Billing page.

Understanding the Results

When the scan completes, the Scan Results tab shows a summary of cookies found, new cookies discovered since the last scan, and an auto-categorisation summary. Each cookie is listed with its name, domain, category, and the pages where it was detected.

Scan Statuses

• Completed - all pages scanned successfully.
• Completed with errors - most pages scanned, but some failed (for example, pages returning 404 or 500 errors). The results from successful pages are still saved.
• Failed - the scan could not complete. Check that your site is accessible and try again.

Auto-Categorisation

After every scan, Kukie.io's auto-categorisation engine classifies cookies into four default categories: Necessary, Analytics, Marketing, and Functional. It uses a four-stage pipeline: exact name matching, regular expression patterns, domain-to-category mappings, and heuristic analysis.

Cookies that the engine cannot confidently categorise are flagged as uncategorised. You will see a notification with the uncategorised cookie names and quick-categorise buttons to assign them manually. See Scanning & Cookies for more on managing cookie categories.

Important: Cookies set only on user interaction (such as a button click or form submission) are not detected by the automated scanner. You may need to add these manually.

Scheduled Scans

On paid plans, you can schedule scans to run automatically on a weekly or monthly basis. This keeps your cookie inventory up to date as your site changes. See Scanning & Cookies for setup instructions.