> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/gerer-le-consentement-aux-cookies/configuration-du-widget/scannez-les-cookies-deposes-sur-votre-site-web.md).
# Cookies scanning
DASTRA allows you to scan the cookies placed on your website thanks to its **cookie scanning** functionality, directly integrated into its "Cookie consent widget" module.
## Access the "scan cookies" function Dastra
You must first log into your Dastra workspace. To learn how to do this, go to the following page:
{% content-ref url="/pages/-LvaGKB4EL4Jf4xLoJUG" %}
[Broken mention](broken://pages/-LvaGKB4EL4Jf4xLoJUG)
{% endcontent-ref %}
Then, you must go to the "Consent to cookies" module, and click on the "New widget" button.
Icon of the "Cookies" module
Click on the "New widget" button
A new screen appears. You are in the "Cookie Scan" section.
## Scan the cookies placed on your website
Once in the "Scan cookies" section, simply enter the domain name of your website in the space reserved, and click on "Submit".
{% hint style="info" %}
Your domain name must include the entire prefix "https: // [www](http://www)." to be taken into account by our engine. Websites without SSL are not eligible to the scan feature.
{% endhint %}
Wait a few seconds, and that's it, the cookies placed on your website are identified!
Once the cookies placed on your website are scanned, you can proceed to their classification.
{% content-ref url="/pages/-M4FMt69NF5QKuXHqZrN" %}
[Classify cookies by consent categories](/en/features/gerer-le-consentement-aux-cookies/configuration-du-widget/classifiez-les-cookies-par-categories-de-consentement.md)
{% endcontent-ref %}
***
## Limitations and best practices
### Cookies set after consent (opt-in services)
By default, a cookie scanner browses your site without giving consent. Cookies that are only placed after opt-in (analytics, marketing, etc.) are never triggered and therefore cannot be detected.
**Exception: if the Dastra SDK is already integrated on your site**, the scanner is able to bypass the consent banner and collect all cookies actually placed — including those from opt-in services. In that case, the scan produces a complete result without any manual intervention.
If the Dastra SDK is not yet in place on the scanned site, opt-in services will need to be **added manually** via the service library.
### Manually added services — excess cookies
When you add a service from the Dastra library (e.g. Google Analytics, Meta Pixel), Dastra imports the full list of cookies that service *can* place across all its possible configurations. Your implementation likely only uses a subset of those.
It is recommended to **remove cookies that your specific implementation does not actually place**. Declaring cookies you do not use is misleading to visitors and may raise questions during a compliance audit.
To identify which cookies to keep, cross-reference the automated scan results (which detect what is actually placed) with the list imported from the library, and remove entries that do not appear in the scan.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://doc.dastra.eu/en/features/gerer-le-consentement-aux-cookies/configuration-du-widget/scannez-les-cookies-deposes-sur-votre-site-web.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.