The 23-page PDF audit report. White-label, agency-ready.

The deliverable that ties every Crawlux audit together. A 23-page PDF drawn from 80+ checks across 8 audit modules, with prioritized fixes, copy-paste code snippets and a 30-60-90 day roadmap. Free tier keeps Crawlux branding; Pro and Team tiers ship white-label with your logo.

By the numbers

23 pages typical for a Pro or Team tier audit on a domain with 50-500 pages. Cover, executive summary, prioritized findings, 8 module deep-dives, competitor benchmark, AEO citation report, 30-60-90 roadmap.

80+ individual checks feed the report, drawn from 23 specialized analyzers across 8 modules. Every finding traces back to a named analyzer.

~6s to generate the PDF once all 8 modules complete. Rendered server-side with Puppeteer using a real HTML/CSS template; no font subsetting issues, no Unicode loss.

A representative pair of pages from the 23-page report

Executive summary on the left, a finding deep-dive on the right. The actual report carries your logo on Pro and Team tiers.

Executive summary

example-protocol.com · DeFi Lending · Audited Apr 26, 2026

Overall score

62 / 100

Position

07 in top 20

High-priority findings

19

Finding 04 · High severity

Module 04 · Token Schema · 14 lending market pages affected

FinancialProduct schema missing on lending pages.

All 14 lending market pages are missing FinancialProduct JSON-LD. Only generic WebPage schema is present, which means search engines and AI models cannot identify the page as a lending product.

Severity & effort

• Severity: High
• Effort: ~1 hr
• Pages affected: 14

Recommended fix

Add FinancialProduct JSON-LD per market page using the DeFi Lending pattern. Pull interestRate dynamically from your rate oracle. Reference the protocol Organization via @id rather than inlining.

{
  "@type": "FinancialProduct",
  "name": "USDC Lending Market",
  "interestRate": { ... }
}

What is inside

The 23 pages, section by section

Every report follows this structure. Page counts approximate; longer for sites with more findings.

• PG 01 - Cover & brand: 1 page
• PG 02-03 - Executive summary: 2 pages
• PG 04-07 - Prioritized findings: 4 pages
• PG 08-09 - Technical SEO deep-dive: 2 pages
• PG 10-11 - YMYL & E-E-A-T deep-dive: 2 pages
• PG 12-13 - AI Visibility (AEO) deep-dive: 2 pages
• PG 14-15 - Token Schema deep-dive: 2 pages
• PG 16 - Keyword Intent deep-dive: 1 page
• PG 17 - Backlink Toxicity deep-dive: 1 page
• PG 18-20 - Competitor benchmark: 3 pages
• PG 21-22 - AEO citation report: 2 pages
• PG 23 - 30-60-90 day roadmap: 1 page

From audit data to PDF in ~6 seconds

1. Findings ingestion: All 8 audit modules emit findings in a normalized format: severity, effort, affected URLs, recommended fix, optional code snippet.
2. Prioritization: Findings are sorted by a weighted closeability formula.
3. Template render: The HTML template renders with the audit data bound to React components server-side.
4. Puppeteer print-to-PDF: A headless Chrome instance loads the rendered HTML and outputs PDF at 8.5 x 11 inches.

Crawlux PDF vs generic SEO tool exports

PDF report FAQ

What is in the PDF audit report?

The PDF is 23 pages covering an executive summary with overall and per-module scores, a prioritized findings list (high to low severity), per-module deep-dive sections, code snippets ready to copy for technical fixes, the competitor benchmark, AEO citation report, and the recommended 30-60-90 day fix roadmap.