Product / Measure / Search Console
SerpDad and Search Console: from new queries to the next page you plan.
Search Console shows you thousands of rows. SerpDad turns them into decisions on your page plan: new queries wait in a keyword inbox until you route them, every planned page shows its 28-day movement, and a drop or rise can start a workflow.
Syncing and the keyword inbox cost nothing. Routing a query shows an estimate first.
The data was never the problem. Knowing which page it belongs to was.
Queries nobody planned for
The performance report fills with searches your keyword list never had. They sit there until someone exports them to a spreadsheet, which is rarely.
Movement with no page attached
A position moved. Was it the page you planned for that keyword, or another one? The report shows URLs, not your plan.
Small moves that look big
An average position wobbles from 6.2 to 6.9 and someone asks what went wrong. Nothing did.
The keyword inbox. New queries, free until you route them.
Plan, Keyword inbox lists Search Console queries that match no keyword in the project. They are not keywords yet: they do not count toward keywords stored, and they cost nothing while they wait. Queries with fewer than 10 impressions are left out.
Each query comes with a proposal, such as joining a planned page or needing a new one, and a receipt that shows where its impressions land today.
When you route a query, SerpDad shows an estimate and sends it through a normal run: the live top 10, the grouping rule and a verdict, like every other keyword in the plan.
The nightly sync finds the query
It matches no keyword in the project and has at least 10 impressions.
SerpDad proposes a home
Join a planned page, or a new page, with the evidence for it.
You route it, and see the cost
Routing shows an estimate on your keys, then runs like any other keyword.
28-day movement. Search Console results for every planned page.
Measure, Results compares each page's last 28 days with the 28 days before, and with 3 months. You can read it by map, by territory or by page, so the unit is the page you planned, not a loose URL.
Each row shows clicks, impressions, average position, the movement, a 12-week sparkline and a receipt with the math. Results exports as Markdown.
The same data sets verdicts in the plan. A page whose position is known only from Search Console reads Optimize #N, with N its Search Console average.
| Result | When |
|---|---|
| Moved | Average position changed by more than 3 positions or 8%, whichever is larger |
| No change | A smaller change than that |
| Too new | A new page, with nothing to compare yet |
| Left out | Fewer than 10 impressions |
Drops and rises. Let the nightly sync start the work.
Search Console drop or rise trigger
A workflow starts when the nightly sync finds pages that moved past the line you set, against the 28 days before. Spending steps wait for an approval.
The content audit
The same 28-day comparison sorts every page into a bucket, from quick win and striking distance to decay and prune.
Content decay
For a decaying page, the stored top 10 from before the drop sits next to a fresh one, with the changes marked.
Ready-made workflows. Start from Monthly re-run, Publisher: find decaying posts or Agency monthly client report. Each copies into your workspace as a draft you can change.
Don't trust us. Inspect our own run.
From our own run on serpdad.com
What it won't do. It reports what moved, never why.
Results says what moved and by how much. It never says SerpDad caused a change, and it never explains why a search engine moved a page. When a page decays, SerpDad names what changed in the results and stops there.
The inbox never fills your plan behind your back either. A query becomes a keyword only when a person routes it, after seeing the estimate.
Not connected yet? Setup takes a Google account and two minutes.
Search Console connects per project with read-only access, and SerpDad never changes anything in your property. The first sync reads 90 days of page and query rows. The Google Search Console integration page covers the connection, what flows where and each connection state.
Questions and answers.
Can't find the answer? Email us.
What is the keyword inbox?
A list of Search Console queries that match no keyword in your project. Each one gets a proposal, such as joining a planned page or needing a new page, with a receipt of where its impressions land.
Do inbox queries cost anything?
No. They do not count toward keywords stored and cost nothing until you route them. Routing shows an estimate and then runs like any other keyword.
When does a page count as moved?
When its average position changes by more than 3 positions or 8%, whichever is larger, comparing the last 28 days with the 28 days before. Smaller changes read No change, and pages with fewer than 10 impressions are left out.
Can a Search Console drop start a workflow?
Yes. The Search Console drop or rise trigger starts a workflow when the nightly sync finds pages that moved past the line you set. Any step that spends waits for an approval.
Does SerpDad say why a page moved?
No. It reports what moved and by how much. It never says SerpDad caused a change or explains why a search engine moved a page.
How do I connect Search Console?
In Workspace, Search Console for the project, sign in with the Google account that can see the property and pick it. Access is read-only. The Google Search Console integration page walks through it.
Your data, on your plan.
Plan your first 1,000 keywords free.
Your first plan is free up to 1,000 keywords, with briefs for the top 5 pages. No card needed.