Direct answer
A useful audit does not end when the crawler finishes. After the scan you still need discovery (structured facts), diagnosis (grouped meaning), a blueprint (prioritized page actions), and a re-audit (validation). That sequence keeps SEO Health, SEO Growth, GEO Health, and GEO Growth as independent capabilities — never one blended overall score.
Health findings tell you whether foundations are usable. Growth findings tell you what demand is still unanswered. The blueprint should say which job each action serves, with a clear check after publish.
The process
- Discover — Walk pages, structure, topics, entities, questions, and evidence. Record sample URLs and concrete observations, not a vibe score.
- Diagnose — Group issues by rule and severity. Separate crawl/index blockers from coverage gaps, and separate unclear entities from unanswered questions. Keep the four capabilities labeled.
- Blueprint — Convert groups into page-level actions: target path, suggested changes (definition, use case, specs, evidence, FAQ), priority, and a validation step such as re-audit.
- Re-audit — After changes ship, scan again. Confirm what improved, what remains, and what new opportunities appeared. Progress is checked against the same independent lenses.
Discovery without diagnosis leaves teams with noise. Diagnosis without a blueprint leaves teams with stories. A blueprint without re-audit leaves teams guessing. The loop is the product of the audit, not a decorative report cover.
Example
Discovery might flag a product URL with a thin template, missing use case, and no FAQ — alongside a separate health note about orphaned documentation pages. Diagnosis puts the orphan under SEO Health (discovery path) and the thin product under SEO Growth / GEO Growth (coverage and answerability), without averaging them.
A blueprint action could look like: expand /products/example/ with a product definition, use case, specifications, evidence, and FAQ; priority P1; validate with re-audit. A second action reconnects the orphan docs into the hub. Each action states its job. Neither claims a ranking or citation outcome.
When the team publishes, re-audit checks whether the product page now answers the intended questions and whether the docs are reachable. Health and growth panels update independently — a healthier link graph does not invent finished topic coverage by itself.
FAQ
What should happen after a website scan?
Do not stop at a list of findings. Move through discovery (facts with sample URLs), diagnosis (group by rule, severity, and opportunity), blueprint (page-level actions with priority and validation), and re-audit after changes ship. That loop turns observations into work you can execute and check.
Why is a single overall score a poor ending for an audit?
SEO Health, SEO Growth, GEO Health, and GEO Growth answer different questions. Blending them hides whether you need crawl fixes, coverage work, clearer entities, or new answers. A blueprint should keep those tracks visible so teams know which job each action serves.
Does a blueprint automatically change my live site?
No. A blueprint is guidance: target URL, suggested changes, priority, and a re-audit check. Your team decides what to publish. The value is a sequenced plan grounded in diagnosed findings — not auto-editing or ranking promises.
Sources
- Mika Visibility process: Audit → Diagnosis → Blueprint → re-audit — mikaovo.ai
- Google Search Central — debugging crawl and indexing issues with evidence from the live site (public documentation)
- People-first content guidance: prioritize clear improvements on real pages over opaque composite scores
Blueprint guidance does not auto-publish changes and does not guarantee rankings or answer-surface placement.