GEOHub Website Diagnosis

Workflow

1. Read references/site-diagnosis-method.md, references/crawler-policy.md, and references/scoring-policy.md.
2. Extract the single public URL. Ask only for the URL when it is missing.
3. Run python3 scripts/run_site_diagnose.py --url <URL> --output <runs-root> --locale <locale> --max-pages 10 --render auto.
4. Inspect quality-report.json, diagnostic confidence, source gaps, and limitations before presenting scores.
5. Validate the report against references/report-module-contract.md and references/report-design-system.md.
6. Deliver the complete Artifact Bus run directory and open report.html for the user.

Output contract

Return a bounded run containing source snapshots, crawl and sampling manifests, structured site and page diagnoses, evidence ledger, remediation backlog, quality and lineage artifacts, and one offline report.html. Read references/report-contract.md for the file contract and report format boundary.

The offline report runtime is packaged under assets/. Governed trigger and output cases are stored under evals/.

Boundaries

Fetch only public HTTP(S) resources on the approved canonical host. Discovery is bounded to 500 inventory URLs, five sitemaps, ten representative pages, 15 MB, and 90 seconds. Preserve blocked or unavailable pages as source_gap. Scores describe observed readiness signals and never claim live AI ranking, recall, citations, traffic, or business effects.

Do not use this Skill for single-page diagnosis, brand-only diagnosis, authenticated sources, live citation measurement, or website modification.