Site-Wide Sweep
Find every weak page across your entire site — before AI crawlers do.
While URL Analysis audits a single page in depth, the Site-Wide Sweep scans your entire indexed site at once — using signals already collected at ingestion time — to find every thin, slow, or structurally weak page dragging down your GEO performance.
What It Does
- Reads quality signals collected automatically for every page when your site was crawled — no additional HTTP requests, no AI tokens consumed during the sweep
- Computes a quickScore (0–100) for each page from 9 programmatic signals: meta title, meta description, structured data, word count, H1 presence, H2 structure, internal links, token budget, and page speed
- Surfaces a geoScore (0–100) per page — an AI-assessed content quality score evaluated at ingest time, measuring how clear, authoritative, and citable the page content is
- Identifies the bottom 20% weakest pages (minimum 10, maximum 100) for priority attention
- Builds an issue frequency table showing which problems affect the most pages across your site
- Generates 5 plain-English priority actions — the specific fixes that would improve the most pages at once
- Supports excludeUrls — exclude blog archives, pagination, and category pages from the sweep
How to Generate a Report
🛠️ Step 1: Navigate to Site-Wide Sweep
From the ai12z GEO portal, select Site-Wide Sweep from the navigation menu.
🛠️ Step 2: Click + Generate Report
Click the + Generate Report button in the top-right corner.
🛠️ Step 3: Configure the Sweep
| Field | Description |
|---|---|
| Exclude URLs | Comma-delimited URL substrings to exclude (e.g. /news/,/category/,/tag/) |
Your site must have been crawled and indexed by ai12z at least once before running a sweep.
🛠️ Step 4: Submit and Wait
Click Submit Job. The sweep reads MongoDB directly and completes in seconds regardless of site size. Click Refresh to check for completion.
🛠️ Step 5: View Your Report
Once complete, click View PDF for the full site health report.
The Two-Score System
Each indexed page carries two complementary scores that together give richer triage than either alone:
| Score | Type | What It Measures |
|---|---|---|
| quickScore | Programmatic (no AI) | Structural signals: meta tags, headings, word count, internal links, schema, token budget, page speed |
| geoScore | AI-assessed (gpt-4.1-nano at ingest time) | Content quality: clarity, authority, and AI citeability of the page content |
A page can score well on structure but have thin, vague content (high quickScore, low geoScore), or have rich content behind weak metadata (low quickScore, high geoScore).
quickScore Methodology
| Signal | Points | Threshold |
|---|---|---|
| Meta title present | 15 | Title tag exists and is non-empty |
| Meta description present | 15 | Description tag exists and is non-empty |
| Structured data (JSON-LD) | 10 | At least one schema type detected |
| Word count | 10 | ≥ 300 words |
| H1 present | 10 | At least one H1 tag |
| H2 structure | 10 | Two or more H2s |
| Internal links | 10 | Three or more internal links |
| Token budget | 10 | Content fits within AI agent context window |
| Page speed rating | 10 | Rated fast (< 1 second) at ingestion time |
PDF Report Sections
| Section | Contents |
|---|---|
| Site Health Scorecard | Total pages indexed, average quickScore, score distribution (Excellent/Good/Fair/Poor/Critical), signal coverage metrics, and Avg Content GEO card |
| Issue Frequency | Each issue type ranked by number of pages affected |
| Priority Actions | 5 plain-English actions targeting the most common issues first |
| Pages Needing Attention | Ranked table of weakest pages with quickScore badge, GEO score badge (color-coded), URL, speed rating, and issue tags |
Cost & Speed
- ~$0 AI cost to run — the sweep job consumes no AI tokens; all scoring is programmatic reads from MongoDB
- geoScore ingest cost — ~$0.00003/page (scored asynchronously at crawl time); 1,000 pages ≈ $0.03
- Seconds to run — reads MongoDB directly, not the web
- Re-runnable at zero cost — regenerate as often as needed after content fixes
Key Outputs
- Site Health Scorecard — Total pages, average quickScore, score distribution bands, per-signal coverage rates, and Avg Content GEO
- Issue Frequency Table — Each issue type ranked by pages affected
- 5 Priority Actions — Plain-English recommendations targeting the highest-impact improvements first
- Weakest Pages Table — Bottom 20% of pages with quickScore badge, geoScore badge, speed rating, and issue tags
- PDF Report — Downloadable site health document
Perfect For
- Content managers who need to know which pages to fix first — site-wide, not one at a time
- Developers auditing a newly indexed site before launch
- SEO specialists who need a fast triage pass before running deep URL Analysis on priority pages
- Marketing teams doing quarterly content audits across large sites
Example Use Case
A B2B software company has 340 pages indexed in ai12z. They run a Site-Wide Sweep with excludeUrls=/blog/category/,/tag/. The Scorecard shows an average quickScore of 54 — Fair. The Issue Frequency table reveals that 210 pages are missing a meta description and 180 pages have fewer than 3 internal links. The Priority Actions section calls out: (1) add meta descriptions site-wide, (2) add internal links to top-of-funnel pages, (3) add H2 structure to 95 thin pages. Within 6 weeks, the average quickScore rises to 71.