# Technical SEO audit. Built for crypto and Web3 sites. The technical SEO foundation of every Crawlux audit. Validates Core Web Vitals, crawlability, indexation, robots.txt and SPA rendering, calibrated for React, Vue and Next.js Web3 frontends with wallet integrations and chain-aware routing. Free first audit, no signup. ## Three layers of technical health Technical SEO breaks down into three things that determine whether your site can be crawled, rendered and ranked. Crawlux checks all three on every audit. ### Crawlability and indexation Can search engines reach every page that should rank? We audit robots.txt, meta robots, canonicals, hreflang and XML sitemap structure. Crypto sites often misconfigure subroutes per chain, which breaks crawl budget without anyone noticing. ### SPA rendering and JavaScript SEO Most Web3 frontends are React, Vue or Next.js single-page apps. Crawlux runs a headless Chrome browser to render JavaScript before crawling, then flags hydration mismatches, RPC failures and lazy routes that fail to render for Googlebot. ### Core Web Vitals LCP, CLS and INP are direct ranking signals. Crawlux measures all three on mobile and desktop, then explains the actual root cause: hero image not preloaded, layout shift from late-loading wallet button, INP blocked by RPC call on connect. ## Eight checks every domain runs through Each check produces a prioritized fix in the PDF report. Severity ratings tell you what to ship first. 01 ### Core Web Vitals LCP, CLS and INP measured on mobile and desktop. Each fix names the specific resource: hero image, late wallet button, blocking RPC call. LCP < 2.5s · CLS < 0.1 · INP < 200ms 02 ### SPA rendering audit Headless Chrome renders React, Vue and Next.js sites before crawl. Flags hydration mismatches, RPC failures and lazy routes that fail in Googlebot. 03 ### Crawlability robots.txt parsed line by line. Each Allow / Disallow tested. AI bot rules (GPTBot, ClaudeBot, PerplexityBot) checked against your AEO strategy. 04 ### Indexation status Every URL on the domain checked for index/noindex, canonical conflicts and orphan pages. Crypto subroutes per chain frequently break here. 05 ### Canonical & hreflang Self-referencing canonicals validated. Hreflang clusters checked for symmetry. Cross-chain URL duplication flagged with a recommended canonical strategy. 06 ### XML sitemap Discovers sitemap from robots.txt or /sitemap.xml. Validates URL formatting, lastmod dates and that listed URLs return 200 + index. 07 ### Mobile-friendliness Viewport meta, tap target size, text readability and mobile Core Web Vitals. Many wallet-modal designs break tap targets without anyone noticing. 08 ### Internal linking Maps the link graph. Flags orphan pages, deep-buried important URLs and pages that pass equity to dead-end paths. All 8 checks run on your domain in **under 60 seconds**. Combined with 7 other audit modules. ## Why a one-page tool is not a domain audit Lighthouse and PageSpeed Insights audit one URL at a time. Crawlux audits the entire domain plus the SPA rendering quirks specific to crypto frontends. ### What a one-page tool gives you - Audits one URL at a time, not the whole domain - No site-wide canonical or hreflang validation - No XML sitemap discovery or validation - No orphan page or click-depth analysis - Generic guidance, not crypto-aware - Does not check schema or AEO at all ### What a domain-level audit gives you - Full domain crawl with site-wide checks - Canonical, hreflang and indexation graph validated - XML sitemap discovered and validated against crawl - Orphan pages and click-depth issues flagged - SPA rendering audit calibrated for Web3 frontends - White-label PDF report for dev handoff ## Four phases, all in parallel The technical SEO module runs alongside the seven other audit modules. Total audit time is typically under 60 seconds. 1. ### Crawl + render Headless Chrome opens the domain, fetches robots.txt and sitemap, then crawls every internal link. JavaScript renders fully before content is captured, so React, Vue and Next.js sites are audited as Googlebot would see them. 2. ### Core Web Vitals measurement LCP, CLS and INP measured on simulated mobile (4G, mid-tier device) and desktop. Each metric is broken down by root cause: late hero image, layout shift from wallet button, INP blocked by RPC call on connect. 3. ### Indexation graph Every URL classified by index status, canonical target and crawl reachability. Orphan pages and click depth issues surface here. Cross-chain duplicate URLs flagged for canonical strategy. 4. ### PDF report assembly Findings prioritized by severity (high / medium / low) and effort (5min / 1hr / dev required). The PDF includes file paths, code snippets and root-cause explanations so the dev team can ship without a translation step. ## Technical SEO questions, answered Common questions from teams running Crawlux's technical SEO module on crypto and Web3 sites. What does Crawlux's Technical SEO audit check?+ The Technical SEO module checks Core Web Vitals (LCP, CLS, INP), crawlability via robots.txt and meta robots, indexation status, XML sitemap discovery, canonical configuration, hreflang setup, mobile-friendliness, SPA pre-render quality and internal linking patterns. Each check produces a prioritized fix in the PDF report. Does Crawlux audit Single Page Applications (React, Vue, Next.js)?+ Yes. Crawlux runs a headless Chrome browser to render JavaScript before crawling, so React, Vue, Next.js and Nuxt sites are audited as Googlebot would see them. Most crypto and Web3 sites use SPA frameworks, so this matters disproportionately. The module flags hydration mismatches, lazy-loaded routes that fail to render and JavaScript errors that block indexation. How long does a technical SEO audit take?+ Most domains complete in under 60 seconds. Larger sites with more than 1,000 pages may take 90-120 seconds. The audit runs in parallel: crawl, render, schema check and Core Web Vitals measurement happen simultaneously.