Fix GSC CTR surfaces and sitemap cleanup

[matt-dean-git]

Summary

Fix the GSC finding that SatGate is indexed but leaking clicks by tightening the highest-impression SERP surfaces and cleaning sitemap/robots noise.

• Rewrite /blog/how-to-add-budget-limits-to-openai-api-calls title/meta/H1/direct answer for OpenAI API budget limits CTR, add HowTo structured data, and soften unverifiable spend claims.
• Rewrite /govern title/meta/H1/direct answer around AI Agent Governance: Policy-to-Proof Controls.
• Remove /crawl, /dashboard, and /monetize from sitemap and align robots.txt to only disallow /playground.
• Refresh SEO reports and clean static SEO audit debt that was blocking seo:links.
• Update the static link audit to skip redirect-only pages for canonical/sitemap checks.

Verification

• git diff --check
• python3 -m py_compile scripts/internal_link_audit.py scripts/seo_machine.py
• python3 scripts/seo_machine.py --check
• npm run seo:links
• focused ESLint on all changed TS/TSX files
• npm run build
• local rendered checks on:
  • /blog/how-to-add-budget-limits-to-openai-api-calls
  • /govern
  • /robots.txt
  • /sitemap.xml

Rendered verification confirmed:

• Budget page title: OpenAI API Budget Limits: Prevent Runaway GPT Spend | SatGate
• Budget page description includes request-path blocking/downgrading/routing + Evidence Pack receipts
• /govern title: AI Agent Governance: Policy-to-Proof Controls | SatGate
• /robots.txt only disallows /playground
• /sitemap.xml excludes /crawl, /dashboard, /monetize, and /playground

Notes

Full-site npm run lint still has pre-existing failures outside this PR's touched scope; focused lint on changed files passed with one pre-existing unused import warning in stripe-link-agents-vs-satgate.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
satgate	Ready	Preview, Comment	Jun 10, 2026 4:55am