When should you use it?
- You publish content that brings in leads and only notice drops weeks later
- You have more pages than time to audit them
- You want a concrete edit to make, not another dashboard
Not for: Sites without Search Console access; Drops caused by technical problems such as indexing errors, which this does not check
What do you need, and what do you get?
You need
- An n8n instance
- Your Search Console property, such as sc-domain:example.com
- OpenAI and Slack credentials
- Pages that are publicly reachable for the scrape step
You get
- A weekly Slack message per declining page
- The drop in clicks and position, with a short reason
- Three title rewrites and one missing heading with what it should cover
How does it work, step by step?
- Import and configureImport the template and enter your Search Console property in the config node.
- Connect accountsConnect Search Console, OpenAI and Slack, and choose the channel for the report.
- Run it onceTrigger a run and check that each reported page really lost clicks in Search Console.
- Sanity-check the adviceRead the suggested titles and heading against the page and the queries before editing anything.
- Make one change at a timeUpdate the title or add the section, note the date, and compare the next month's numbers.
The prompt
The original prompt by Shun Nakayama, word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in n8n and ChatGPT. Values in lime are placeholders.
Original prompt by Shun Nakayama
You are an expert Web Editor skilled in SEO analysis.
You are analyzing a client's website traffic to improve rankings.
The following page has seen a DROP in rankings and clicks compared to last month.
Analyze the "Search Queries" and the actual "Article Structure" to understand the site's genre and target audience instantly.
Provide the most effective improvement plan for that specific audience.
## 🔹 Analysis Data
- URL: {{ $('Format Queries').first().json.target_url }}
- MoM Change: 📉 Clicks {{ Math.round($('Format Queries').first().json.clicks_diff) }} / Rank {{ Number($('Format Queries').first().json.pos_diff).toFixed(1) }} (Positive value means rank dropped)
- Search Queries (User Needs):
{{ $('Format Queries').first().json.query_summary }}
## 🔹 Article Content (Current Reality)
- Title: {{ $json.page_title }}
- H2 Headings: {{ $json.h2_tags }}
## 🔹 Writing Rules (Strict)
1. **Do NOT use Markdown bolding (asterisks).** It makes Slack hard to read.
2. Do NOT use cliché AI phrases like "Ultimate Guide" or "Comprehensive Analysis".
3. Write in a human, engaging tone appropriate for the specific genre.
## 🔹 Output Format
Use the following emoji structure. No greetings.
🚨 Alert: Ranking/Click Drop
(Start by stating the quantitative drop: "Clicks dropped by X, Rank dropped by Y". Then, analyze the root cause of WHY Google/Users abandoned this page by comparing queries vs content. Be sharp. e.g., "Title is too generic", "Answer is buried too deep".)
🧐Search Queries
{{ $('Format Queries').item.json.query_summary }}
✨ Title Improvement Ideas (3)
1. [Specific idea with numbers/benefits]
2. [Idea appealing to "FOMO" or curiosity]
3. [Different angle from competitors]
📝 Missing H2 Heading to Add
(Propose ONE missing piece to satisfy the search intent. Explain why this heading is needed and what content it should cover.)Exactly as published by Shun Nakayama in Auto-audit SEO traffic drops with AI & Google Search Console to Slack.
Our adapted version (optional)
Fill in the blanks (optional; the copied prompt uses your values)
This page lost search traffic last month. Help me work out why and what to change. Page: {url} Change vs the previous month: clicks {clicks_change}, average position {position_change} Same month last year, if known: {last_year} Top search queries with position and clicks: {queries} Current title: {title} Current section headings: {headings} First say whether this looks seasonal, a mismatch between queries and content, or unclear. Then, if it is a mismatch, name the gap in one sentence, suggest three accurate titles that match the queries, and propose the single new section that would best answer them, with three points it should cover. Plain text, no bold, no greeting, and nothing the page could not honestly deliver.
What can go wrong?
- Seasonal topics drop every year; compare with the same month last year before you rewrite a page.
- Some title ideas lean on curiosity or fear of missing out; keep titles accurate to what the page delivers.
- The scrape reads only the title and H2 tags, so it can miss content inside other headings or scripts.
- Some comments in the template code are in Japanese; they do not affect how it runs.
Our take
Good SEO advice usually comes down to one question: does this page answer what people searched for? This template asks exactly that, page by page, by putting the real queries next to the real title and headings. The prompt is opinionated in useful ways: no greetings, no bold, no stock AI phrases, a quantified opening line and exactly one heading to add. We ran it word for word on a synthetic gardening page that lost 412 clicks while ranking for winter storage questions under a generic title and spring-focused headings. It named the mismatch plainly, proposed three titles built around storing tubers, and suggested a single section on winter storage covering timing, drying, temperature and rot checks. It followed every formatting rule. Two cautions from our side: rule out seasonality first, since a winter topic will dip in summer whatever you do, and keep curiosity-style titles honest so the page still delivers what the title promises.
Where the time goes back: Instead of digging through Search Console for losers and guessing why, you get a short list of pages with a specific edit for each.
FAQ
How does it pick pages?
Does it change my site?
Why no bold text?
Source and credit
The original prompt on this page is by Shun Nakayama, shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- Auto-audit SEO traffic drops with AI & Google Search Console to Slack
- Creator
- Shun Nakayama
- Published on
- n8n workflow templates
- Original date
- Dec 1, 2025
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- n8n
- AI dry run
- Oct 22, 2026: passed. Dry-run tested by our AI test agent on sample input. One title leaned on curiosity as the prompt asks; our pitfalls ask for accurate titles.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.