Status: production. The Search Console / GA4 pull is the supported product. The gaps below are still real and are listed here rather than left for someone to discover from a surprising report.
Search Console's URL Inspection API would tell you what Google actually indexed for a page, which is a different and stronger fact than what the page says about itself. It is not wired up. Its per-URL quota is low enough that it needs a sampling strategy rather than a naive loop, which is why it has not landed yet.
The Chromium collect intercept (observeEvents / ANALYTICS_OBSERVE) is
opt-in and off by default. The hosted portal does not turn it on. Installing
Playwright yourself is required if you want the probe locally.
Installation is currently from a git tag:
npm install github:pendulumdev/pend-audit-analytics#v0.3.0Distribution is git tags and GitHub Releases. Consumers should pin an
annotated tag rather than track a branch. Publishing to npm under the
@pendulumdev scope is not scheduled.
Treat these as public API. Changing any of them is a breaking change:
- The
--outJSON shape, exported asAuditRunfrom@pendulumdev/analytics/types audit-config-analytics.tomlkey names- The PageSpeed screenshot path scheme under
dirname(--out)/psi-shots/ - Everything re-exported from
src/index.ts
Anything not re-exported from src/index.ts is internal and may change in a
patch release.
pend-analytics mcp (stdio) and pend-analytics mcp --http (loopback
Streamable HTTP) expose docs, config validate, projected
analytics_audit_run, and run_summarize. See SKILL.md. Public
hosted HTTP is out of scope for this CLI.
- A readiness score. Traffic evidence is not a rating. The zeros in
run.scoreare intentional. - Ranking prediction. Nothing in a GSC/GA4 pull predicts search position.
- A report UI.
out/analytics.jsonis the interface. Presentation belongs to whatever consumes it. - Paid SERP, backlink, or keyword APIs. Off-page data products stay out of this engine.