Site Analytics

Site Analytics shows how your site performs in search and how AI crawlers interact with it. It pulls real data from Google Search Console (impressions, clicks, queries, position) and tracks which AI bots are visiting your site — so you can measure the impact of your visibility work, not just guess at it.

In the app it's Site Analytics in the sidebar.

Connecting Google Search Console

Click Connect Google Search Console on the Site Analytics page and sign in with Google. Pendium requests read access to your Search Console data, lists the properties you have access to, and auto-matches the one for your website or custom domain. Once connected, it pulls your search metrics on a regular cadence.

Connecting is read-only — Pendium never changes anything in your Search Console account.

Verifying your domain in Search Console

This is separate from connecting, and only needed if you serve your site on a custom domain and want Google to recognize that you own it.

In Site → Manage → Hosting, Pendium gives you an HTML-tag verification token to add to your domain. The flow:

1. In Google Search Console, start adding your domain and choose the HTML tag verification method. Copy the content value from the <meta name="google-site-verification" ...> tag it shows you.
2. Paste that token into the Search Console verification field in Site → Manage → Hosting.
3. Pendium publishes the meta tag on your site and round-trips a check to confirm it's live. When it matches, your domain shows verified.

Prerequisites: your custom domain must be connected and verified with Pendium first, and your site must be public. If verification fails, it's usually because the token was mistyped or the domain isn't serving the site yet — re-copy the token and retry.

What you'll see

The page is split into tabs. Each one can be linked to directly, for example ?tab=search.

Pick 7, 30 or 90 days to see each key number next to the period before it, for example the previous 30 days, and how much it changed. Untick Compare with the previous 30 days to hide the comparison. All time has nothing to compare against.

Each table (pages, search queries, AI agents and traffic sources) has an Export CSV button. The file holds every row for the range you picked, not only the rows shown; the AI agents file lists the 50 busiest agents.

• Overview: your key numbers, a headline naming the assistant and page with the most live fetches this week (for example, ChatGPT read your FAQ 13 times while answering people), and a daily chart for each source: visitors from AI answers (Google Analytics), AI agent visits and search clicks. When you compare, the period before shows as a dashed line. Your monthly recap email carries the same line for the last 30 days. Dots under each trend chart mark the days Pendium did something for you: a post or page published, a site change shipped, a visibility scan run. Click a dot to see what happened that day. Use Add note above the Overview charts to mark something you did, like a launch or a campaign; your notes show on every trend chart too, and anyone on your team can delete them.
• Pages: every page on your site with human visits and the AI assistant visits it got. Jump to any page to edit it. Below it, each page's AI reads and visits from AI answers over the last 30 days sit next to how many of your visibility scans cited it. Pages that AI assistants open while answering people but that no scan has cited are marked "Read, not cited yet", with a Create Content shortcut; pages a recent scan cited but no AI agent fetched in 30 days are marked "Cited, no recent reads".
• AI Agents: which AI crawlers visit your pages (assistants like ChatGPT, Claude and Gemini, training and research bots, SEO crawlers), how often, and the trend over time. The tab says which pages these numbers cover. To count AI traffic across your whole site, open Integrations and look under AI traffic: a Cloudflare Worker (on a Cloudflare subpath, an upgraded version of the Worker you already run) or the WordPress plugin. The Setup tab links there too. If your domain's DNS is on Cloudflare but your Pendium pages aren't on a subpath, the Cloudflare Worker there is a standalone one: it counts AI crawlers and visits from AI answers across your whole site without changing how your site is served. If your website is on a subdomain (shop.yourbrand.com), Pendium checks the DNS that serves it (usually your main domain's), and the Worker runs on that subdomain only. A subdomain a site builder gives you, like yourbrand.substack.com, can't run it. On WordPress, use the Pendium plugin for WordPress instead: download it from Integrations, paste your connection key under Settings, Pendium, and you're connected. Use one or the other, not both. If your site runs on Vercel, a Vercel drain counts it instead. Whichever you set up, click Verify connection at the top of its tile: Pendium sends one request to your site and confirms it arrived through that connection, usually within a minute, and the tile then shows as Connected. If someone else runs your site, send them the steps from there. If your host caches pages, cached visits never reach WordPress, so counts come out low. Otherwise the tab checks which platform your website runs on and whether it already has a Google Analytics tag, and offers to connect Google Analytics, which shows the visitors AI answers send across your whole site. If we got your platform wrong, pick the right one. Below that, the AI request log lists each AI agent request from the last 7 days (time, agent, page, status, country), newest first, filterable by agent, type and page. Ask an assistant about your brand, then refresh the log to see whether it opened your pages.
• Visitors: people who came from AI answers and other sources, from Google Analytics once it's connected, including how engaged they are (engagement rate and average session) next to your site's average.
• Search: impressions, clicks, CTR and average position from Search Console, by page and by query, plus content opportunities: queries where you get impressions but few clicks, and queries that mention AI tools.
• Setup: whether your site is public, connecting Search Console, AI traffic across your whole site (opens Integrations), sync status, and the analytics tag for a site you render yourself.

If you render the site yourself

When the brand's site runs on your own code with Pendium as the content source, add the brand's analytics tag to your pages and report AI crawler visits from your server. Both are on the Setup tab under Running your own front end? See Use Your Own Front End.

Why it matters

Search Console is the measurable rung of the visibility ladder: crawlable → measurable → tactical. Until Pendium can measure real search impact, it holds off on recommending search-specific content work — so connecting GSC unlocks more useful recommendations and lets you prove that the content you ship actually moves impressions and clicks.