Vizzybl LogoVizzybl LogoVizzybl

Allow Vizzybl to Index Your Site

Allow the Vizzybl crawler through your robots.txt, firewall, or WAF so site indexing returns pages, not zero.

Allow Vizzybl to index your site

Vizzybl crawls your website to build the content index behind brand defense and content optimization. When our crawler can't read your pages, indexing returns 0 pages and a "needs attention" warning appears in Brand Protection → Content Index. This is Vizzybl's own crawler — not the Google or Vertex AI bot — so allow it explicitly using the details below.

How to tell if Vizzybl is blocked

Open Brand Protection → Content Index. A domain that couldn't be indexed shows one of two states:

  • Blocked — we reached your site but requests were refused. The site is likely blocking our crawler at the firewall or WAF.
  • No readable content — we reached your pages but found nothing to index. This is usually thin content, a JavaScript-only page, or a robots rule that hides your real URLs.

Note: A 0-page result is not always a block. An over-broad rule in your robots.txt can hide almost every URL from every crawler — check that section below before assuming a firewall problem.

Vizzybl crawls from a single, stable egress IP. Allowlisting that IP in your firewall or WAF is the most reliable option, because our crawler falls back to a standard browser User-Agent for compatibility — so User-Agent matching alone may not catch every request.

Add this IP to your allowlist:

35.202.121.22

Important: Allowlist by IP as your primary rule, and add the User-Agent rule below as a second signal.

Allow the VizzyblBot User-Agent

Our crawler identifies itself on its first request to each page as:

Mozilla/5.0 (compatible; VizzyblBot/1.0; +https://vizzybl.ai/bot)

Allow it in two places:

  • robots.txt — add an explicit group for our crawler:
User-agent: VizzyblBot
Allow: /
  • WAF / firewall — add an allow (or skip-bot-check) rule that matches the User-Agent VizzyblBot. Managed bot-fighting rules often challenge unfamiliar crawlers, so name us explicitly.

Note: User-Agent allowlisting is best-effort — if a site blocks VizzyblBot, our crawler retries as a browser so indexing still works where it can. The IP rule above is the deterministic one.

Check your robots.txt

Vizzybl honors robots.txt on every request, whatever User-Agent we send. An over-broad rule silently removes your content from indexing.

Warning: A rule like Disallow: /*? blocks every URL that contains a query string. If your pages live on query-parameter URLs — common on booking, search, and catalog sites — this hides them from all crawlers. Add an Allow: for the paths Vizzybl should read, or scope the Disallow more narrowly.

When both a wildcard group (User-agent: *) and a User-agent: VizzyblBot group are present, the VizzyblBot group takes precedence for us — so a specific Allow: / for VizzyblBot overrides a broad wildcard Disallow.

Verify it worked

  1. Go to Brand Protection → Content Index and click Index Site to re-run.
  2. A healthy run reports the number of pages indexed — not 0.
  3. In your server or WAF logs, confirm requests from VizzyblBot (and our egress IP) return 200.
PreviousCloudflare Setup
NextBilling & Credits