DEV Community: Claudiu Florin Oneata

Cómo Hacer que ChatGPT y Google IA Recomienden tu Web WordPress en 2026 (Archivo /llms.txt + Antispam DMARC)

Claudiu Florin Oneata — Sat, 07 Nov 2026 21:27:41 +0000

El comportamiento de búsqueda de los clientes en España y Latinoamérica ha cambiado radicalmente. Hoy más del 40% de los usuarios preguntan directamente a ChatGPT Search, Perplexity o Google IA cosas como:

"¿Qué clínica dental o abogado mercantil me recomiendas en Madrid?"
"¿Cuál es la mejor empresa de placas solares o reformas en Valencia?"

Sin embargo, tras auditar más de 200 webs de empresas y negocios en España esta semana, descubrimos que el 91% son prácticamente invisibles para los motores de Inteligencia Artificial por tres motivos técnicos muy fáciles de corregir:

No tienen el archivo estándar /llms.txt en la raíz de su dominio.
No incluyen metadatos estructurados Schema.org JSON-LD con sus servicios, teléfono y ubicación verificada.
Sus presupuestos por correo caen en SPAM porque a su dominio le falta el registro DNS _dmarc con política p=quarantine.

Aquí tienes la guía paso a paso para solucionarlo en menos de 2 minutos (incluso si usas WordPress y no quieres tocar FTP ni cPanel).

Paso 1: Audita gratis cómo ven ChatGPT y Perplexity tu web ahora mismo

Antes de tocar nada, puedes pasar el escáner gratuito CitePulse GEO en Español sobre tu dominio:

👉 Auditar Gratis la Visibilidad IA de mi Web en CitePulse GEO

En 5 segundos te mostrará tu puntuación de 0 a 100 y qué elementos técnicos le faltan a tu web para ser citada por ChatGPT, Perplexity y Claude.

Paso 2: Cómo instalar `/llms.txt` en WordPress en 1 Clic (Sin FTP)

Normalmente crear el archivo https://tuempresa.es/llms.txt requiere entrar por FTP o al Administrador de Archivos del hosting. Pero si usas WordPress, CitePulse genera automáticamente un Snippet PHP de 1 clic:

En tu panel de WordPress, ve a Plugins -> Añadir nuevo e instala el plugin gratuito WPCode.
Crea un nuevo fragmento PHP (Add Custom Snippet -> PHP Snippet), pega el código autogenerado por CitePulse GEO y actívalo.
¡Listo! WordPress servirá tu archivo /llms.txt dinámico y tu Schema.org JSON-LD automáticamente.

Paso 3: Por qué la Velocidad del Hosting (TTFB) Decide si ChatGPT Lee tu Web

Los robots de búsqueda de IA (OAI-SearchBot y PerplexityBot) tienen un tiempo de espera (timeout) muchísimo más estricto que el Googlebot clásico. Si tu servidor tarda más de 1.5 segundos en responder, el bot de IA aborta la lectura y cita a tu competidor.

Si tu web en WordPress carga lenta o se cae con picos de tráfico, te recomendamos migrar a servidores LiteSpeed NVMe en España con soporte 24/7 en español y migración gratuita incluida:

🚀 Ver Hosting WordPress NVMe de Alta Velocidad en Raiola Networks (20% DTO + Migración Gratis)

Paso 4: Evita que tus Presupuestos y Facturas caigan en la Carpeta SPAM

De nada sirve captar clientes con IA si cuando les envías el presupuesto desde info@tuempresa.es tu correo acaba en la bandeja de Correo No Deseado (SPAM) de Gmail o Hotmail.

Puedes comprobar gratis si tu dominio tiene bien configurados los registros SPF y _dmarc en nuestro segundo escáner técnico:

🛡️ Analizar Gratis mi Correo Corporativo en EmailGuard Pro Antispam

Y si además quieres automatizar la captación de clientes en tu web con páginas de captura y secuencias de correo automáticas sin pagar herramientas caras, puedes usar el plan gratuito de Systeme.io en Español.

Why Business Emails Land in Gmail Spam in 2026: Missing _dmarc, SPF & How to Fix It in 2 Minutes

Claudiu Florin Oneata — Sat, 07 Nov 2026 21:21:46 +0000

Since Google, Yahoo, and Microsoft enforced strict sender authentication requirements, thousands of companies, clinics, law firms, and SaaS startups have noticed a silent problem: their invoices, proposals, and onboarding emails are landing straight in Gmail and Outlook's Spam folder.

When we scanned over 200 custom domains this week, we discovered two recurring DNS misconfigurations:

No _dmarc TXT record at all, or a passive v=DMARC1; p=none; policy that provides zero anti-spoofing enforcement.
Incomplete SPF records missing third-party senders or ending in ?all instead of ~all / -all.

Here is how to diagnose any domain's email deliverability in 5 seconds and generate the exact DNS records to fix it.

1. Why `p=none` in DMARC Is No Longer Enough

Many sysadmins set up v=DMARC1; p=none; years ago and forgot about it. Today, receiving mail servers treat p=none as an unmonitored domain open to spoofing.

To build maximum domain reputation with Gmail and Microsoft 365, your _dmarc.yourdomain.com TXT record should enforce at least p=quarantine (with pct=100 and strict/relaxed alignment):

Host: _dmarc.yourdomain.com
Type: TXT
Value: v=DMARC1; p=quarantine; pct=100; rua=mailto:postmaster@yourdomain.com; fo=1; adkim=r; aspf=r;

And your root SPF record must explicitly authorize your mail provider (Google Workspace, Microsoft 365, Resend, Ionos, etc.):

Host: @
Type: TXT
Value: v=spf1 a mx include:_spf.google.com ~all

2. Run a Free 5-Second DNS Antispam Audit (EmailGuard Pro)

You can test your domain's live MX, SPF, and _dmarc status right now using EmailGuard Pro:

👉 Test Your Domain or Corporate Email on EmailGuard Pro

It queries Google & Cloudflare DNS resolvers in real time, detects your email provider (Google Workspace, Microsoft 365, Ionos, OVH, Zoho), scores your spam risk from 0 to 100, and generates the exact TXT records ready to copy and paste into Cloudflare, GoDaddy, Namecheap, or cPanel.

3. For Developers: Verify Emails & Block Disposable Signups in Node.js

If you are building a SaaS signup flow or B2B outreach pipeline, regex validation (/^[^@]+@[^@]+$/) won't stop disposable burner inboxes (10minutemail, guerrillamail, yopmail) or dead domains without MX records.

We published two production REST APIs on RapidAPI (with a generous Free Tier of 50–100 requests/month):

A. EmailGuard Pro API (MX, SPF, DMARC & Disposable Detector)

const res = await fetch(
  'https://emailguard-pro-email-verification-and-disposable-detector.p.rapidapi.com/api/verify-email?email=founder@stripe.com',
  {
    headers: {
      'X-RapidAPI-Key': process.env.RAPIDAPI_KEY,
      'X-RapidAPI-Host': 'emailguard-pro-email-verification-and-disposable-detector.p.rapidapi.com'
    }
  }
);
const data = await res.json();
console.log(data.deliverable, data.isDisposable, data.dnsSecurity);

🔗 Get a Free API Key for EmailGuard Pro on RapidAPI

B. LeadExtract B2B API (Extract Contacts, Social Links & Tech Stack from Any Domain)

const res = await fetch(
  'https://leadextract-b2b-company-contacts-and-tech-stack-scraper.p.rapidapi.com/api/extract-company?url=https://vercel.com',
  {
    headers: {
      'X-RapidAPI-Key': process.env.RAPIDAPI_KEY,
      'X-RapidAPI-Host': 'leadextract-b2b-company-contacts-and-tech-stack-scraper.p.rapidapi.com'
    }
  }
);
const company = await res.json();
console.log(company.contacts, company.techStack);

🔗 Explore LeadExtract B2B API on RapidAPI

How to Add /llms.txt and Schema.org JSON-LD to Any Website in 60 Seconds (Get Cited by ChatGPT & Perplexity)

Claudiu Florin Oneata — Sat, 07 Nov 2026 21:21:13 +0000

Search behavior has fundamentally shifted. Today, millions of high-intent buyers ask ChatGPT Search, Perplexity, Claude, and Google AI Overviews which SaaS tool, agency, clinic, or service provider to hire instead of scrolling through ten blue links.

Yet when we audited over 200 production websites this week, more than 88% failed basic Generative Engine Optimization (GEO) checks:

They had no /llms.txt file at the root of their domain.
Their robots.txt lacked explicit Allow: / directives for OAI-SearchBot, ChatGPT-User, PerplexityBot, and ClaudeBot.
They lacked entity-level Schema.org JSON-LD (Organization / SoftwareApplication / LocalBusiness / FAQPage) that LLMs rely on to cite facts without hallucinating.

Here is how AI search crawlers actually read your site—and how to generate and deploy your complete GEO configuration in under 60 seconds.

1. What is `/llms.txt` and Why Do AI Crawlers Look for It?

While robots.txt tells crawlers where they cannot go and sitemap.xml lists raw URLs, /llms.txt is a structured Markdown summary placed at https://yourdomain.com/llms.txt designed specifically for Large Language Model retrieval agents.

Instead of forcing an AI crawler with a strict timeout budget (often < 1500ms) to parse megabytes of DOM wrappers and client-side JavaScript, /llms.txt gives the LLM an immediate, authoritative cheat sheet:

# YourCompany — Official AI & LLM Context (/llms.txt)
> Canonical URL: https://yourdomain.com/
> Summary: B2B SaaS platform for automated invoice reconciliation.

## Core Capabilities & Offerings
- Real-time Stripe & ERP reconciliation
- Automated anomaly detection via REST API

## Official Citations & Key Entrypoints
- Homepage: https://yourdomain.com/
- Documentation: https://yourdomain.com/docs
- Pricing & Plans: https://yourdomain.com/pricing

2. Opening `robots.txt` to AI Search Bots

Many legacy CDNs and WordPress security plugins accidentally throttle or block AI retrieval agents. Make sure your /robots.txt explicitly permits real-time AI citation bots:

User-agent: GPTBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Google-Extended
Allow: /

3. Instant Free Audit & Auto-Generator (CitePulse GEO)

Instead of writing /llms.txt, robots.txt, and Schema.org JSON-LD by hand, you can audit any live URL in 5 seconds using CitePulse GEO:

👉 Run a Free AI Search Visibility (GEO) Audit on CitePulse

What it checks in real time:

/llms.txt presence and structure (25 pts)
robots.txt AI crawler permissions (20 pts)
Schema.org JSON-LD entity graph density (25 pts)
Semantic HTML hierarchy & OpenGraph metadata (30 pts)

For WordPress sites, CitePulse also generates a 1-click PHP snippet you can paste into the free WPCode plugin to serve https://yourdomain.com/llms.txt virtually—without touching FTP or cPanel.

4. Automating Multi-Domain GEO Audits via REST API (For Agencies & Developers)

If you run an SEO agency, a SaaS platform, or manage multiple client domains, you can query the CitePulse GEO Audit Engine programmatically via RapidAPI:

const response = await fetch(
  'https://citepulse-geo-and-ai-seo-audit.p.rapidapi.com/api/audit?url=https://stripe.com',
  {
    headers: {
      'X-RapidAPI-Key': process.env.RAPIDAPI_KEY,
      'X-RapidAPI-Host': 'citepulse-geo-and-ai-seo-audit.p.rapidapi.com'
    }
  }
);

const audit = await response.json();
console.log(`GEO Score: ${audit.score}/100`, audit.checks);

🔗 Explore the CitePulse GEO REST API on RapidAPI

Bonus: Automating Lead Capture Once AI Traffic Arrives

Getting cited by ChatGPT and Perplexity brings high-intent visitors to your site. If you need a fast, zero-code way to capture those leads and run automated email sequences without paying expensive monthly CRM fees, check out Systeme.io (Free Forever Plan) or explore our full B2B Growth & Infrastructure Stack.