Agent operations template

Hermes SiteOps Monitoring Runbook

Use this runbook to connect Hermes-style agents to RedBit monitoring in phases: public health checks now, analytics and Search Console reporting after verification, SEO optimization after data accrues, and AdSense review only after approval.

Copyable Monitoring Runbook

Paste this into a Hermes thread, repo issue, or ops document before scheduling recurring reports. Keep credentials out of prompts and use approved connectors or environment variables for private data.

# Hermes SiteOps Monitoring Runbook

## Phase 0: Start Now
- Check production URL status.
- Check robots.txt and sitemap.xml.
- Check core page coverage in sitemap.
- Review latest deployment and build status.
- Draft a manual SiteOps note from public checks and repo changes.
- Run pnpm siteops:health for the no-credential health report.

## Phase 1: After GA4 And Search Console Verification
- Confirm GA4 data is arriving.
- Confirm Search Console domain property is verified.
- Submit sitemap.xml.
- Inspect core URLs.
- Start daily availability and early indexing notes.

## Phase 2: After 7 To 14 Days Of Search Console Data
- Compare current and previous GSC periods.
- Find high-impression low-CTR rows.
- Find position 8 to 20 striking-distance opportunities.
- Flag impressions-up clicks-down rows for manual SERP review.
- Draft GitHub issues with evidence and acceptance criteria.

## Phase 3: After AdSense Approval And Real Reports
- Review RPM movement cautiously.
- Compare GA4 traffic source, country, device, and engagement changes.
- Preserve evidence for suspicious traffic spikes.
- Do not click ads, test ads, or create pageviews.

## Daily Output
- Health: production URL, robots, sitemap, deployment.
- Traffic: GA4 and GSC availability, clicks, impressions, CTR, position.
- Wins: pages and queries worth preserving.
- Risks: drops, indexing gaps, suspicious traffic, uncertain SERP changes.
- Actions: top 3 tasks and blocked items.
- Issues: no more than 3 issue drafts per day.

## Weekly Output
- Search Console growth review.
- Completed action review.
- Top query clusters.
- Content refresh queue.
- Internal link queue.
- Template/tool opportunities.
- Up to 5 priorities for the next week.

## Monthly Output
- Opportunity reprioritization.
- Kill/update/build list.
- Monetization-readiness review.
- Content quality and policy review.

## Safety Rules
- No fake pageviews.
- No ad clicks.
- No live ad tests.
- No guaranteed rankings, AdSense approval, revenue, or AI Overview placement.
- No unreviewed publishing.
- Mark uncertain findings as hypotheses.

Connection Timeline

Phase	Status	Requirement	Hermes use
Now	Ready	Public URL, sitemap, robots, build, deployment, and repo checks.	Daily health note, backlog triage, issue drafts, and safe PR suggestions.
After GA4 + GSC	Blocked by setup	GA4 measurement ID in Vercel, Search Console domain verification, submitted sitemap.	Daily analytics availability, early indexing notes, and tracking gap reports.
After 7-14 days of data	Needs data	Comparable Search Console and GA4 windows with enough signal.	Weekly growth review, low CTR queue, striking-distance queue, and issue planning.
After AdSense approval	Future	Real AdSense reporting and a cautious invalid-traffic workflow.	RPM movement review, suspicious traffic triage, and evidence preservation.

Required Inputs

Production URLs

Owner: Public

Timing: Now

Health checks, sitemap verification, and availability reports.

Vercel deployments

Owner: Project owner

Timing: Now or after GitHub connection

Deploy status, failed build review, and release notes.

Google Analytics 4

Owner: Project owner

Timing: After measurement ID is set

Traffic availability, page engagement, source quality, and event checks.

Google Search Console

Owner: Project owner

Timing: After domain verification

Indexing, clicks, impressions, CTR, position, and query opportunity reports.

AdSense

Owner: Project owner

Timing: After approval

RPM movement and traffic-quality review. Never ad-click testing.

Phase 0 Command

RedBit includes a no-credential health script for Hermes Phase 0. It checks public URLs, robots, sitemap coverage, and critical routes with server-side HTTP requests only.

pnpm siteops:health
pnpm siteops:health:json
node scripts/siteops-health.mjs --base http://localhost:3001
node scripts/siteops-health.mjs --json --all-sitemap-urls
node scripts/siteops-health.mjs --base http://localhost:3001 --concurrency 2

Related Resources

Start with the Hermes SEO Agent Prompt Pack, generate a daily note with the Search Console Daily Report Generator, and choose an export route with the GSC Export Planner.

FAQ

When can Hermes start monitoring RedBit?

Hermes can start Phase 0 monitoring now with public URL, robots, sitemap, build, deployment, and repo checks. Traffic and search reporting starts after GA4 and Search Console are verified.

When will Hermes reports become useful for SEO decisions?

Meaningful SEO optimization usually needs at least 7 to 14 days of Search Console and GA4 data. Before that, reports should focus on setup, indexing, and obvious technical issues.

Can Hermes monitor AdSense now?

No. AdSense-specific monitoring should wait until the site is approved and real reports exist. Even then, Hermes must not click ads, test ads, or create traffic.

Should Hermes create issues and PRs automatically?

It can draft up to a few focused issues and low-risk PRs, but publishing, metadata changes, monetization changes, and content changes should require human review.

Last updated: May 19, 2026.