Query × page × date history
Connecting a property backfills about 16 months of Search Analytics, then a daily job keeps the last few days fresh. Device and country are stored alongside, not mashed into one giant cube.
Product
The weekly move is only as good as the rows under it. WiseSEO computes those rows in code. An assistant can explain them later. It does not invent the click estimates.
Connecting a property backfills about 16 months of Search Analytics, then a daily job keeps the last few days fresh. Device and country are stored alongside, not mashed into one giant cube.
Queries are rolled up with an impression-weighted position. Anything in that band, above an impression floor, is a candidate. The sort key is estimated click gain, not vanity position.
A power-law CTR curve is fitted from the property's position buckets. If there is not enough data, a fallback curve is used and labelled as such. Click gain assumes a move to position 3 (from 4–10) or position 8 (from 11–20).
Pages that lose a meaningful share of clicks versus the previous week, and versus the same window a year earlier, are flagged separately so a seasonal dip is not treated as a crisis.
A query is cannibalized when two or more URLs each hold a real share of its impressions. Leader flips versus the previous period are called out. Queries that appear or vanish between 28-day windows are listed too.
The daily sync is the foundation. Email and Slack alerts for click drops, cannibalization flips and sudden new queries are the next layer on top of it.
A remote connector so ChatGPT, Claude and similar tools can ask for this week's move, the decay list and the stored history. The dashboard numbers stay the source of truth. The assistant narrates them.
When you mark a move done, WiseSEO will compare the 14, 28 and 56 days after with the period before. That measurement is not in this release.