Integrations

The Integrations screen connects Google Analytics, Google Tag Manager, Google Search Console verification, Bing Webmaster Tools verification, and IndexNow. Paste the identifier from the service and save it, and it takes effect at once, with no code change or deployment.

Analytics and Tag Manager load only on the public site. To see what Google Analytics counts without leaving the dashboard, connect it on Analytics once its Measurement ID is saved here. The two verification tools each add one meta tag so Google or Bing can confirm that you control the site; neither adds tracking by itself. IndexNow puts nothing on a page at all: it runs from our servers when you publish.

Both search engines offer other ways to prove it, such as uploading a file or adding a DNS record. Pick the HTML meta tag option, which is the one you can finish here: copy the whole tag they show you, paste it into the field, and the token inside it is what gets saved.

Tell search engines when you publish

IndexNow tells Bing, Yandex, Seznam and Naver the moment you publish, rather than leaving them to come back and look. There is no account to open.

Connect it with the key box empty and a key is generated for you. Your site then serves that key at an address of its own, which is how those search engines check a submission really came from you, and the card links to the file so you can see it answering. Paste a key of your own only if you already use IndexNow somewhere else, because saving a different one retires the old key at once.

A publish goes out within five minutes. The card says when the last submission went and what happens next, and if one is refused or the service cannot be reached it says that too, with when it will try again, rather than telling you once in a message you have clicked past.

Nothing is submitted while Keep this site out of search engines is ticked on Site, and the card says so while that is the case.

Cookies, per tool

Every card says what its tool does with cookies, before and after you connect it. Every connected tool that waits for an answer also lets you change it.

Asks the visitor first is the default. Nothing that tool sets is loaded until somebody accepts the banner, and it is never loaded for somebody who says no. Needed to run the site loads it for every visitor without asking.

That second one is a claim rather than a preference, so the card keeps saying what it does while it is in effect, and your cookie banner names the tool to visitors as one you said is needed. Google Tag Manager is the honest case: a container carries whatever you put in it, and only you know whether that is something a visitor has to agree to. Google Analytics is the one to think twice about, because its cookie recognises a visitor between visits whatever you call it here, and where your visitors have to be asked it needs their consent.

If you meant it about the whole site rather than one tool, the cookie banner setting below says that in one place.

The verification tools and IndexNow have no such choice: they set no cookie, so there is nothing to decide.

Cookie banner

Analytics and Tag Manager may set cookies, and this card decides when your site asks about them. There are three choices.

When a connected tool needs it is the default and what nearly every site wants. The banner appears when a connected tool sets cookies and the visitor is somewhere that requires asking: the EEA, the UK, and Switzerland today. A visitor whose country we cannot tell is asked as well. Everyone else gets the tags without a banner. So if you connect Analytics, open your own site from outside those countries, and see no banner, that is the setting working rather than something broken.

Always shows it on every page whatever is connected here. Use it when your own pages embed something that sets cookies of its own, such as a video player or a map.

Never loads the connected tools for everybody without asking. Whether that is allowed for your business and visitors is your responsibility.

If you have marked every tool that sets cookies as needed to run the site, nobody sees a banner at all, and this card says so.

Disconnecting a tool removes its tag from the public site. It does not delete data already held by that service.

Make the banner your own

The default banner already uses your site’s colours and type. If you want a different look, ask your coding agent to add a .vz-consent rule to the site’s stylesheet.

Your site can also carry a banner of its own: a form marked consent with an accept and a reject button, shown while the visitor has not answered. Without one, the default banner asks.

Either way Vizitka decides who is asked, and the tags stay gated on the visitor’s answer, so a banner of your own cannot accidentally load something somebody refused.