SEO Monitoring Playbook

Review indexing status, sitemap fetch state, and newly discovered pages.

Escalation: If valid pages are excluded unexpectedly, inspect canonical tags, robots rules, and sitemap URLs.

Track early impressions for Roth Conversion Calculator, Roth IRA Conversion Calculator, and long-tail pages.

Escalation: If impressions appear but CTR is weak, review title and meta description clarity.

Verify privacy-safe calculator events and page views without sending exact financial inputs.

Escalation: If events disappear, check NEXT_PUBLIC_GA_MEASUREMENT_ID and production consent/privacy settings.

Open /api/health and review production status, feature counts, and tax-year metadata.

Escalation: If the endpoint fails, inspect Vercel deployment status and recent release notes.

Run production Lighthouse/PageSpeed checks for homepage, calculator hubs, and content hubs.

Escalation: If LCP, INP, or CLS regresses, review recent UI modules and bundle changes.

Compare submitted sitemap URLs with indexed URLs and inspect important missing routes.

Escalation: If route groups are missing, confirm static generation, internal links, and canonical metadata.

Check that site-index, blog, glossary, state, and tax-reference pages link users back to the calculator.

Escalation: If a cluster is isolated, add a contextual link from a hub page rather than modifying the calculator core.

Add or update educational pages based on GSC query data and user questions.

Escalation: If a topic touches personal tax decisions, keep content educational and route users to professional review.

Group performance by calculators, blog, glossary, states, tax brackets, basis, and operations pages.

Escalation: If a cluster underperforms, improve hub copy, internal links, and metadata before creating new features.

Review crawl requests, response codes, and large changes in crawl behavior.

Escalation: If crawl errors spike, compare against recent release notes and Vercel logs.

Check dependencies, tax-year labels, methodology notes, and IRS update windows.

Escalation: If tax rules change, route work through a reviewed tax-data update rather than a small content-only release.

Compare the incident time with the latest deployment and feature registry entry.

Escalation: If a new module caused the issue, disable or roll back that module before changing unrelated code.

Pause tax-sensitive copy edits until compliance language and source assumptions are reviewed.

Escalation: If AI or calculator pages are involved, verify disclaimer visibility and no-advice boundaries first.

Record affected URLs, symptoms, action taken, rollback path, and verification output.

Escalation: If the same class of incident repeats, convert the finding into a regression test or launch checklist item.