Integrations
Google Search Console
Google Search Console is the record of which searches send people to a page, and which pages get the click. Each morning at 08:30 UTC we store that day’s clicks, impressions, and pages on the client record. On Monday at 09:00 UTC a weekly plan becomes a card. A person approves that plan before any note is written. Nothing on this path publishes by itself.
Why it is here
Benefit
You can see which searches send people to a page, and which pages deserve the next piece of work.
The numbers are stored once a day. Nobody has to export a spreadsheet to read them.
The path
How it works
Each morning the handoff worker asks Google Search Console for the finished day and stores the clicks, impressions, and pages. The client’s Search tab reads those stored rows. It does not call Google on every page view.
After a clean load, the client’s lead and the SEO and Analytics agent get a note that the numbers are new.
On Monday a weekly report takes a 28-day snapshot and files one card. The SEO agent writes a short narrative and a list of topics. Those topics are not posts. A person approves the plan before any note is written.
When that plan is approved, a daily job files the blog cards for that day. After a blog passes its release check, another job files one social card. Nothing is scheduled, and nothing is added to the library, until a person says so.
What you get
Deliverables
- A Search tab of stored clicks, impressions, and pages.
- A weekly report card.
- A topic list for the week, not finished posts.
- Blog cards for an approved day.
- One social card after a blog passes its release check.
When it starts
Workflows
Search sync
Starts Every day at 08:30 UTC
Loads Search Console into stored facts and tells the assigned agents the numbers are new.
SeoReportWorkflow
Starts Monday at 09:00 UTC
Files the weekly report card and asks for a content plan. It does not publish.
BlogBatchWorkflow
Starts Every day at 14:00 UTC
Files that day’s blog cards after the plan is approved. It does not publish.
SocialFromBlogWorkflow
Starts After a blog release check passes
Files one social card. It does not schedule a post.
On this site
Where this connects
- AI visibility Search Console shows which pages already earn a click. AI visibility is the service for being found in AI search.
- HQ The Search tab on HQ is where the stored rows and the weekly card live.
Questions, answered
FAQ
What does the Google Search Console integration do?
It stores each day’s search clicks, impressions, and pages on the client record, then turns a 28-day snapshot into a weekly plan a person can approve.
When do the Search Console workflows start?
Search sync starts every day at 08:30 UTC. SeoReportWorkflow starts Monday at 09:00 UTC. BlogBatchWorkflow starts every day at 14:00 UTC, and only files cards after the plan is approved. SocialFromBlogWorkflow starts after a blog release check passes.
Does it publish or change the site?
No. The weekly job files a report card and a topic list. Those topics are not posts. A person approves the plan before any note is written, and the jobs do not publish.