Run SEO as a daily discipline
Own the daily loop (auth check, data pull, anomaly triage, an honest brief), plus the weekly strategy cadence and the real mechanics of shipping a fix, a PR a human merges and a verified re-crawl.
Copy this prompt to start your first task:
What is this workflow?
Running SEO as a daily discipline means giving a teammate a fixed loop instead of a one-time scan: check Search Console access, pull the data, triage anomalies, and send an honest brief every morning — including an honest “no data today, here's why, here's the unblock” on days access is down, instead of a fabricated one. It builds and maintains a 4-layer keyword map (brand terms already ranking, real non-brand queries already surfacing, aspirational keywords worth building for, and comparison terms), routing each keyword to the page type built to earn it. Every Monday the brief turns into a ranked proposal — one to three moves, each naming the target keyword or page, the expected impact, and the cost — and every metadata, schema, or content gap it finds ships as a reviewable PR, tagged to a human reviewer, and verified against the live URL and a requested re-crawl after merge, never called “done” on the strength of a merged PR alone.
Always waits for a human:
- Merging any PR: it opens PRs and tags a reviewer, it never merges its own work and never pushes straight to main
- Posting anything to LinkedIn, X, or Hacker News: it only drafts; you review the wording and post from your own account
- Publishing a case study
- Spending money on anything: no paid backlinks, no paid promotion, ever
- Clicking “Request indexing” in Search Console: the re-crawl request is UI-only, so it preps the URL and asks, but a human clicks it
Not in scope, full stop:
- Buying backlinks, fake accounts, paid guest posts, comment spam, or reciprocal-link schemes. Proposed backlinks are always earned, drafted for a real account to post
- Redesigning a page: it flags a layout that's hurting click-through rate, it doesn't ship a redesign
- Deciding the product roadmap: it proposes what's worth building for search, you and the team decide what actually gets prioritized
- Paid ads, or any channel besides organic search
- Talking to customers directly
How to use this workflow
Hire the Growth Hacker, and write the bio around the daily discipline, not a one-time scan
Open AI Teammates in the sidebar, click Hire AI Teammate, and pick the Growth Hacker template. The default bio undersells this as a one-time audit. Replace it on the Profile step so the teammate starts out already knowing this is a standing operating role, not a checklist:
Confirm the name and click Create teammate. They land in their own channel, which is where you'll send everything below. More on hiring →
Connect GitHub: the two-layer flow
Fixes ship as pull requests against the site's repo, never pushed directly. A workspace admin installs the GitHub App once, in Settings → Integrations (a one-time, workspace-level step), then grants this teammate the specific repo (here, helio-website) it's allowed to open PRs against. Connect GitHub →
The weekly backlink drafts don't need any extra connection: posting stays with you (see the boundaries above), and Helio's LinkedIn connector is identity-only — it can't post or hold drafts anyway. The drafts land right here in the teammate's channel; you review the wording and post them from your own account.
The Search Console gap: no native connector, so it reads GSC through a browser instead
Helio doesn't have a native Google Search Console connector. There's no “Connect Search Console” OAuth button to click, and none of the marketplace skills wrap its API either. What this teammate actually does is install the Stagehand Browser CLI skill (Skills & Plugins → Productivity) and use it to open Search Console the way a person would: log in, click into URL Inspection, read the Performance report. It's slower than an API pull and it can't do anything the Search Console UI itself can't do, but it's real data, not a guess, and it means the daily loop below doesn't stall on a connector that doesn't exist.
Installing the browser skill doesn't grant a logged-in Google session, though — the teammate still needs the Search Console account's credentials to get past the login page. Add that Google account to the Vault and share it with this teammate before the Day 1 audit, or the first login attempt (and every daily loop after it) blocks. Share credentials →
Kick off the Day 1–2 landscape audit and keyword map
The first real work in a new SEO teammate's week is the baseline everything else compares against: pull every production URL, see what's actually indexed, then build the keyword map the daily brief will reference from here on. That starts broad, not with one page:
Ship a fix for one surfaced gap: draft, PR, a human merges, then verify it actually landed
Once the daily brief surfaces something real (a keyword the site should own but has no page for, a schema warning, a missing meta description), the response is the same every time: confirm the gap is real, draft the content, open a PR, and wait. This teammate never merges its own work:
Put the daily brief on automation
Open Automations in the sidebar and click Create via Chat. On Home, choose this teammate and send the prefilled scheduled-task starter. When the interview asks what to schedule, answer with the recurring job below. This is the loop that runs every morning without anyone asking for it, and the one place “honest over polished” matters most, since a fabricated brief on a day access is down is worse than no brief at all:
Same-day escalation, and the Monday proposal that runs on top of it
Most of what the daily loop finds waits for the brief. A short list doesn't: a canonical, robots, or noindex regression on a live URL; a previously-indexed page dropping out of the index; a schema warning in Rich Results Test; a Search Console manual action or security notice; or a ranking or CTR drop past a threshold you've agreed on for a page that matters. Those get a same-day DM, not a line in tomorrow's brief:
On top of that, Monday's brief turns into a proposal instead of just a report: one to three ranked actions, each naming the target keyword or page, the expected impact, and the cost, so you're picking from options instead of starting from a blank page every week.
This flow waits for you on five things: merging any PR, posting to LinkedIn, X, or Hacker News, publishing a case study, spending money, and clicking “Request indexing” in Search Console. Everything else — reading Search Console data, drafting content, opening PRs — runs on its own. See Control for how approval works in Helio generally.
Tips for Better Results
| Tip | Description |
|---|---|
| Share the Search Console credential before Day 1 | There's no native connector, so this teammate logs in through a browser skill instead. Skip the Vault share and every login after the first blocks too. |
| Expect an honest “no data” day, not a fabricated brief | If Search Console access is down, the brief says so and tells you the unblock — it never invents numbers to stay on schedule. |
| A merged PR isn't “done” yet | The fix isn't verified until the live URL is curled and a re-crawl is requested — that check happens after you merge, not instead of it. |
| Watch for same-day DMs, not just the morning brief | Regressions like a noindex slip, an index drop, or a schema warning get flagged the day they're found, separate from tomorrow's brief. |
Common Questions
GTM & Growth
Back to the GTM & Growth use case overview.
Run Google Ads end to end
Own the account, not a checklist: intake, keywords, daily optimization, and a self-refreshing report.
Track KOL campaigns
Turn a confirmed KOL list into tracking links and a click-data report.
Track KOL campaigns
Turn a list of confirmed KOL accounts into per-channel tracking links and a running click-data report, no manual UTM building.
Run Google Ads end to end
Own the account, not a checklist. Intake, keyword research, campaign build, daily optimization, anomaly escalation, and a self-refreshing weekly report.