Akamai

Finseo gives you a dedicated HTTPS ingest endpoint and credentials for your project. You create a DataStream 2 stream in Akamai Control Center for the properties you want to monitor, choose the JSON log format, include the request, user-agent, and geo dataset fields, and point the stream at the Custom HTTPS destination Finseo provides. Akamai delivers log batches as often as every 30 seconds. Finseo filters each batch down to requests from known AI and search crawlers, such as GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended, Googlebot, and Bingbot, verifies them, deduplicates them, and shows crawled pages, crawl frequency, status codes, and response sizes per crawler in Bot Traffic.

1. 01

   AI crawler coverage across enterprise properties

   Large sites on Akamai often span dozens of hostnames. One DataStream 2 stream covers all selected properties, so you see whether GPTBot and ClaudeBot reach every product line, country site, and documentation portal.

2. 02

   Find blocked or absent crawlers

   If PerplexityBot or Google-Extended never appears in the feed, an Akamai bot manager rule, a robots.txt directive, or a WAF policy is likely blocking it. Unblock before investing in content for that engine.

3. 03

   Tie crawls to AI citations

   Compare the pages OAI-SearchBot and Claude-SearchBot fetch with the sources ChatGPT and Claude cite for your tracked prompts. Crawled but uncited pages are the first candidates for a Finseo visibility task.

4. 04

   Monitor status codes at the edge

   Every DataStream 2 record carries the edge response status. Bot Traffic breaks down 2xx, 3xx, 4xx, and 5xx by crawler, so redirect chains and cache errors that stop Gemini or Microsoft Copilot from reading a page surface immediately.

5. 05

   Replace manual log exports

   Instead of pulling Akamai logs into a SIEM and exporting them for upload, the stream runs continuously. Historical .log uploads and the live feed share one project and are deduplicated automatically.

Enterprises choose Akamai for delivery and security at global scale, but that same edge is where AI crawler behavior is visible and nowhere else. GPTBot, ClaudeBot, and PerplexityBot never run JavaScript, so tag-based analytics tools show zero AI crawler activity even on sites that ChatGPT and Perplexity cite daily. DataStream 2 already streams edge logs for observability; sending the same stream to Finseo adds Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO) insight without new infrastructure. You learn which pages AI engines actually read, which crawlers are missing, and whether your AI visibility work is being picked up.

1. 01

   Get your Finseo endpoint and credentials

   In Finseo, open Bot Traffic, Sync, and click Connect on the Akamai card. Choose whether you want to authenticate with a custom Authorization header or with Basic auth. The dialog shows the endpoint URL and the matching credentials.

2. 02

   Create a DataStream 2 stream

   In Akamai Control Center, go to Common Services, DataStream, and create a new stream. Select the properties whose traffic you want Finseo to analyze.

3. 03

   Choose the JSON log format and fields

   Set the log format to JSON and include the request, user-agent, and geo dataset fields. The User-Agent is required, otherwise Finseo cannot tell GPTBot from a normal browser.

4. 04

   Set the Custom HTTPS destination

   Select Custom HTTPS as the destination, paste the endpoint URL from Finseo, and add the Authorization header value, or enter the provided username and password for Basic auth.

5. 05

   Validate, save, and activate

   Run the Akamai destination validation, save the stream, and activate it on your properties. The Finseo card switches from Awaiting first push to Connected when the first bot visit arrives.

How does Finseo connect to Akamai?

Through Akamai DataStream 2. You create a stream in Akamai Control Center with the JSON log format and a Custom HTTPS destination pointing at your Finseo ingest endpoint. Akamai pushes log batches as often as every 30 seconds, and Finseo keeps only the AI and search crawler requests.

Through Akamai DataStream 2. You create a stream in Akamai Control Center with the JSON log format and a Custom HTTPS destination pointing at your Finseo ingest endpoint. Akamai pushes log batches as often as every 30 seconds, and Finseo keeps only the AI and search crawler requests.

Which authentication does the Akamai integration use?

You choose in the Finseo connect dialog: either a custom Authorization header that you add to the DataStream 2 destination, or Akamai built-in Basic auth with the username and password Finseo generates. Both are project-bound credentials you can invalidate at any time by disconnecting.

You choose in the Finseo connect dialog: either a custom Authorization header that you add to the DataStream 2 destination, or Akamai built-in Basic auth with the username and password Finseo generates. Both are project-bound credentials you can invalidate at any time by disconnecting.

Which dataset fields must the stream include?

Choose the JSON log format and include the request, user-agent, and geo dataset fields. The User-Agent is mandatory for bot classification. Request fields power the crawled pages, status code, and response size views; geo fields add country, city, and region per crawler visit.

Choose the JSON log format and include the request, user-agent, and geo dataset fields. The User-Agent is mandatory for bot classification. Request fields power the crawled pages, status code, and response size views; geo fields add country, city, and region per crawler visit.

Does Finseo store all my Akamai traffic?

No. Finseo processes each batch, keeps only requests from verified AI and search crawlers such as GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and Bingbot, and discards everything else. Regular visitor requests are never stored. You can also filter the stream on the Akamai side to reduce payload size.

No. Finseo processes each batch, keeps only requests from verified AI and search crawlers such as GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and Bingbot, and discards everything else. Regular visitor requests are never stored. You can also filter the stream on the Akamai side to reduce payload size.

Which crawlers does Finseo detect from Akamai logs?

The same list as every Finseo push integration: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-Web, Claude-SearchBot, anthropic-ai, PerplexityBot, Perplexity-User, Google-Extended, GoogleOther, Googlebot, Bingbot, CCBot, Bytespider, Amazonbot, Applebot, meta-externalagent, FacebookBot, DuckAssistBot, cohere, MistralAI, YandexBot, and DuckDuckBot. Finseo additionally verifies each request against the crawler operator's published IP ranges before storing it.

The same list as every Finseo push integration: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-Web, Claude-SearchBot, anthropic-ai, PerplexityBot, Perplexity-User, Google-Extended, GoogleOther, Googlebot, Bingbot, CCBot, Bytespider, Amazonbot, Applebot, meta-externalagent, FacebookBot, DuckAssistBot, cohere, MistralAI, YandexBot, and DuckDuckBot. Finseo additionally verifies each request against the crawler operator's published IP ranges before storing it.

How fresh is the data in Bot Traffic?

Akamai DataStream 2 delivers log batches as often as every 30 seconds, depending on the upload interval you configure in the stream. Finseo processes each batch on arrival, so a crawler visit typically shows in the Bot Traffic dashboard within about a minute.

Akamai DataStream 2 delivers log batches as often as every 30 seconds, depending on the upload interval you configure in the stream. Finseo processes each batch on arrival, so a crawler visit typically shows in the Bot Traffic dashboard within about a minute.

Can I combine the Akamai stream with manual log uploads?

Yes. Uploaded .log and .txt files and the DataStream 2 feed share the same Bot Traffic project. Finseo deduplicates visits by bot, timestamp, IP, and page path, so importing historical logs next to the live stream never double-counts a request.

Yes. Uploaded .log and .txt files and the DataStream 2 feed share the same Bot Traffic project. Finseo deduplicates visits by bot, timestamp, IP, and page path, so importing historical logs next to the live stream never double-counts a request.

How do I stop the Akamai integration?

Click Manage, then Disconnect on the Akamai card in Finseo. This invalidates the credentials so further deliveries are rejected. Then deactivate or delete the DataStream 2 stream in Akamai Control Center, or remove the Custom HTTPS destination, so Akamai stops pushing batches.

Click Manage, then Disconnect on the Akamai card in Finseo. This invalidates the credentials so further deliveries are rejected. Then deactivate or delete the DataStream 2 stream in Akamai Control Center, or remove the Custom HTTPS destination, so Akamai stops pushing batches.