Production URLs
Owner: Public
Timing: Now
Health checks, sitemap verification, and availability reports.
Agent operations template
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 reporting only after approval. Hermes can prepare readiness packets before approval, but owner authorization is required for Google account and monetization actions.
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
## Operating Loop
- Monitor public health, sitemap coverage, analytics availability, and repo changes.
- Research demand from Reddit, Search Console queries, GA4 landing pages, and official docs.
- Convert demand into a small backlog of guides, tools, templates, internal links, or documentation updates.
- Draft issues with evidence, expected impact, policy risk, and acceptance criteria.
- Ask the owner to approve production deploys, Google account actions, monetization changes, and compliance-sensitive copy.
- Verify with lint, typecheck, build, sitemap checks, and safe analytics events.
- Report what changed, what moved, what is blocked, and what needs authorization.
## 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.
- Draft AdSense readiness packets, but do not add ad code without owner approval.
## 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.
- Do not automate ad layout or monetization changes.
## 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.
- Owner authorization is required for production deploys, Google account changes, AdSense code, ads.txt publisher IDs, affiliate links, and sponsor copy.| 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 | Ready for snapshots | GA4 measurement ID in Vercel, Search Console domain verification, submitted sitemap. | Daily analytics availability, early indexing notes, tracking gap reports, and AdSense readiness packets. |
| 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. |
Owner: Public
Timing: Now
Health checks, sitemap verification, and availability reports.
Owner: Project owner
Timing: Now or after GitHub connection
Deploy status, failed build review, and release notes.
Owner: Project owner
Timing: After measurement ID is set
Traffic availability, page engagement, source quality, and event checks.
Owner: Project owner
Timing: After domain verification
Indexing, clicks, impressions, CTR, position, and query opportunity reports.
Owner: Project owner
Timing: Review prep after site readiness; reporting only after approval
Approval packet, ads.txt/code checklist, RPM movement, and traffic-quality review. Never ad-click testing.
Owner: Public + owner review
Timing: Weekly
Find operator pain, map it to RedBit pages, and avoid spammy community posting.
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 2Hermes can monitor, research, summarize, draft issues, and prepare low-risk recommendations continuously. The owner should approve production deploys, Google account changes, AdSense code, ads.txt publisher IDs, affiliate links, sponsor copy, redirects, and compliance-sensitive public claims.
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.
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.
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.
Hermes can prepare an AdSense readiness packet now, but AdSense reporting should wait until the site is approved and real reports exist. Hermes must not click ads, test ads, or create traffic.
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.
The site owner should approve production deploys, Google account changes, AdSense connection steps, ads.txt publisher IDs, affiliate links, sponsor copy, and any compliance-sensitive public claim.
Last updated: May 22, 2026.