GSC drop → refresh + Notion

Refresh pages losing clicks, write findings to Notion.

Find GSC click drops → At least N? → Refresh page → Export to a tool → Notify

Because a click loss is money you can already see. This workflow starts where the loss is undeniable and then asks whether the answer explains it.

Yes, and that is the point. Same position with fewer clicks usually means an answer took the click; a lost position is a different problem.

Because findings need somewhere permanent that is not a chat message. Any destination with an API works; Notion is just the common one.

The page, the queries that lost clicks, the answer that now covers them, and the refresh it drafted. One row per page rather than a report.

Your threshold, but a useful default ignores anything under a fortnight of decline, because weekly variation in Search Console is large.

It compares against the same window last year where you have the history. Without a year of data it says so instead of pretending.

Yes, with their Search Console connected to their project. The findings stay inside that project, which is what keeps agency work separate.

Then the refresh draft is the wrong answer and the workflow says so: it flags pages where no competing answer appeared, which usually means demand moved.