AI Traffic

Why is Traffic Overview showing no data?

The most common reasons for empty traffic data: a missing integration, a missing tracking key, the selected time period, or a read-only workspace.

Last updated 23 days ago

If Traffic Overview shows a notice instead of analytics, KI Score has stored neither AI crawlers nor AI referrals for this website in the selected period. This article walks you through the most common causes. KI Score does not offer a connection test or a display of the last event it received, so you check the integration on your side.

Which notice do you see?

The notice already tells you where the problem lies:

Notice Meaning
Noch keine Traffic-Daten (no traffic data yet) with the Integration einrichten (set up integration) button No site ID is stored for the website yet.
Noch keine Traffic-Daten eingegangen (no traffic data received yet) with the Integration prüfen (check integration) button The website is set up, but KI Score has never stored an event for it. Until then, the time period can't be changed.
Keine Traffic-Daten im gewählten Zeitraum (no traffic data in the selected period) with the Integration prüfen button Data arrived at some point, but not in the selected period.

Is the integration set up?

Traffic Overview only receives data if your server reports each page request to KI Score. Without this server-side integration, the page stays empty.

  1. Click the button in the notice, or open Einstellungen → Traffic-Tracking (Settings → Traffic tracking) in the sidebar.
  2. Under Verfügbare Integrationen (Available integrations), click the Server API card. The setup guide opens in a window.
  3. Compare your setup with the Dein Tracking-Endpoint (your tracking endpoint) and Universelles cURL-Beispiel (universal cURL example) fields, which KI Score fills in for your website.

If the integration page shows the notice “Verbindungsdaten fehlen” (connection details missing) or “Keine Integrationsdaten verfügbar” (no integration data available), the website is missing its site ID, tracking key, or API endpoint. In that case, contact support at support@kiscore.ai.

Is the tracking key being sent?

Every report must include your website's tracking key in the X-Kiscore-Tracking-Secret header. If the header is missing or the key is wrong, KI Score rejects the request with status code 401, and the events don't appear in Traffic Overview. The cURL example on the integration page already includes the header with your key.

To check your setup:

  1. Send a test request from your server, following the cURL example.
  2. Check the response. For an accepted report, it contains the field status with the value ok.
  3. If you get a 401, check the header name, the tracking key, and the site ID.

Note: The integration page also shows cards for Nuxt, TYPO3, WordPress, and Next.js. The TYPO3 extension sends the key from version 2.0.0 onward, once you enter the site ID and tracking secret in the Site Configuration. According to our most recent check, the published version of the Nuxt module doesn't send the header. If you use the Nuxt module and see no data, that is the most likely cause. In that case, we recommend the Server API as the reliable option.

Time period and first events

Under Zeitraum (time period) at the top, choose a preset such as Letzte 7 Tage, Letzte 14 Tage, or Letzte 30 Tage (last 7, 14, or 30 days), or mark your own range in the calendar. Choose a longer period if the events happened a while ago.

Even a correctly configured integration only shows data once there is something to report:

  • Under KI-Crawler (AI crawlers), a request appears only after the next visit from an AI crawler.
  • Under KI-Verweise (AI referrals), a visit appears only once a real person arrives on your website from an AI source such as ChatGPT or Perplexity.

KI Score doesn't store regular visits. A response with the status ok only means it was accepted, not necessarily that an event will show up in Traffic Overview.

Limits for static sites and high traffic

Pages served entirely from a CDN or static hosting never reach a server that could send a report, so KI Score can't capture requests for them. The same applies to pages that an upstream page cache serves without reaching your server. KI Score does not offer a browser-side JavaScript snippet as an alternative.

KI Score also limits the number of reports: at most 120 requests per minute per sending IP address and 600 per minute per website. Reports beyond that may be lost, so with very heavy traffic the numbers in Traffic Overview may be incomplete.

Read-only workspace

In a read-only workspace, KI Score doesn't store any traffic events, even if your server keeps reporting. KI Score then answers the reports with status code 422 instead of ok. In this state, the dashboard redirects you to the plan selection. After reactivation, only events from that point on appear, and the gap is not backfilled.

What teams say about KI Score

“We finally see week by week where our brand shows up in ChatGPT and Perplexity.”

Lena Vogt, Head of SEO

“The score finally gave us one number the whole team actually understands.”

Tobias Reimann, CMO

“Instead of guessing which prompts matter, we now have real data.”

Franziska Aldag, Head of Content

“Within the first week we already saw which competitor was beating us in AI answers.”

Malte Ohlsen, CEO

“Setup took one afternoon, not weeks of onboarding.”

Insa Brechtel, Head of Marketing

“Finally a tool that takes AI Overviews as seriously as classic SEO.”

Jonas Peiter, SEO Manager

Measured where your customers ask

ChatGPT
Perplexity
Gemini
Claude
Copilot
Grok
AI Overviews
DeepSeek

Ask our experts

Our team is happy to help personally — reach out anytime.