Loop HUX-L2 · Marketing — Huxberry.com · reports to Sherif

Where we rank, what competitors changed — every morning.

Tracks huxberry.com's Google rankings for the money keywords and diffs competitors' product pages, prices and promos daily.

Ready to buildWave 2🕐 Daily⚙️ Scheduled scrape-diff
Part 1 — the plain-english view

The search battlefield, checked before breakfast.

What it watches
  • Our rankings for the money keywords (we're #2 for “organic mattress Dubai”)
  • Competitors' product pages: price changes, new promos, copy changes
  • Once tracking-foundation verifies Search Console: what searches actually bring us clicks
When & how it speaks

Daily short digest to Sherif: rank movements and competitor changes worth knowing. Quiet when nothing moved.

Why it exists

Rank drops and competitor price moves are invisible until revenue already fell. A daily position file plus a scrape-diff turns those into same-day signals — and feeds the content loop's keyword decisions.

#2
our current rank for “organic mattress Dubai” — worth defending daily
4
competitor sites watched for page, price and promo changes
Daily
diff cadence — same-day awareness instead of quarter-late surprises

Daily

Early morning

🔎

Pulls rankings

SEO APIs for the tracked keyword set

🕸️

Diffs competitors

Product pages, prices, promos vs yesterday

💬

Digest to Sherif

Movements only; quiet when static

📚

Feeds the content loop

Keyword gaps flow into article planning

What it will never doNever touches the website.
Where it stands today · July 2026Design ready, not yet built — the blocker is credentials (SEO tool API keys into the vault) and the Search Console side of the tracking foundation. The scraping approach is the proven pattern from the retired competitor-scanner job.
Part 2 — under the hood

How it's wired: systems, models, and the path a number takes.

For implementers and the technically curious. The full build sheet — verified queries, thresholds, and build notes — lives on the specs page.

ReadsSEO APIs
Rankings for the tracked keyword set
ReadsCompetitor sites
Scrape of PDPs, prices, promos
StepScrape-diff
Position file + page diffs vs yesterday
StatePosition history
Rank trends over time
DeliversDaily digest
To Sherif; feeds HUX-L4's keyword data
System we read Automated step State / memory Human decision
SystemRole in this loop
SEO toolingahrefs / semrush CLIsRanking pulls via existing CLI tooling with vault-held keys.
Search Consoleafter HUX-L0First-party search data — which queries actually bring clicks (CLI path; no MCP exists).
Agent Vaultcredential storeWhere API keys live. Loops get read-only credentials from the vault; nothing is hardcoded in scripts.
Hermesagent runtime on our serverThe scheduler that wakes the loop up. Each loop is a cron job under a Hermes profile; the planned bizops profile will host the business digests (IT loops run under vpsops).
Healthcheckshealthchecks.huxapps.comThe dead-man's switch. The loop pings it only after a clean run — if the loop dies or errors, the ping stops and Healthchecks raises the alarm independently. This is how 'never silent' is enforced by machinery, not promises.
Email renderer + gwsrender_email.pyAll digests pass through one shared renderer: Huxberry-branded HTML, tables for repeated rows, a coral 'needs your response' box when the loop has questions, and an arrow link on every record. Sent from the loops mailbox via the Google Workspace CLI.
Model / brainWhat it does here
None at run timedeterministic scriptA normal cycle is a plain Python script — no AI tokens are spent unless a diagnosis or judgment step is actually needed. AI wrote the script; the script does the rounds.
GPT-5.5 via Codexthe bulk-work modelWrote and maintains the mechanical parts — SQL, diffing, digest assembly. Effectively free on our existing subscription, so routine cycles cost almost nothing.
State & memory

The daily position file + competitor page snapshots — diffs need yesterday.

Delivery

Daily email/Telegram digest to Sherif; movements only.

Safety rails

Read-only scraping and API pulls; competitor sites are diffed respectfully (throttled, cached).

Before it can run for real
  • SEO tool API keys into the vault
  • Search Console verification (part of HUX-L0)
Full build sheet →