The Site Analyzer is the audit you reach for when you already suspect a problem in this dimension and need a fast, copy-paste-able fix list. It reuses the same chrome as every other jwatte.com tool — deep-links from the mega analyzers, AI-prompt export, CSV/PDF/HTML download — but the checks it runs are narrow and specific.
Your compelling page description in 150-160 characters that summarizes the page content and encourages clicks.
Why this dimension matters
Orchestrator tools are how most audits actually begin — run the meta-audit, get the overall shape of the site's problems, then drill into the specific dimension-level tools the orchestrator flags. Running only specialist tools without an orchestrator pass first is how teams end up fixing the wrong thing: a performance-focused team optimizes images while the real regression is a canonical-to-404 bleed in the sitemap. The orchestrator catches the cross-dimension interactions that specialist tools miss.
Common failure patterns
- Treating the overall score as the signal — the overall number is a directional heuristic. Two sites scoring 72 can have wildly different profiles (one strong-SEO weak-schema, one strong-schema weak-security). The per-dimension breakdown is the useful signal; the overall number is useful only for trending across audits of the same site.
- Skipping the deeper-dive pass — the orchestrator surfaces that a dimension is weak. The specialist tool surfaces what specifically is wrong. Both are needed; the orchestrator alone produces "performance is low" level diagnoses, which isn't actionable.
- Running once and not trending — orchestrators shine when you run them every 30–90 days and watch which dimensions move. A single run tells you what's wrong now; a quarter's worth of runs tells you whether the site is improving.
How to fix it at the source
Build an orchestrator cadence: once per site per quarter, or once per major site change. Export the audit to PDF and version-store it so you can compare side-by-side. For any dimension scoring below 70, chain into the specialist tool the orchestrator deep-links to — the orchestrator is the map, the specialist tool is the territory. Then re-run the orchestrator after the fixes to verify the dimension moved and that the fix didn't regress another dimension.
When to run the audit
- After a major site change — redesign, CMS migration, DNS change, hosting platform swap.
- Quarterly as part of routine technical hygiene; the checks are cheap to run repeatedly.
- Before an investor / client review, a PCI scan, a SOC 2 audit, or an accessibility-compliance review.
- When a downstream metric drops (rankings, conversion, AI citations) and you need to rule out this dimension as the cause.
Reading the output
Every finding is severity-classified. The playbook is the same across tools:
- Critical / red: same-week fixes. These block the primary signal and cascade into downstream dimensions.
- Warning / amber: same-month fixes. Drag the score, usually don't block.
- Info / blue: context-only. Often what a PR reviewer would flag but that doesn't block merge.
- Pass / green: confirmation — keep the control in place.
Every audit also emits an "AI fix prompt" — paste into ChatGPT / Claude / Gemini for exact copy-paste code patches tied to your stack.
Related tools
- Mega Analyzer — One URL, every SEO/schema/E-E-A-T/voice/mobile/perf audit in one pass..
- Mega Batch — Mega Analyzer across up to 10 URLs — side-by-side score matrix..
- Mega AEO Analyzer — One URL, 10 AEO probes in one pass: schema, attribution, retrievability, freshness, accessibility, tokenizer, prompt-injection, AI-bot meta, speakable, E-E-A-T.
- Mega GEO Analyzer — One business URL, 10 Local SEO probes in one pass: NAP, LocalBusiness schema, service-area, reviews, hyperlocal, hours, geo, multi-loc, categories, sameAs.
- Mega Security Analyzer — Seven security layers in one scan: TLS, PQC hybrid-KEX, HTTP security headers, DNS email-auth (SPF/DKIM/DMARC/CAA), CSP strictness, MITRE ATT&CK tactic mapping, CWE / OWASP / SANS pattern scan.
Fact-check notes and sources
- Google Search Central: Technical SEO guidelines
- Web.dev: Lighthouse documentation
- Ahrefs + Semrush + Sitebulb: published site-audit methodology guides
- Chrome UX Report: https://developer.chrome.com/docs/crux (for field-vs-lab performance comparison)
This post is informational and not a substitute for professional consulting. Mentions of third-party platforms in the tool itself are nominative fair use. No affiliation is implied.
