Can the scanner test a signed-in account?

No. CookieScript says its scanner does not enter logged-in pages or submit forms. Cookies found only in those sessions have to be added to the report manually.

What happens when I exclude a URL?

The automated scan skips that absolute URL. If it points to a subdomain, cookies from the excluded subdomain will not be included in the Cookie Declaration.

Is CookieScript's robots.txt behavior documented?

No clear statement appears in the operator's scanner help material. The catalog has a token, but the official articles reviewed here do not confirm a user-agent value or robots compliance.

Is CookieScript an AI crawler?

No AI collection use is documented. It visits pages to assemble a customer's cookie report rather than to create a search index or training dataset.

CookieScript: What It Is & How to Handle It

What is CookieScript?

CookieScript customers use Cookie Scanner to find cookies on the domain connected to a consent banner. A scan can be started from the account or scheduled to run monthly, and the finished report supplies the cookie information the customer reviews and maintains.

Discovery starts on the main page. Cookie Scanner saves the links found there, scans that first level, and repeats the same work at each deeper level. It stops after finding no new URLs or reaching the page allowance on the subscription. Account settings can include unlinked absolute URLs, omit selected destinations, and choose whether subdomains are scanned.

The crawler does not carry out interactive flows. It will not add a product to a basket, submit a form, or sign in, so cookies created only by those actions require manual entry. CookieScript also offers a fixed-source option for sites that block the normal scan; its help center currently gives 80.240.129.194 for that mode.

The collected data belongs to a cookie compliance report. CookieScript does not describe this bot as a source for AI answers or training corpora. Denying it may leave cookies out of the declaration, but it has no documented effect on citations, rankings in AI search, or model access.

Not relevant for AI search

Is CookieScript relevant for AI search?

No. CookieScript is not part of AI search or training, so allowing or blocking it does not change your AI visibility.

CookieScript runs synthetic monitoring or uptime checks on a schedule. It is not collecting content for any index or model, so it has no bearing on search rankings or AI answers. You usually see it because your own team or a service you use set up a check.

How to handle CookieScript

Use CookieScript's own scan settings for routine scope changes. Excluded URLs must be absolute, and excluded subdomains will not contribute cookies to the declaration. If an authorized scan stops after the first page, confirm the current fixed address in the help center before allowlisting it in a firewall.

The facts record supplies a stable token for this preference:

User-agent: CookieScript
Disallow: /

Robots compliance is unknown. CookieScript's public help articles describe URL exclusions and the fixed IP option, but they do not document a scanner user agent or say that robots.txt is read. Disable the scan, change its scope in CookieScript, or enforce a block at the server when a predictable result is required.

Examples

A product launch page is not linked from the main site. The privacy manager adds its full HTTPS URL to the scan so cookies on that page appear in the next report.
Cookie Scanner reports only the home page after a firewall change. An administrator enables the fixed-source setting, checks CookieScript's current help article, and permits the documented address before scanning again.

Frequently asked questions about CookieScript

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

It works through discovered links one level at a time. The scan ends when a completed level yields no new URLs or the account reaches its subscription page limit.