Niches · SEO & search visibility
Report how the user's own site performs in search
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
Clicks, impressions, click-through rate and average position by query and page for the asked period, each row dated, read with a read-only scope, for both URL-prefix and Domain properties, with the row cap and any data dropped by grouping stated in the docs.
Measured, for our own tests: a 28-day query and page pull for a small site completes in under 5 calls. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: which queries bring people to my site
, what changed in my search traffic this month
, which pages are close to page one
, give me a weekly search report
Does the job, with a limit 4
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Ahrefs D Ahrefs Pte. Ltd. | GSC Insights endpoints (keywords, pages, performance-history) return clicks, impressions, CTR and position free of units, but only for a Search Console property connected to an Ahrefs project; Domain-property support and row caps aren't stated, and acc-18's plan refused every GSC tool over MCP. source |
| Google Search Console API B Google LLC | searchAnalytics.query returns clicks, impressions, CTR and position by query, page and date under webmasters.readonly, for URL-prefix and sc-domain properties; 25,000 rows a call, 50K a day, top rows only and grouping losses are documented. acc-12 hit a not-verified 404 on a Domain property. source |
| Manifold C Jesse Sibley, trading as Manifold (sole trader, United Kingdom) | console_get_search_analytics returns clicks, impressions, CTR and position by query, page and date for sc-domain and URL-prefix properties, free, 16 months, grouping differences stated. Pages cap at 1,000 rows, so large pulls need cursors, and the connection also submits sitemaps, so it is not a read-only scope. source |
| SE Ranking API + MCP E SER Acquisition Inc. | Get Google Search Console data returns query, impressions, clicks, CTR and average position for a project site, but takes only site_id: no date range, no page dimension, no dated rows and no stated row cap. source |
Couldn't check 1
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Similarweb D Similarweb Ltd. | Docs not read: Similarweb's terms bar robots and other automated means on its Site and Platform, so this pass kept the 5 November pause. Whether any first-party Search Console connection exists is unread. |
Doesn't do this job 7
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| DataForSEO B DataForSEO OÜ | No Search Console connection or first-party clicks and impressions; acc-07 pairs DataForSEO with a separate Search Console integration. source |
| Keywords Everywhere API + MCP E Axeman Technology Solutions LLP | No Search Console or first-party data; the 14 tools are third-party keyword, traffic and backlink lookups. source |
| Lordevo Shop E Lordevo (no legal entity named) | No Search Console or analytics connection; the tools read public pages only. source |
| Majestic API F Majestic-12 Limited | A backlink index only; no Search Console or first-party traffic. source |
| Moz API D SEOmoz, Inc. | No Search Console or first-party traffic method in the 74-method index. source |
| Semrush API + MCP C Semrush Inc. | No Search Console bridge in the v3 or v4 indexes; figures for the user's site are Semrush estimates, not first-party clicks and impressions. source |
| SpyFu API D SpyFu, Inc. | No Search Console or first-party data; every API reads SpyFu's own index. source |
What stops agents finishing
- the site is not verified in the account the agent signed in with
- Domain property not reachable through the tool (acc-12)
- vendor plan refuses Search Console tools over MCP (acc-18)
- daily row cap and top-rows-only reporting hide long-tail queries
Around it
Before: chat.user-names-site. After: cms.edit-in-place, product-analytics.dashboard-digest, notifications.digest-batch.
Where this comes from
Weight 24 of 100 in SEO & search visibility: 8 of 34 use-case memberships across 32 accounts (acc-01, 03, 04, 07, 12, 18, 22, 25); the most described job on Hacker News and in agent repos
The same as data: /api/v1/use-cases/seo.own-site-performance.json, or the MCP tool get_use_case with id seo.own-site-performance. Other jobs in this category: /api/v1/niches?category=seo.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.