SEOmise

Region and currency

  1. Home
  2. Help centre
  3. Website health and changes
  4. What does ConsentGuard SEO show about my cookie banner?

What does ConsentGuard SEO show about my cookie banner?

Short answerEvery website health scan reads your start page once; ConsentGuard SEO reads the same answer and names the consent tool (cookie banner) it runs, how sure it is and why, what the page says about Google Consent Mode and IAB TCF, and tells you when the tool changes. A check of search and measurement effects, not legal advice.

About ConsentGuard SEO: how your cookie banner affects search engines and measurement. A check, not legal advice

Updated 5 November 2026

Where to find it

Open Website health → Consent & SEO. The scan overview also has a small Consent tool card. Nothing to switch on: it fills in after the next scan of your main website.

What you see

  • Consent tool: the tool found on your start page, such as Cookiebot, Usercentrics, OneTrust, CookieYes, Complianz, iubenda, Osano, Didomi, Termly, Quantcast or InMobi Choice, Shopify's own banner, or a banner of the site's own.
  • Likely or Possible: a tool is called likely only when two different kinds of signal point to it (its script, its banner's markup, its code on the page or its cookie) and the confidence reaches the line staff set (50 % unless changed). One kind alone shows as possible.
  • Signals: what was found, for example the script address or the banner's element.
  • Version: only when the script's address shows it (often a WordPress plugin's version). It is never the IAB TCF version.
  • Google Consent Mode: whether your page sets a default, which of the seven types it names (ad_storage, analytics_storage, ad_user_data, ad_personalization, functionality_storage, personalization_storage, security_storage), whether ads and analytics start as denied, and whether the default comes before the Google tag. Not verified means a Google tag or Tag Manager is there but no default is written in the page: it may be set inside Tag Manager, which the page source does not show.
  • IAB TCF: whether the page has the __tcfapi stub. The framework version and whether the tool answers need a real browser, so they say "not checked yet".
  • History: the tool found on each scan, with any change.

When the tool changes

When a scan finds another tool, a tool where there was none, or none where there was one, the owners and admins of the workspace get a notice and an e-mail, and the project timeline records it. Only changes both scans were sure about count, so a "possible" sighting raises no alarm. Turn the e-mails off with Tell me when the consent tool changes on the screen.

Check it by hand

The screen lists the steps for your platform: open the site in a private window, see the banner, and compare the page before and after you accept (text, menu links, title). After a change to your banner, press Scan again in Website health to check it.

What comes next

The browser checks (the page as a fresh visitor, after reject and after accept, side by side) are in early access: press Ask for early access on the screen.

Good to know

  • Holding back analytics or ads until a visitor agrees is normal and never counts against your SEO.
  • It reads the start page only, from the answer the scan already had. Nothing is installed on your site and nothing is changed.
  • This is a check of search and measurement effects, not legal advice. For privacy questions, use the privacy and cookie scanner.

Still stuck?

Ask Mise, or a person

Mise answers from these help articles in seconds. If the answer is not here, raise a ticket and our support team replies by e-mail.