Help Center / Guides

Guides

Guides, screenshots, and step-by-step articles presented in a structured format that is easy to understand.

FAQs

The most common answers, organized and easy to scan for a faster support experience.

Video Tutorials

Show full visual walkthroughs for setup, scans, policies, and advanced features in one place.

Support

Reach out when you need direct help with setup, troubleshooting, or account-related questions.

Docs

Download deeper implementation notes, developer-facing references, and structured technical material.

How to Review Scan Results

How to Review Scan Results

How to Review Scan Results

This guide explains how to review the cookies detected during a scan and decide what needs attention before you move forward with classification, banner setup, or policy generation in Cookiedad.

Use this process to turn raw scan data into something clear, usable, and ready for action.

When to use this guide

Follow these steps when:

  1. you have completed a new scan
  2. you want to validate the detected cookies
  3. you need to review unknown or uncategorized entries
  4. you want to prepare accurate data for your cookie banner or policy pages

Step 1: Open the scan results

Start by opening the latest scan results inside Cookiedad.

Make sure you are reviewing the correct scan, especially if your site has been scanned more than once or if changes were made recently.

You should always work from the most relevant and up-to-date result set.

Step 2: Check the total number of detected cookies

Look at the overall number of cookies found in the scan.

This gives you a first overview of how large the review will be and helps you spot unusual situations, such as:

  1. an unexpectedly low number of results
  2. a sudden increase in detected cookies
  3. missing cookies you expected to see
  4. too many uncategorized entries

At this stage, do not classify anything yet. First, understand the scope of the results.

Step 3: Review the cookie names one by one

Go through the detected cookie names carefully.

Focus on identifying:

  1. familiar cookies you already know
  2. cookies clearly linked to specific services
  3. repeated entries or very similar names
  4. entries that look custom, incomplete, or unclear

The goal here is to separate what is already obvious from what needs deeper review.

Step 4: Identify the source when possible

For each cookie, try to understand where it is coming from.

A cookie may be linked to:

  1. the WordPress site itself
  2. a plugin
  3. an analytics tool
  4. an embedded video or map
  5. a payment provider
  6. an advertising or tracking platform
  7. a consent or security system

If the source is already obvious, note it mentally or in your workflow. If it is not clear, keep it for further review.

Step 5: Check whether the category makes sense

If the scan already assigned a category, review it instead of accepting it automatically.

Ask whether the category fits the actual purpose of the cookie.

For example:

  1. a login or session cookie may belong to Necessary
  2. a language or user preference cookie may belong to Functional
  3. an analytics cookie may belong to Statistical
  4. an advertising or retargeting cookie may belong to Marketing

Automatic logic can help, but final review should still be based on real purpose.

Step 6: Look for unknown or uncategorized cookies

Pay special attention to cookies that are still marked as unknown, uncategorized, or not fully documented.

These are usually the entries that need manual review before your setup can be considered cleaner and more reliable.

When you find them, check:

  1. the exact cookie name
  2. where it appears
  3. whether it may belong to a known service
  4. whether it only appears on specific pages or after consent

Do not leave these entries ignored if they may affect compliance or classification accuracy.

Step 7: Watch for duplicate or related cookies

Some cookies may appear as part of the same family.

You may find:

  1. the same cookie shown more than once in slightly different forms
  2. cookies with a shared prefix
  3. cookies from the same provider with different purposes
  4. session and persistent versions of similar entries

Review them carefully so you do not treat related cookies as completely separate issues when they are actually part of one system.

Step 8: Compare the results with your website features

Now compare the scan results with the real services active on your site.

Ask yourself:

  1. does the site use analytics tools
  2. are there embedded videos or maps
  3. is there a payment system
  4. are marketing or retargeting tools installed
  5. are there forms, chats, or third-party widgets

A scan result is more useful when it matches what is actually present on the website.

If a cookie appears but no matching service is active on the site, that entry may need extra verification.

Step 9: Check what needs manual confirmation

Some scan results should not be accepted without checking them further.

These usually include:

  1. unknown cookies
  2. cookies with vague descriptions
  3. cookies with unclear providers
  4. categories that do not seem correct
  5. cookies that may be essential on some pages but optional on others

Mark these internally for a second pass so the review stays organized.

Step 10: Prioritize the entries that matter most

Do not treat every cookie with the same urgency.

Start with the entries that are more important for compliance and user consent, such as:

  1. cookies that may load before consent
  2. marketing or analytics cookies
  3. third-party tracking cookies
  4. cookies with no clear category
  5. cookies that will appear in your policy or banner setup

This keeps the review practical and helps you fix the most relevant issues first.

Step 11: Cross-check with a browser test when needed

If something in the scan looks unclear, verify it in a real browser session.

This is useful when you want to confirm:

  1. whether the cookie is actually written in the browser
  2. whether it appears before or after consent
  3. whether it is tied to a specific page or action
  4. whether the scan result reflects real behavior

A scan is useful, but browser validation gives you a more direct view of what happens during an actual visit.

Step 12: Finalize the review before moving on

Once the results have been checked, make sure you have a clear separation between:

  1. cookies already confirmed
  2. cookies that need classification updates
  3. cookies that need web research
  4. cookies that need browser verification
  5. cookies that are ready for policy use

This final step helps you move into the next phase without confusion.

What a good review should achieve

By the end of the review, you should be able to answer these questions clearly:

  1. which cookies are known and correctly categorized
  2. which cookies still need manual investigation
  3. which entries may affect consent behavior
  4. which results are ready to be used in your compliance workflow

If you cannot answer these yet, the scan results still need more review.

Common mistakes

Accepting every result as final

A scan is a strong starting point, but some entries still need human review.

Ignoring unknown cookies

Unclear entries are often the ones that matter most during a proper review.

Reviewing without website context

A cookie only makes sense when matched with the real tools and features active on the site.

Skipping browser verification

Some results are better understood when checked in a live session.

Final result

You have successfully reviewed the scan results and prepared them for the next stage inside Cookiedad.

This process helps you move from raw detection data to a cleaner, more reliable cookie setup that is easier to classify, manage, and document.

Contact Us

First
Last