Find the pages losing clicks in Search Console, from Claude or ChatGPT
Compare two Search Console periods, isolate the pages and queries going down, check their indexing: one conversation with your AI, no export, no access to the property.
Published on October 28, 2026
In short
- With Persyst’s Search Console connector, your assistant compares two periods, isolates the pages losing clicks and the queries behind them.
- It then checks the indexing of the declining pages and the sitemap status, and suggests leads.
- Everything is read-only, on the properties opened to the member, with no CSV export and no invitation to the property.
Which pages lost the most clicks this month compared with last month, and why?
Three pages account for most of the drop. /pricing loses 38 clicks: the average position on “crm software price” goes from 4.2 to 8.9. /blog/follow-up-guide loses 22 clicks with stable impressions: CTR is down, the title needs work. /features loses 15 clicks, and the inspection shows a canonical pointing to another URL since the 12th. I would start with that canonical.
Sources consulted
- Search Console · period comparison
- Search Console · queries per page
- Search Console · URL inspection
The problem: a drop, but where?
The Search Console dashboard shows a site losing clicks. It does not say which ones. To find out, you compare two periods, filter by page, then by query, export, cross-check, and inspect the suspicious URLs one by one.
An AI assistant does this work in one conversation, provided it can read the property.
What the assistant does, step by step
With Persyst’s Search Console connector, the question “Which pages lost the most clicks this month?” unfolds like this:
- Compare two periods by page (
compare_search_analytics). Differences in clicks, impressions and position are computed server-side. - Drill down to queries for the declining pages (
query_search_analytics, page and query dimensions). The assistant tells a lost position from a lower CTR at the same position. - Inspect the URLs involved (
inspect_urls, ten at most): crawling, indexing, the canonical chosen by Google. - Check the declared sitemaps (
list_sitemaps) when a recent page is missing.
The answer separates the likely causes: lost position, a title that attracts fewer clicks, an indexing issue.
Asking the right way
- Give the periods: “the last 28 days against the previous 28, ending three days ago”.
- Name the property if you have several: “on persyst.ai”.
- Ask why, not just for the list: the assistant then chains the query analysis and the inspection.
Three questions to try
- “Which queries are on page 2 with many impressions and a low CTR?”
- “Compare mobile and desktop clicks on our connector pages this quarter.”
- “Are these five URLs indexed, and with which canonical?”
Setup
- An administrator connects the property in Data sources, with the Google account that owns it. Persyst only asks for read access; the Search Console guide walks through it.
- They open the property to the marketing team, a consultant or a single person.
- Each member adds Persyst to their assistant (getting started) and asks their question.
Limits to know
- Sixteen months of history at most, and about two days of delay: those are Google’s.
- Inspection works URL by URL, within the property’s daily quota; Persyst never crawls a whole site.
- No Google Analytics or Google Ads in this connector: Search Console clicks are not sessions.
Questions
Frequently asked questions
Do I need to be a user of the Search Console property?
No. The person who owns the property connects it once in Persyst. Authorized members then query it from their AI, without being invited to the property.
Are today’s numbers reliable?
Not yet. Search Console data arrives about two days late. For a comparison, end the period three days before today.
Why is the sum of clicks per query lower than the total?
Google leaves out anonymized queries. The gap is normal; compare pages with pages, or totals with totals, but not one with the other.
Can the assistant request indexing or submit a sitemap?
No. The connector only has Search Console’s read scope. Actions happen in Search Console, by someone who has access to it.