Technical SEO portfolio module

SEO Audit Bench

A public audit surface that shows how AI Growth Bench is checked for crawlability, indexability, sitemap health, structured data, security headers, links, and performance risk.

Module status

Live baseline, no paid API required

This module is designed for remote SEO work where a client needs clear technical findings, visible evidence, and a prioritized repair path rather than a vague audit checklist.

Technical SEO

87

Codex SEO score after canonical, sitemap, and header fixes.

Sitemap

100

All sitemap URLs return 200 and match self-canonical pages.

Links checked

52

Last confirmed Linkinator crawl returned all 200-status links.

Open issues

1

CWV still needs real lab or field data; webmaster dashboards remain pending.

Workflow

  1. 01Run technical crawl and sitemap checks.
  2. 02Separate confirmed defects from heuristic warnings.
  3. 03Fix crawl/index blockers first: canonicals, sitemap status, noindex, redirects, and security headers.
  4. 04Re-run checks and record score deltas.
  5. 05Move unresolved items into a next-test queue instead of hiding them.

Client-ready deliverables

  • Technical SEO issue table with priority and evidence.
  • Sitemap and canonical validation summary.
  • Security header baseline.
  • Broken-link crawl result.
  • Residual risk list for CWV, IndexNow, and API-backed checks.

Current evidence

  • Codex SEO technical score improved from 79 to 87.
  • Sitemap score improved from 73 to 100.
  • Canonical mismatch count dropped to 0.
  • Deprecated sitemap priority/changefreq tags were removed.
  • CSP, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy are live.
  • IndexNow, RSS/Atom feeds, and text sitemap are part of the discovery layer.

Next moves I can do without API access

  • Add a before/after audit table to the weekly report.
  • Run Linkinator before every deploy.
  • Run Unlighthouse locally when the machine can complete a browser crawl.
  • Use the IndexNow submit script after publishing new pages.

Requires API, login, or paid data later

  • PageSpeed Insights API key for repeatable Lighthouse/PageSpeed evidence.
  • Google Search Console property access for index coverage and query data.
  • CrUX field data is only useful after the site has enough real-user traffic.

Portfolio proof path

This module feeds the weekly report.

New evidence from this module should be summarized in Reports and added to Evidence Log before it is treated as a portfolio claim.