Fix what the Overview shows

Written for Cookie Rocks 2.11.0, checked on 6 November 2026. The current version is 2.11.2: some details may have changed.

This guide is for site owners who opened the Overview page and see points to fix. It explains the most common ones: what each means, what to do, and which button to click.

You need: Cookie Rocks Audit (free). The points that only Cookie Rocks Pro shows are in the grey box at the end.

How to work through the list

1. Open Cookie Rocks, then Overview. The title says how many points are left, for example “3 points to fix”. They are listed under To fix.
2. Start with the first point. Serious points come first, with a red Alert label. The others have a yellow To fix label. Read the point, then click its button: it opens the page where you fix it. The first button is the main (blue) one.
3. Many points come from the scan. Once you have changed something, open Cookies and click Scan my pages again.
4. Come back to the Overview. A fixed point is gone. When none is left, the page says “Nothing to fix among what Cookie Rocks can check.”

The most common points

The points call your banner “your current cookie plugin” or “your cookie banner”. They also name your tools or your countries: below, these parts are left out (…). Only the start of each point is quoted.

The point says	What it means	What to do
“Tell Cookie Rocks where the site owner is based and who your visitors are”	Cookie Rocks does not know which laws apply to your site.	Click Answer four questions, answer, then click Show what the law asks of my site.
“Your site has not been analysed yet”	Cookie Rocks does not know your cookies or your banner yet.	Click Analyse the site, then Scan my pages.
“Your last analysis is … days old”	Cookies not seen for 30 days drop out of your list and of your cookie policy. The point shows after 25 days.	Click Analyse the site, then Scan my pages.
“No cookie banner was found on your home page during the last scan”	Visitors are asked nothing. This point is a red Alert.	Install a cookie banner, or Cookie Rocks Pro. Then click Analyse the site and scan again.
“Your current cookie plugin is active, but its banner was not found on your home page”	Your cookie plugin is on, but visitors probably see no banner.	Turn its banner on, clear the page cache, then click Analyse the site.
“Your current cookie plugin is installed, but its banner is not set up yet”	Visitors see no banner.	Finish the setup of your cookie plugin, then scan again.
“… loads before the visitor chooses” (with the names of your tools first, for example “YouTube loads…”)	Your banner lets a tool through. Its provider receives the visitor’s address.	Click See the details. Turn on the blocking in your cookie plugin, then scan again.
“The automatic blocking of your current cookie plugin is off”	The scan saw trackers load before the visitor chooses.	Turn on the automatic blocking in your cookie plugin, then scan again.
“Cookies set before the visitor consents, by …”	Cookies are set before any choice.	Click See the details, then check how these tools are added to your site.
“Your home page loads Google Fonts from Google’s servers …”	Each visit sends the visitor’s IP address to Google before any consent. Cookie Rocks never holds a font back, so that your layout does not break.	Serve the fonts from your site. The point names the setting that does it in your theme or plugin when Cookie Rocks knows it (Elementor, WP Rocket, Spectra, Kadence, Astra, OceanWP, Neve and others), or a plugin such as OMGF. With Cookie Rocks Pro, Serve Google Fonts from this site on the Consent page does it for you, and is on by default. Then click Check again.
“A third-party script loads without waiting for consent, and Cookie Rocks does not know it”	A script from another site is not in the list Cookie Rocks knows.	Click Check them. For each one, click Send to Cookie Rocks if it follows visitors, or Not a tracker.
“Your cookie banner shows no “Reject” button next to “Accept””, or “The banner of your current cookie plugin has no “Reject” button on its first layer”	Refusing takes more clicks than accepting. European authorities ask for refusing to be as easy as accepting.	Add a “Reject” button in your cookie plugin, with the same look as “Accept”. See the laws, when shown, gives the rule.
“Your current cookie plugin keeps the visitor’s choice for … days”	Your banner asks again too late, or too early, for your countries.	Change the duration in your cookie plugin. See the laws shows the rule.
“Google receives no consent signal”	Google tags do not learn the visitor’s choice.	Turn on Consent Mode in your cookie plugin. See Set up Google Consent Mode.
“Your current cookie plugin counts continuing to browse, scrolling or closing its banner as consent”	European authorities do not accept it: consent must be a clear action, such as a click on “Accept”.	Change this in the settings of your cookie plugin. See the laws shows the rule.
“Google’s own consent message (AdSense, Privacy & messaging) also shows on your site”	Two consent tools ask your visitors. For Google ads, Google’s message decides, not your banner.	Keep one consent tool, or make both say the same thing. In AdSense, Privacy & messaging, turn on “Do not consent” so that Google’s message offers to refuse on its first screen.
“No cookie policy page is known”	Cookie Rocks cannot find your cookie policy.	Click Choose the page. See Get a cookie policy that writes itself.
“No privacy policy page is set”	Your banner needs to link to one.	Click Choose or create the page.
“… points of what the law asks of your site are still to do”	Other duties of your countries are open.	Click See my obligations, and work through the points marked to do.

Every point of the screen: Overview.

Next step: Show a fair cookie banner