Frequently Asked Questions (FAQ)

The EEAT Analyzer rates your website against Google's E-E-A-T criteria:

• Experience - Does the website show practical experience?
• Expertise - Is expertise demonstrated?
• Authoritativeness - Is the website an authority in its field?
• Trustworthiness - Is the website trustworthy?

The analysis uses AI to evaluate these factors and provide concrete improvement suggestions.

There are several possible reasons:

• Cloudflare-Schutz: Your website is blocking our crawler. See the "Cloudflare Configuration" section below.
• JavaScript-Rendering: Key content loads only after JavaScript execution.
• IP-Blocking: Your server is blocking certain IP addresses.

Social media links are recognized when they:

• As <a href="..."> links exist in the HTML
• Link to official profile pages (not share buttons)
• Are not dynamically loaded by JavaScript

If your website uses Cloudflare, our crawler may be blocked. Here's how to allow our crawler:

Step 1: Open your Cloudflare Dashboard

1. Log in at dash.cloudflare.com
2. Select your domain
3. Navigate to: Security > WAF > Custom rules

Step 2: Create a new rule

Click "Create rule" and use these settings:

• Rule name: Allow EEAT Analyzer Bot
• Expression:

(http.user_agent contains "Mozilla/5.0") and (http.user_agent contains "Chrome")

Step 3: Define action

• Action: Skip
• Skip options:
  • Super Bot Fight Mode
  • Rate Limiting
  • Browser Integrity Check

Error 429 means Cloudflare's rate limiting blocked the crawler. Solutions:

Option 1: Adjust rate limiting rule

1. Go to Security > WAF > Rate limiting rules
2. Create an exception rule for our User-Agent

Option 2: Adjust Super Bot Fight Mode

1. Go to Security > Bots
2. Under "Super Bot Fight Mode" select "Allow" for "Definitely automated"

The crawler uses two user agents, depending on the step.

Individual page fetches and checks:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36

Page crawl:

Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Googlebot/2.1; +http://www.google.com/bot.html) Chrome/124.0.6367.60 Safari/537.36

Page crawl settings: depth up to 3, up to 8 concurrent requests per domain, 0.5 seconds delay. The maximum number of pages depends on your plan. If a page responds with 403, 429 or 503, the crawler automatically fetches it through a proxy service.

You can test this with the following command:

curl -I https://ihre-website.de

If you see these headers, your website uses Cloudflare:

• Server: cloudflare
• CF-RAY: ...
• CF-Cache-Status: ...

If a Cloudflare-protected website responds with 403, 429 or 503, our EEAT Analyzer automatically tries to fetch the page through a proxy service.

Here you'll find useful external guides for Cloudflare configuration:

Change security level

Guide to changing the security level for your domain:

• How to change security level of Cloudflare domain (ex2.com)

Configure WAF and firewall

Community guides for proper firewall configuration:

• How to properly configure Cloudflare to block attacks (Cloudflare Community)

Troubleshooting

If the security level setting doesn't seem to be active:

• Security Level setting is not active - Troubleshooting (Cloudflare Community)

The page crawl does not evaluate robots.txt. This prevents shop systems such as Shopify from stopping the analysis with 429 errors when the robots.txt is fetched.

Areas that should not be analyzed can be blocked through your server or WAF configuration. If you have questions, write to service@visibly-ai.com.

Analysis duration depends on various factors:

• Website size: More pages = longer analysis
• Server speed: Slow servers delay analysis
• Blocked pages: If we have to fall back to a proxy service, the analysis takes longer
• AI Analysis: AI rating requires additional time

Typical analysis times:

• Small website (10-20 pages): 1-2 minutes
• Medium website (50+ pages): 3-5 minutes
• With proxy fetch for blocked pages: longer

Check the following points:

1. Check your spam folder
2. Verify that you entered the email address correctly
3. Wait a few minutes - larger analyses take longer

Our emails come from: service@visibly-ai.com

Possible causes and solutions:

We take protecting your data very seriously. Sensitive data is protected with state-of-the-art encryption:

• AES-128-CBC encryption: Your revenue and keyword data is encrypted and stored with Fernet (AES-128-CBC)
• Per-user key: Each user has an individual encryption key
• Secure transmission: All data is transmitted via HTTPS
• Google OAuth: We don't store Google passwords - authentication happens via Google OAuth 2.0

The following sensitive data is encrypted and stored:

• Revenue Analysis: All revenue data (total, organic, brand, generic)
• Keyword data: Top keywords by revenue
• Landing Pages: Page performance by revenue
• Google OAuth Tokens: Google APIs credentials

Only necessary metadata (project ID, time period, status) remain unencrypted for database queries.

Our encryption is based on the Fernet standard:

• Algorithm: AES-128-CBC with HMAC-SHA256 for integrity verification
• Key derivation: Your individual key is generated from multiple factors
• Encryption: Data is encrypted before being stored in the database
• Decryption: Data is only decrypted server-side when you retrieve it

Encryption happens automatically, so you don't need to configure anything.

The organic traffic figures in the Online Presence dashboard are monthly estimates from DataForSEO. For potential calculations (for example in the Brand Deep Dive), Visibly AI uses the empirical CTR curve of the Keyword Study 2026. It is based on anonymized Search Console data from 94 domains (CTR = clicks / impressions):

From position 11 the CTR is between 0.40 and 0.49%. For positions 21 to 50 we use 0.3%, beyond that 0.1%. The study measures positions up to 20, anything beyond is extrapolated.

Formula: Estimated traffic = search volume × CTR (position)

Example: Keyword with 8,100 searches at position 3 → 8,100 × 0.0237 = approx. 192 clicks/month

The values come from the Keyword Study 2026 and are measured, not estimated:

• Empirical: The basis is anonymized Search Console data from 94 domains. CTR per position is clicks divided by impressions.
• Realistically low: At position 1 the average across all keywords is 5.59%. Idealized tables with 28% or more do not reflect this.
• SERP features: Featured snippets, ads, AI answers and knowledge panels reduce organic CTR.
• Spread: Actual CTR varies by industry, search intent and device. The curve is an average and serves as a planning value, not as a forecast for a single keyword.

The label "Your Domain" marks your own website in the competitor overview:

• This way you can see at a glance where you stand compared to your competitors
• The row is highlighted in yellow for better visibility
• You can compare the metrics directly with your competitors

The Online Presence Score (0-100) rates a domain's overall online visibility based on 5 components:

Domain Health measures link quality:

• DoFollow share: Share of doFollow domains among all referring domains. 80% doFollow or higher = full score.
• Link diversity: Ratio of referring domains to backlinks. More different domains = healthy profile (no spam links).

The data comes from DataForSEO, a professional SEO data provider:

• Keyword rankings: Current SERP positions for organic keywords
• Search Volume: Monthly search volume based on Google data
• Backlinks: Comprehensive backlink database with Domain Rank
• Competitors: Domains with similar keyword rankings

Data is updated regularly to provide current information.

You can find the current plans with credits, projects and features on the Pricing page.

You can end your contract at any time on the cancellation page: app.visibly-ai.com/kuendigen.

If you have questions, reach us at service@visibly-ai.com.