URL Audit

A URL audit is a full 6-category analysis of a single publicly accessible web page. It is the most detailed audit type and the best starting point for improving any specific page.

When to use

• Auditing a specific landing page, blog post, or product page
• Checking a page after a content update or redesign
• Diagnosing a ranking drop on a high-value page
• Benchmarking a page before and after an optimization sprint

How to run

1. Open Run audit

   From any project page, click Run audit (top right).

2. Select URL

   Choose URL from the audit type options.

3. Enter the target URL

   Paste the full URL including https://. The page must be publicly reachable without authentication.

4. Submit

   Click Start audit. The audit enters the queue immediately.

What it measures

The URL audit runs these tools in sequence:

1. Google PageSpeed Insights API — Lighthouse Performance, SEO, Best Practices, and Accessibility scores via PSI. Results reflect real-world Chrome UX data where available.
2. Custom SEO tool — 12-field rubric (title, meta description, h1, OG tags, Twitter card, robots, sitemap reference, JSON-LD, charset, lang, canonical, viewport).
3. GEO tools — meta tags, structured data, headings, resources, robots.txt, sitemap, GEO-specific lint rules, content depth analysis.
4. Content quality tool — Flesch-Kincaid readability, passive voice ratio, keyword density, duplicate content detection, HTML-to-text ratio.

What it returns

A completed URL audit gives you:

• Overall score — weighted average across all 6 categories
• Category scores — each out of 100 with a pass/fail/needs-improvement rating
• Metric breakdown — per-metric values with good/needs-improvement/poor thresholds
• Recommendations — prioritized list of specific fixes, each with severity, effort, and a GEO strategy tag
• Rewrite suggestions — AI-generated improvements to title, meta, headings, structured data, and body copy

Processing time

Limits

• The target URL must respond to an unauthenticated GET request
• Max page size for content analysis: ~500 KB HTML
• JavaScript-rendered content is captured via PSI (uses a real Chrome instance)
• Internal pages behind a login wall cannot be audited with the URL type