Proofsource and Google Cloud CDN: see AI crawlers in your load balancer logs

Create a Cloud Logging sink for your load balancer, route it through Pub/Sub, and Proofsource counts every verified AI crawler visit, page by page. You see which pages the engines read and which they miss, using logs your Google Cloud project already produces.

Connect Google Cloud CDN See it in Proofsource

Live

Visit cloud.google.com ↗

app.proofsource.co/integrations

More crawler sources, Google Cloud

LiveReceiving logs

Load balancer logsCloud Logging sinkPub/Sub topicProofsource

Sinkproofsource-crawler-logs

Topiccrawler-logs

SubscriptionPush, one per brand

KeyWrite access, this brand only

https://api.proofsource.co/v1/crawler-logs/google-cloud?key=YOUR_API_KEY

Sample data

The Google Cloud card with the push URL for the Pub/Sub subscription.

Proofsource and Google Cloud CDN, in short

The facts, ready to quote.

Stage: Live on every plan
Connects with: A Cloud Logging sink to a Pub/Sub topic, then a push subscription to a Proofsource URL
Access it needs: A write-only key limited to one brand, placed in the push URL; no access to your project
Where it shows: Integrations, Crawler sources, More crawler sources, Google Cloud
Bot check: IP ranges plus reverse DNS on every line
Disconnect: Delete the push subscription or the sink in Google Cloud and logs stop at once

Why we love Google Cloud CDN

In the makers' own words, from their own pages. Proofsource builds on it, never around it.

Caching close to your users

Cloud CDN caches content and serves it from Google's edge, answering from cache when it can and sending only misses to your origin.

From docs.cloud.google.com

A CDN built into the load balancer

Cloud CDN works with Google's global load balancing, so one front door handles routing, caching and delivery.

From cloud.google.com

Logs that flow anywhere

Cloud Logging collects logs from across Google Cloud and routes them with sinks to the destination you pick.

From cloud.google.com

How Proofsource uses Google Cloud CDN

Counts verified AI crawler visits from your Google Cloud load balancer logs through Cloud Logging and Pub/Sub.

Connect
Sink the load balancer logs
A Cloud Logging sink sends your load balancer's request logs to a Pub/Sub topic.
Read
Receive and verify
A push subscription delivers each message to Proofsource, where it is matched to an AI crawler and checked against IP ranges and reverse DNS.
Show
See reads per page
Crawler sources and AI traffic list each page, crawler and status code.
Prove
Link reads to answers
After a fix ships, Proofsource shows whether crawlers fetched it and whether the engines name you.

Set up Google Cloud CDN in 4 steps

Open Integrations, Crawler sources
Choose More crawler sources, then Google Cloud, to see the push URL and key.
Create the sink
In Cloud Logging, create a sink for your load balancer's request logs with a Pub/Sub topic as the destination.
Create a key for this brand
Create a Proofsource API key limited to this brand with write access.
Add a push subscription
Point a push subscription on the topic at the URL from the card, replacing YOUR_API_KEY. Pub/Sub cannot send headers, so the key travels in the URL.

app.proofsource.co/integrations

Verified AI visits

Verified AI visits1,087last 7 days

Dropped as fake29

Pages read176

Page	Crawler	Visits
/docs/getting-started	GPTBot	96
/pricing	ClaudeBot	71
/blog/meeting-notes-guide	PerplexityBot	58

Sample data

Visits counted from Pub/Sub deliveries after the bot check.

What you unlock with Google Cloud CDN

Verified crawler counts

Real AI visits only, from logs you already produce.

Per-page reads

See which pages each engine reached.

Brand-limited key

The key can only send logs for one brand.

Block check

Find rules that stop AI crawlers reaching pages.

AI traffic

Crawler visits beside AI referral clicks.

Fix pickup

Confirm crawlers returned after each fix.

Google AI Overviews

Google AI Mode

Questions about Proofsource and Google Cloud CDN

What does Proofsource receive from Google Cloud?

The request log messages your sink sends through Pub/Sub. Proofsource keeps AI crawler visits and drops the rest. It has no access to your project, your buckets or your settings.

Why is the key in the URL?

Pub/Sub push subscriptions cannot send custom headers, so the brand-limited key goes in the push URL. The key can only write logs for one brand and cannot read anything. Replace it any time.

How do I connect Google Cloud CDN?

Open Integrations, Crawler sources, More crawler sources and choose Google Cloud. Create a Cloud Logging sink to Pub/Sub, make a brand key, and add a push subscription with the URL from the card.

How do I disconnect?

Delete the push subscription or the sink in Google Cloud. Logs stop at once. You can also delete the brand key in Proofsource. Past counts stay unless you ask us to remove them.

Can Proofsource change my Google Cloud setup?

No. Everything is pushed out by your own project.

How does this help my AI visibility?

Engines cannot cite pages they cannot fetch. Counts per page show what crawlers reach, so you fix the right pages, and Proofsource then asks the engines again to see whether they name you.

Which AI engines does Proofsource check?

Up to 10 depending on your plan: ChatGPT, Perplexity, Claude, Google AI Overviews, Google AI Mode, Gemini, Microsoft Copilot, Grok, DeepSeek and Meta AI. The free scan and the trial run four.