Automation library · Content

Auto-audit SEO traffic drops with Google Search Console

Started by a clock, and works across Slack. It hands the judgement calls to OpenAI. 13 steps, 2 loops or waits: a working afternoon to understand properly.

MediumCalls a model: OpenAI

13 stepsMedium: a working afternoon
0Branches: places the flow splits
2Loops or waits
1Service it connects to

The flow

Starts it 1Model 1Logic 7Service 4

The steps in the order they run, from what starts it.

  1. 1Weekly ScheduleSchedule triggerStarts it
  2. 2📝 Edit Me: ConfigSetLogic
  3. 3GSC: Compare PeriodGoogle Search ConsoleService
  4. 4Filter: DropsFilterLogic
  5. 5Loop PagesSplit In BatchesLogic
  6. 6Wait 1sWaitLogic
  7. 7GSC: Get QueriesGoogle Search ConsoleService
  8. 8Format QueriesCodeLogic
  9. 9Scrape PageHttp RequestService
  10. 10Extract ContentHtmlLogic
  11. 11AI AnalystOpen AiModel
  12. 12Format for SlackCodeLogic
  13. 13Notify SlackSlackService

How it's built

Starts on
A clock
Steps
13, 2 loops or waits
Size
Medium: a working afternoon
Connects to
Slack
Model
OpenAI

Questions

What does it need to run?

An n8n account, plus your own Slack account, and a key for OpenAI. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

Yes. It calls OpenAI. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Plan an afternoon. 13 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 13 steps before you point it at anything that matters.