Search engines & SEO
Connect Google Search Console and Bing Webmaster Tools under Project settings → Integrations → Search engines. Their numbers then show on the website's SEO page, next to agent sessions in Visitors → Humans vs agents, and in Ask AI and the MCP server.
Google Search Console
Sign in with Google (read-only)
Bing Webmaster Tools
Bing Webmaster Tools → Settings (top right) → API access → API key → Generate. One key covers every site verified on your account.
Connect
Google Search Console. Click it and sign in with Google, then pick the property (a domain property such as sc-domain:example.com, or a URL prefix). Access is read-only.
Bing Webmaster Tools. In Bing Webmaster Tools open Settings → API access → API key and generate a key, then paste it and pick the site. One key covers every site verified on your Bing account. It's worth connecting even if most of your search traffic is Google: Bing's index also feeds Copilot and ChatGPT search.
On connect, AgentStats imports the last six months of daily clicks and impressions (Bing only has data from the day the site was verified), then refreshes them every hour.
The SEO page
The website's SEO page has three tabs.
Performance
Clicks, impressions and click-through rate per day from both engines, compared with the previous period, and the top search queries and pages with their average position. Google and Bing are added together: a query is matched case-insensitively and a page by its path.
Search engines report two to four days late, so the most recent days are empty; the Data through figure says which day the numbers run to.
Indexing
AgentStats reads your sitemap (from the Sitemap: lines in robots.txt, or /sitemap.xml), asks each engine about every page in it, and lists what to do:
| Suggestion | What it means | What to do |
|---|---|---|
| Fix before submitting | Google can't index the page: robots.txt or noindex blocks it, it redirects, or it returns an error | Fix the page, or take it out of the sitemap |
| Not on Google yet | Google hasn't indexed it ("Discovered – currently not indexed", "URL is unknown to Google"…) | Click Resubmit sitemap to Google so Google reads it again. For a page you need sooner, click Request indexing: it opens the page in Search Console, where the button is (Google has no API for single pages) |
| Not on Bing yet | Bing hasn't crawled it | Click Submit, or Submit all: AgentStats sends them to Bing, which usually crawls them within a day |
| Changed since the last crawl | The sitemap's <lastmod> is newer than the engine's last crawl | Resubmit the sitemap to Google, or request indexing; resubmit the pages to Bing |
| Google chose another canonical | Google indexes a different URL as the main version of the page | Look for duplicate pages or conflicting canonical tags |
The Sitemaps table shows whether each engine has your sitemap, and submits (or resubmits) it to either. The first time you submit to Google, Google asks you to allow AgentStats to submit to Search Console; connecting only asks for read access. Submitting needs Owner or Full user permission on the property.
A check (on your first visit, daily, or with Check now) goes through every page that's due and keeps going until it's done. It runs in the background: the page shows how far it has got and fills in as results come in, and you can leave it. Pages that aren't indexed yet are checked again daily; indexed pages weekly, or sooner when their <lastmod> changes. Both engines limit how fast they can be asked:
- Google answers quickly, up to 2,000 pages a day per property.
- Bing answers about 10 page lookups a minute per Bing account, so a check paces itself: a few hundred pages take under an hour. Websites connected with the same Bing account take turns, so checking several at once takes longer. If Bing slows it down anyway, the check waits and carries on. Pages that already get impressions in Bing count as indexed without a lookup. Bing also limits how many pages you can submit a day (100 for a newly verified site, more later); the page shows what's left.
If your site blocks our crawler from robots.txt or the sitemap, or has no sitemap, AgentStats checks the home page and the pages search engines already show instead.
Page speed
Lighthouse on one or two pages of each kind in your sitemap, on mobile and desktop. Pages built the same way (every blog post, every product, every docs page) score about the same, so AgentStats groups your pages by their path (/blog/*, /docs/*, /pricing) and tests one or two of each, up to 50 pages: the home page first, then the kinds search sends the most people to. Each tested page shows how many pages it stands for. Pick a page from the toolbar, or from Tested pages:
- Lighthouse scores for performance, SEO, accessibility and best practices, the biggest performance wins, and failing SEO checks, from Google's PageSpeed Insights.
- Core Web Vitals (LCP, INP, CLS) from real Chrome users over the last 28 days, from the Chrome UX Report: for the page, or for the whole site when the page has too little traffic. These are what Google uses in ranking. A site without enough Chrome traffic shows Lighthouse's lab values instead.
Page speed is checked weekly. Re-test page runs Lighthouse again on the page you're looking at (about half a minute), any time; Re-test all runs every tested page again, once a day. A full run takes a few minutes (Lighthouse loads each page on Google's servers); pages show as they finish. For on-page basics (titles, structured data, robots.txt, llms.txt), see the website's AI audit.
Self-hosting
- Search Console uses the Google OAuth client in
NUXT_GOOGLE_CLIENT_ID/NUXT_GOOGLE_CLIENT_SECRET. Enable the Google Search Console API in its Cloud project and add<APP_URL>/api/traffic/oauth/google/callbackas a redirect URI. Add thewebmasters.readonlyscope (for connecting) and thewebmastersscope (asked for when someone first submits a sitemap to Google) under Data Access. Google classes both as non-sensitive, so they need no scope review. Then publish the app under Audience: while it's in Testing, only test users can connect and Google expires their connections after 7 days. - Page speed needs one Google Cloud API key in
NUXT_GOOGLE_API_KEYwith the PageSpeed Insights API and the Chrome UX Report API enabled. Both are free (no billing account), about 25,000 PageSpeed runs a day and 150 Chrome UX Report requests a minute. Restrict the key to those two APIs and to your server's IP addresses, not to websites: a key limited to websites (referrers) is refused when the server calls. - Every project's page speed runs share that key. Full runs go two projects at a time across all your servers (
NUXT_PAGESPEED_JOBS), and the weekly runs stop for the day at 80% of the daily quota, leaving the rest for re-tests. If Google raises your quota, setNUXT_PAGESPEED_DAILY_QUOTAto the new figure.
Security
Connecting Google gives read-only access; submit access is asked for separately, the first time you submit a sitemap to Google. Both it and the Bing key are only used for reading reports and for the submissions you click. Keys and OAuth tokens are encrypted at rest (AES-256-GCM).