SEO Change Impact Monitoring

Use for SEO work when Codex should measure SEO release impact with pre/post baselines, annotations, crawl checks, and rollback criteria.

srednoff888-art c3ee8ce 2 files · 1.5 KB Updated 1 repo stars

File contents

seo change impact monitoring

Workflow

  1. Confirm the business outcome, owner, source data, constraints, and success metric.
  2. Inspect the project and available account or analytics evidence before proposing changes.
  3. Use official documentation for current platform behavior and retain source provenance.
  4. Produce an evidence-backed plan with assumptions, dependencies, and measurable validation.
  5. Run only read-only diagnostics by default; gate external, paid, production, or publishing actions behind explicit approval.

Domain Focus

measure SEO release impact with pre/post baselines, annotations, crawl checks, and rollback criteria.

Official Sources

https://developers.google.com/search/docs | https://schema.org/docs/gs.html

Guardrails

  • Capture baselines before making recommendations that affect crawl, indexation, or traffic.
  • Do not delete pages, publish redirects, change robots, or alter canonicals without explicit approval.
  • Separate observed evidence from inferred search-impact estimates.

srednoff888-art/srednoff-os/tree/main/.codex/skills/seo-change-impact-monitoring commit c3ee8cebad

Frequently asked questions

npx skillmds add srednoff888-art/seo-change-impact-monitoring