Checklist de auditoría SEO Web3: 23 checks que cada sitio de token necesita

Checks de SEO técnico (1 al 6)

Los primeros seis checks cubren fundamentos técnicos. Si cualquiera de estos falla, cada otro módulo de auditoría mide ruido. Arregla estos primero sin importar la prioridad en otra parte.

Check 1: Crawlability for Googlebot. Verify the homepage and at least one page per template returns HTTP 200 to Googlebot. Test with the Search Console URL Inspection tool. Fail mode: Cloudflare bot rules block Googlebot accidentally.

Check 2: Crawlability for AI bots. Test access for GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, Claude-SearchBot, Google-Extended and Applebot-Extended. Use curl with each user-agent. Fail mode: Cloudflare's default bot management blocks AI crawlers as a side effect.

Check 3: Server-side rendering. View the raw HTML in DevTools Network tab. The hero copy and primary CTAs should be present in the raw HTML, not loaded via JS. Fail mode: SPA frameworks ship empty HTML and hydrate later.

Check 4: Core Web Vitals. LCP under 2.5 seconds, INP under 200ms, CLS under 0.1. Test on mobile, not desktop. Fail mode: charting libraries and animation libraries inflate LCP on token pages.

Check 5: Canonical correctness. Every page has a self-referencing canonical or a canonical pointing to the correct preferred URL. Fail mode: copying a site to a new domain leaves canonicals pointing to the old domain.

Check 6: Mapa del sitio freshness. XML sitemap exists, is referenced in robots.txt, contains all indexable URLs and updates within 24 hours of publish. Fail mode: stale sitemaps cause Google to under-index new content.

Checks de validación de schema (7 al 10)

El schema es el fix AEO de mayor apalancamiento. Los checks 7 al 10 capturan los errores de schema que realmente mueven la tasa de citas.

Check 7: FinancialProduct on token pages. Token landing pages use FinancialProduct schema, not Producto. Verify with the Google Rich Resultados Test. Fail mode: framework defaults emit Producto schema everywhere.

Check 8: CryptoExchange on exchange pages. Exchange pages and trading-pair pages use CryptoExchange schema with the listed pairs as Offers. Fail mode: exchanges use Organization schema only and miss the trading-pair extraction.

Check 9: Organization schema with founders. Organization schema includes founder names, foundation date and parent organization where applicable. Critical for E-E-A-T. Fail mode: minimal Organization schema with only name and URL.

Check 10: BreadcrumbList on every page. Every non-home page has BreadcrumbList schema reflecting the actual Migas de pan hierarchy. Fail mode: Migas de pans in HTML but no corresponding schema.

Checks de preparación AEO (11 al 14)

La preparación AEO es el modelo de cuatro factores del framework de citas. Cada check mapea a un factor.

Check 11: Factual density above threshold. Aim for at least 3 named entities, numbers or dates per 100 words across landing pages. Below threshold the content reads as marketing rather than reference. Fail mode: hero sections that are all claims and no facts.

Check 12: AI bot allowlist explicit. robots.txt explicitly allows the seven AI bots. Cloudflare bot rules permit them. Verify with curl using each user-agent. Fail mode: implicit allow that gets overridden by edge bot management.

Check 13: Authority citations present. Landing pages cite at least three external authority sources (audit firms, academic papers, regulatory bodies, established crypto publications). Fail mode: marketing pages with zero outbound citations.

Check 14: Citation rate baseline. Run a 30-prompt baseline test across ChatGPT, Perplexity and Claude. Document the per-LLM and per-intent citation rate. This becomes the metric you optimize against in the next 90 days.

Checks de señales de autoridad (15 al 19)

Las señales de autoridad importan más para crypto que para casi cualquier otra vertical. Los checks 15 al 19 capturan los déficits de confianza YMYL que suprimen tanto los rankings de Google como las citas IA.

Check 15: Author bylines on YMYL pages. Every page involving user funds has a named author with credentials visible. Fail mode: anonymous content on token pages and exchange landing pages.

Check 16: Audit firm citations. Token landing pages and protocol pages cite at least one named audit firm with audit date and link to report. Fail mode: "audited and secure" without naming the auditor.

Check 17: Regulatory disclosures where required. Pages targeting regulated jurisdictions include the appropriate disclosures. Fail mode: US-targeted product pages with no SEC-relevant disclaimers; EU-targeted pages with no MiCA-relevant language.

Check 18: Backlink profile health. Toxic links below 5% of total profile. Crypto-tuned toxicity scoring catches what generic tools miss. Fail mode: PBN links from recycled scam-token domains accumulate without disavow.

Check 19: Crypto-native authority citations inbound. Site is cited by CoinGecko, DefiLlama, audit firms or major crypto publications. These citations transfer authority faster than generic high-DA backlinks. Fail mode: site has good generic backlinks but no crypto-native authority links.

Checks Web3-específicos (20 al 23)

Los últimos cuatro checks capturan problemas que son específicos a sitios crypto y por los cuales las auditorías SEO genéricas no prueban.

Check 20: Token disambiguation. Token name does not collide with another token of the same name on a different chain. Where collision exists, the page disambiguates explicitly. Fail mode: "USDC" without specifying chain, leading to wrong-chain extraction.

Check 21: Chain-specific schema. Schema includes the chain explicitly (Ethereum, Arbitrum, Optimism, Base, Solana). Fail mode: schema implies a token without naming the chain, leading to ambiguous AI citations.

Check 22: dApp and marketing site interlinking. The dApp domain (or subdomain) links to the marketing site and vice versa with descriptive anchor text. Fail mode: dApp and marketing site treated as independent properties with minimal cross-linking.

Check 23: Smart-contract address disclosed. Token landing pages include the contract address with explorer link. Fail mode: contract address only appears in the dApp UI, not on the marketing page where AI engines look.

Continúa explorando

Más piezas tácticas del blog Crawlux. Escogidas porque se relacionan con el tópico arriba.