{"id":5735,"date":"2026-06-26T02:21:36","date_gmt":"2026-06-26T09:21:36","guid":{"rendered":"https:\/\/clone.surecookie.com\/docs\/connecting-your-site-to-surecookie-scanner-setup\/"},"modified":"2026-07-09T20:38:15","modified_gmt":"2026-07-10T03:38:15","slug":"connecting-your-site-to-surecookie","status":"publish","type":"docs","link":"https:\/\/clone.surecookie.com\/de\/docs\/connecting-your-site-to-surecookie\/","title":{"rendered":"Connecting Your Site to SureCookie (Scanner Setup)"},"content":{"rendered":"
SureCookie’s cookie scanner runs on our servers and loads your site in a real browser to find the cookies in use. Before your first scan, you connect your site to that service once. Connecting verifies that you control the domain and links your site to the scanner, which also powers automatic categorization and compliance suggestions.<\/p>\n\n\n\n
You only do this once per site. After connecting, you can scan anytime, and your consent banner, script blocking, and consent logging work whether or not a scan has run.<\/p>\n\n\n\n
Before You Begin<\/h2>\n\n\n\n
Connecting happens over the public internet, so a few things need to be in place:<\/p>\n\n\n\n
\n
A publicly reachable site<\/strong> \u2013 Connecting won’t work on localhost, a private network, or a development domain such as .local<\/code> or .test<\/code>, or while the site is behind HTTP basic auth, maintenance mode, or a coming-soon page.<\/li>\n\n\n\n
HTTPS with a valid SSL certificate<\/strong> \u2013 Verification fails on a self-signed or expired certificate.<\/li>\n\n\n\n
A reachable REST API<\/strong> \u2013 SureCookie verifies your site through a request to \/wp-json\/surecookie\/v1\/<\/code> on your domain. If a firewall blocks that path, connecting can’t complete.<\/li>\n<\/ul>\n\n\n\n
Connect During Onboarding<\/h2>\n\n\n\n
The setup wizard opens automatically the first time you open SureCookie after activating the plugin. Connecting is one of its steps.<\/p>\n\n\n\n
\n
On the welcome screen, start the setup.<\/li>\n\n\n\n
On Connect Your Account<\/strong>, click Connect<\/strong>.<\/li>\n\n\n\n
Wait for the Connected to SureCookie<\/strong> confirmation, then continue to the scan step.<\/li>\n<\/ol>\n\n\n\n<\/figure>\n\n\n\n
Connect From the Cookie Manager<\/h2>\n\n\n\n
If you skipped the wizard, you can connect from the scanner instead.<\/p>\n\n\n\n
\n
Go to SureCookie \u2192 Cookie Manager<\/strong>.<\/li>\n\n\n\n
On the Connect to scan your website<\/strong> screen, click Let’s Get Started<\/strong>.<\/li>\n\n\n\n
Wait for the Connected successfully!<\/strong> confirmation.<\/li>\n<\/ol>\n\n\n\n<\/figure>\n\n\n\n
\n
Note:<\/strong> Until your site is connected, scanning is unavailable and SureCookie shows an Account not connected<\/strong> prompt.<\/p>\n<\/blockquote>\n\n\n\n
What SureCookie Sends When You Connect<\/h2>\n\n\n\n
Connecting is a lightweight handshake, not a data transfer. SureCookie sends only:<\/p>\n\n\n\n
\n
Your site URL<\/li>\n\n\n\n
The WordPress administrator email<\/li>\n\n\n\n
The SureCookie plugin version<\/li>\n<\/ul>\n\n\n\n
No page content and no visitor data are sent. As part of the check, SureCookie requests a one-time verification token from your site to confirm you control the domain. Once verified, a private credential is stored on your site and used to sign future scan requests.<\/p>\n\n\n\n
Run Your First Scan<\/h2>\n\n\n\n
With your site connected, you’re ready to scan.<\/p>\n\n\n\n
\n
Go to SureCookie \u2192 Cookie Manager \u2192 Manual<\/strong>.<\/li>\n\n\n\n
Under Select Pages<\/strong>, choose the pages to scan.<\/li>\n\n\n\n
Click Start Scan<\/strong>.<\/li>\n<\/ol>\n\n\n\n
The detected cookies appear on the All Cookies<\/strong> tab, sorted into the Essential<\/strong>, Functional<\/strong>, Analytics<\/strong>, and Marketing<\/strong> categories.<\/p>\n\n\n\n
Troubleshooting<\/h2>\n\n\n\n
\n
The Connect button fails or you see “Account not connected”<\/strong> \u2013 SureCookie couldn’t reach your site to verify it. Confirm your site is public, served over HTTPS, and not in maintenance mode, then try again.<\/li>\n\n\n\n
You see an HTTP 422 or registration error<\/strong> \u2013 Verification was blocked, often by a security plugin or firewall. See Fix a Stuck or Failed Cookie Scan<\/em>.<\/li>\n\n\n\n
You moved your site to a new domain<\/strong> \u2013 Connecting is tied to your domain. After a move, reconnect so SureCookie can re-verify and issue fresh credentials.<\/li>\n<\/ul>\n\n\n\n
![\"Connect](\"https:\/\/clone.surecookie.com\/wp-content\/uploads\/2026\/06\/connecting-your-site-onboarding-connect-1024x640.png\" "\\"Connecting")
<\/figure>\n\n\n\n![\"Cookie](\"https:\/\/clone.surecookie.com\/wp-content\/uploads\/2026\/06\/connecting-your-site-connect-to-scan-1024x640.png\" "\\"Connecting")
<\/figure>\n\n\n\n