Vaidya — Page-Level Audit
AS is a domain-level score. It tells the practitioner where the domain’s readiness is deficient at the pillar and vector level, but it averages across pages — a low chunk-extractability score may reflect three poorly structured pages dragging the average down, not a site-wide structural problem. Vaidya produces the page-level view that makes the domain-level finding actionable.
How it differs from AS and pAS
AS runs across the domain, averaging signals from the homepage and sampled subpages. It is the strategic diagnostic: where should the engagement focus?
pAS runs all 36 Datapoints against a single specified URL. It is the tactical diagnostic for one page already identified as significant.
Vaidya audits many pages at once — the full sitemap, or a curated list — and produces per-page severity ratings. It is the audit tool: which pages have which problems, at what severity, and how many are affected?
Audit modes
- Sitemap — Vaidya crawls the sitemap and audits every page discovered
- Sitemap Plus — sitemap crawl with extended discovery of pages not formally in the sitemap
- Manual List — practitioner provides specific URLs (useful for targeting known problem areas)
- Plugin — WordPress or CMS integration that uploads page data without requiring external crawling
Severity ratings
Each finding is rated Critical, High, Medium, or Low. Critical findings — missing entity schema on the homepage, AI crawler access blocked, no canonical declarations — are the structural problems that constrain AS regardless of what other work is done. High findings are meaningful deficits that should be addressed in the next sprint. Medium and Low findings are improvement opportunities that improve the margin but are not blockers.
When to use Vaidya
Vaidya is most useful at engagement start (to understand the page-level distribution of Optimize and Manifest problems before action selection) and after Optimize-pillar work (to verify that fixes deployed correctly across the site and no pages were missed).