Search & analytics
An SEO agent that reads Search Console every week and acts on it.
Connect Google Search Console and OpenHelm's SEO agents work from real search data. A weekly digest reads clicks, impressions, CTR and average position, then writes the figures back to each post in the Content Log. Technical checks watch index coverage, and once a fix is live the agent resubmits your sitemap so Google fetches the site again.
What agents do with Google Search Console. Recurring jobs, checked every run.
Weekly SEO digest
Each week, summarise clicks, impressions, CTR and average position for the product, with the pages and queries that moved and why they matter.
Measured performance on every post
Write each post's clicks, impressions, CTR and position into the Content Log with the date measured, so a post nobody finds is a measured zero rather than a guess, and the lifecycle agent knows what to refresh or prune.
Index coverage checks
Check which pages Google has and has not indexed, work out the likely cause for the ones left out, and fix what the agent can fix in the repository.
Sitemap resubmission after fixes
Once a fix is live, resubmit the sitemap through Search Console so Google re-reads the site, instead of waiting for its next routine crawl.
Connect Google Search Console. A few minutes, once.
Connect Google Search Console
Add Google Search Console under Connections in the OpenHelm app and complete the hosted sign-in, or mint a connect link programmatically with POST /v1/connections/links.
Describe the job in plain English
Tell OpenHelm what you want done and how often. It drafts a plan with a schedule, the tools it will use, and a clear definition of done.
Approve the plan
No job fires until you have reviewed the plan. Set the autonomy level to control whether writes execute directly or queue for your approval.
It runs, self-checks and reports
Runs execute in isolated cloud sandboxes on schedule. An independent evaluator scores each run against the goal, and results arrive as logs, emails or data-table rows.
Or provision it over the API (see the Connections API docs):
curl https://api.openhelm.ai/v1/connections/links \
-H "Authorization: Bearer oh_live_..." \
-H "Content-Type: application/json" \
-d '{ "provider": "<provider id>", "name": "Google Search Console" }'
# Returns a short-lived hosted link. Open it once to authorise,
# then poll GET /v1/connections until it shows as authenticated.Questions
Can OpenHelm request indexing for a single page?
No. Google offers no public API to request indexing of an arbitrary URL; the button in Search Console has no API behind it. Resubmitting the sitemap is the documented way to ask Google to look again, so that is what the agent does.
How does OpenHelm connect to Google Search Console?
Through a scoped OAuth grant: you sign in to Google Search Console once via a hosted connect flow, in the OpenHelm app or via a connect link minted with POST /v1/connections/links. OpenHelm stores no passwords, the grant is limited to what your jobs need, and you can revoke it at any time.
Can the jobs run on a schedule without me?
Yes, that is the point. Jobs run once, on an interval, or on a cron expression. A scheduler fires them, a watchdog times out anything hung, and a separate evaluator checks each run actually advanced the goal. You approve the plan before anything runs for the first time.
Is my Google Search Console data safe?
Each run executes in an isolated cloud sandbox with scoped, revocable credentials and no middle-layer copy of your data. Every action is logged per run, results come back with evidence, and the agent never fabricates data it could not verify.
More in Search & analytics
Give your product a team that never clocks off.
Start free in the browser, or run it on your Mac with your own Claude Code or Codex plan.