--- title: "11,793 AI Bot Hits on Our Homepage. Only 2,219 Were Verified." description: "Dedicated strategists run your account and a proprietary engine trained on $500B in profitable ad spend optimises the execution underneath them" image: "https://cdn.prod.website-files.com/6823bbd57170ea42b357cf81/6ac1e225f45c1574accb38f1_24489b89-9fce-46f1-9c97-1af943e87cb2.png" --- October 4, 2026 • 11 min read # 11,793 AI Bot Hits on Our Homepage. Only 2,219 Were Verified. ![Young man with curly hair wearing a black shirt outdoors against green foliage background.](https://cdn.prod.website-files.com/6821efca072e48f6f495a47e/68562d390107b3921a6e3d68_1743932904108.jpg) **Alexander Perleman**, Head Of Product @ groas Ex-Goldman Sachs and Stanford Computer Science **Email: alex@groas.com** [**LinkedIn: https://www.linkedin.com/in/alexander-433793253/**](https://www.linkedin.com/in/alexander-433793253/) ![Cover image for: 11,793 AI Bot Hits on Our Homepage. Only 2,219 Were Verified.](https://cdn.prod.website-files.com/6823bbd57170ea42b357cf81/6ac1e225f45c1574accb38f1_24489b89-9fce-46f1-9c97-1af943e87cb2.png) Only **18.8%** of the AI bot hits on our homepage were verified crawlers. Over 30 days on groas.com, the page logged 11,793 requests claiming to be AI bots; 2,219 passed verification. A chart of the first number would have looked busy. It would not have told us much about AI visibility. The more useful number sat elsewhere: three dated, specific posts received **524 live-answer fetches** between them, while three category pages with more than 3,000 claimed hits each received none. That does not prove every fetch produced a citation. It does show why I no longer treat crawl volume as the prize. Answer retrieval concentrated on a few pages built to answer specific questions. #### The homepage number that fooled me Our edge logs counted requests whose user agents *said* they were AI bots. That is a claim, not an identity: [anyone can send `User-Agent: GPTBot` with curl from a laptop](https://github.com/waseemnasir2k26/aeo-crawl-radar). Scrapers can wear the same costume, particularly where a site whitelists known AI crawlers. We checked the claimed traffic against publisher information: GPTBot against [OpenAI's `gptbot.json`](https://honeyb.ai/blog/gptbot-verify), OAI-SearchBot against [its `searchbot.json`](https://honeyb.ai/blog/gptbot-verify), and Claude traffic against [Anthropic's combined `bots.json` feed](https://support.claude.com/en/articles/8896518). These are our site logs, not an industry sample; the percentages below describe this path in this 30-day window. | Path | Claimed AI hits | Verified crawler hits | Verified share | | --- | --- | --- | --- | | Homepage `/` | 11,793 | 2,219 | **18.8%** | I used to tell clients to watch crawl volume as a proxy for AI visibility. I was wrong. On our homepage, roughly four out of five hits in that chart failed the verification step. Before asking whether a number went up, ask what the number counts. #### Separate the bots before you compare pages I now keep **three buckets** rather than one: - **Claimed hits:** requests carrying a bot user agent, whether or not the requester is that bot. - **Verified hits:** requests whose network identity passes the relevant check. For OpenAI, we match published IP lists; for Anthropic, its published feed; for [PerplexityBot, forward-confirmed reverse DNS and published bot files](https://surfacedby.com/ai-crawlers-reference-2026). - **Live-answer fetches:** verified requests classified as retrieval for an answer, rather than a steady training crawl. This is a measure of fetching, not a count of citations displayed to users. The jobs differ. [OpenAI distinguishes GPTBot, OAI-SearchBot, and ChatGPT-User](https://developers.openai.com/api/docs/bots): training, search and citations, and on-demand page fetches are not interchangeable. [Allowing GPTBot does nothing for OAI-SearchBot or PerplexityBot](https://surfacedby.com/ai-crawlers-reference-2026). [Blocking GPTBot does not by itself remove you from ChatGPT answers; blocking OAI-SearchBot can](https://developers.openai.com/api/docs/bots). Nor does reverse DNS settle OpenAI identity when [OpenAI publishes no stable rDNS suffix](https://honeyb.ai/blog/gptbot-verify). Use the check that fits the bot. Our `robots.txt` shows why even the third bucket needs interpretation. It drew **1,156 fetches classified as live Claude traffic** in the same window. That is a retrieval check, not evidence that anyone cited a robots file. And [an Anthropic IP verifies the organization, not which of ClaudeBot, Claude-User, or Claude-SearchBot made the request](https://support.claude.com/en/articles/8896518); the user agent and request pattern still matter when classifying its job. There are limits outside the log, too. [Cloudflare notes that edge blocking can keep requests out of origin logs](https://developers.cloudflare.com/bots/additional-configurations/block-ai-bots/). A separate 28-day comparison reported roughly [2,237 ClaudeBot crawls and 217 GPTBot crawls per referral](https://seomator.com/blog/geo-data-report-2026-which-ai-crawlers-llm-bots-take-the-most-and-give-the-least). That study measures crawls against referrals, not our answer fetches against citations, so I would not paste its ratios onto our site. Its useful warning is narrower: a large crawl count need not produce a large visible return. **Count the bot's job before you assign value to its visit.** #### Three posts took the answer-fetch traffic In our logs, **524 live-answer fetches went to three URLs**. The figures below come from the same groas.com 30-day window as the homepage count. The final column describes what each page offers a reader or fetcher; it is my explanation of the pattern, not a reason recorded by a bot. | Page | Live-answer fetches | Material available to retrieve | | --- | --- | --- | | YouTube ads 2026 guide | **290** | Dated format prices, frequency rules, and policy cutoffs | | AI Max setup and data guide | **144** | Step order, data requirements, and settings in sequence | | Google Ads updates 2026 | **90** | Dated changes, effective dates, and whom they affect | These are not three versions of an *ultimate guide to everything*. Each gives a fetcher something bounded: a date, a price or limit, a requirement, or a step in an order. The page does less interpretive work for the system retrieving it. That is my reading of the concentration, not a claim that a log can reveal why a model chose a URL. Outside work points in a similar direction, with different measures and limits. One citation study reports AI-cited content as [about 25.7% fresher than standard search results](https://baadigi.com/chatgpt-contractor-study-august-2026) and reports [higher AI visibility for content with statistics, sources, and quotes, alongside lower visibility for keyword stuffing](https://baadigi.com/chatgpt-contractor-study-august-2026). Its tracker of [1,429 AI answers](https://baadigi.com/chatgpt-contractor-study-august-2026) also found ChatGPT returning to pages with specific, checkable facts. Those are outside observations, not a controlled explanation of our 524 fetches. Our logs support the practical hypothesis: **make the answer easy to locate and check**. They do not let me claim that each request became a displayed citation. #### Three busy category pages got none The contrast is blunt. Each of our three busiest category pages cleared **3,000 claimed AI hits** in the same window. Their live-answer fetch counts were **zero, zero, and zero**. Older explainer posts also received verified bot visits without showing up in the answer-fetch pattern we could identify. Traffic reached those pages; the retrieval activity we were looking for concentrated elsewhere. That is not the same as saying category pages are useless, or that every broad page loses every citation. It says their apparent bot popularity did not predict this particular outcome. A separate summary of ChatGPT Search behavior reports that [around 85% of retrieved pages in its analysis were never cited](https://seomator.com/blog/geo-data-report-2026-which-ai-crawlers-llm-bots-take-the-most-and-give-the-least). Retrieval itself is already a narrower measure than crawling, and even retrieval is not a citation receipt. I would still choose a narrow page with a quotable answer over a broad page that makes the reader hunt through several topics. Our three posts give that choice a concrete basis on this site. The category-page chart gives me no reason to buy more of what it measures. #### What I would change on a business site First, **report verified answer fetches beside crawl totals**, not underneath them as a footnote. I want two ratios each month: verified hits divided by claimed hits, and live-answer fetches divided by verified hits. The homepage's first ratio was 18.8%; the three category pages recorded zero live-answer fetches. Neither figure alone describes the whole site's visibility. Together, they make a vendor's rising bot-traffic chart much harder to mistake for progress. If someone cannot show how they checked bot identity, I would not call the chart verified AI traffic. Second, build fewer, sharper pages around buyer questions. Say you spend $20k a month and one broad services page tries to cover twelve questions. I would not assume that splitting it will reproduce our results. I would ask whether any one question has a clear answer on that page. Our most-fetched posts put dated, usable details where a reader can find them. My working rule is one buyer question, one URL, a quotable answer in the first 150 words, and the supporting detail underneath. Date material that depends on the year. Name the numbers you can substantiate and cite their source on the page. Do not add a year merely as decoration; make it tell the reader which version of an answer they are getting. Third, check fetchability before rewriting copy. A polished answer cannot help a retrieval bot that is blocked at the edge or receives blank HTML without JavaScript. Check the bot rules, the response it actually receives, and whether your robots file permits the retrieval crawlers you mean to reach. [*Before You Write for ChatGPT, Check Whether AI Can Read Your Site*](https://groas.com/post/before-you-write-another-page-for-chatgp) lays out that audit before you spend money on new content. There is no point polishing a page the intended fetcher cannot read. #### Run the comparison on your own logs **Question:** Which pages receive live-answer fetches, and which merely collect claimed bot hits? This is the test I would run prospectively with edge logs or CDN bot analytics. Hold the time window and classification rules constant across paths. Do not treat a change in either as a content result. 1. **Collect 30 days of requests by path and user agent.** Export path, user agent, IP, and timestamp. Keep `robots.txt` in the set: its retrieval checks are a useful reminder that a fetch need not mean content demand. 2. **Split claimed traffic from verified traffic.** Match OpenAI requests against its published `gptbot.json`, `searchbot.json`, and `chatgpt-user.json` lists; Anthropic requests against `bots.json`; and Perplexity against forward-confirmed reverse DNS and its bot files. Leave requests that fail your check in the claimed bucket. 3. **Classify answer retrieval separately.** Look for OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, and Perplexity-User, alongside fetch bursts tied to a fresh answer request rather than a steady crawl rhythm. For a shared publisher IP feed, do not infer the exact bot from the IP alone. Keep uncertain requests identifiable rather than silently promoting them to confirmed answer activity. 4. **Rank your top 10 paths three ways:** claimed hits, verified hits, and live-answer fetches. For each path, calculate verified share and live-answer share. Keep the raw counts beside the ratios; a percentage without its denominator is another attractive chart that can waste your afternoon. My expectation is that the lists will diverge. Claimed traffic may favor a homepage or category pages; answer retrieval may favor dated posts with prices, thresholds, or steps. The mechanism I would test is straightforward: a page that supplies a checkable answer gives a fetcher less to reconstruct than a page that gestures at several answers. That is a hypothesis to compare with your own paths, not a forecast that every site will have our distribution. If the lists match, inspect the pages before rewriting them; your broad pages may already contain the answers people seek. If answer fetches read zero, check edge rules and rendered output before blaming the copy. Either result changes the next task. **Do not commission more content to increase crawling until you know which pages retrieval bots can reach and use.** #### One site and one month set the boundary This is one domain, one 30-day window, and a site that publishes dated Google Ads and YouTube guides. A local services site with twelve pages and no dated posts has no reason to expect our 524-fetch pattern. A news site may have a different rhythm again. Treat the homepage's 18.8% verified share and the three posts' 524 fetches as observations about groas.com, not targets for another site. Skip the verified-share test if you cannot obtain edge logs or CDN analytics with IPs. User-agent strings alone cannot run that step. If your firewall blocks retrieval at the edge, a zero in your logs may reflect access policy rather than a failed page. And throughout this analysis, **a fetch is evidence of retrieval, not proof of a published citation**. That boundary matters most when someone tries to turn a promising log count into a claim about revenue. ![Funnel diagram showing claimed AI bot hits narrowing to verified crawlers and live-answer fetches](https://cdn.prod.website-files.com/6823bbd57170ea42b357cf81/6ac1e226f45c1574accb3930_533c4c59-5962-4d34-b4ef-350d18236596.png) The decision the numbers support is narrow: stop buying crawl volume as a goal. On our site, the busiest claimed traffic did not identify the pages getting answer fetches. Three dated, specific posts did that work. If you want to see which buyer questions trigger mentions of your business and where the gaps sit, [earned search](https://groas.com/earned-search) is built to track that across engines. You can start with the logs: pull the three lists, inspect the pages already getting fetched, and decide what answer each could make clearer. Leave the busy category pages out of the rewrite queue unless the evidence gives you a reason to put them back. Keep the raw export for the next month. Bot lists and hosts change, and one 30-day slice cannot show whether an edit worked. I keep the three lists frozen by date, then compare the same paths after a fetchability fix or rewrite. If the retrieval pattern moves, there is something to investigate. If only the claimed-hit chart moves, I do not call it a win. #### Preguntas frecuentes **¿Qué porcentaje de las visitas de bots de IA a la página de inicio de groas.com eran crawlers verificados?** Solo el 18.8%. En 30 días, la página de inicio registró 11,793 solicitudes que decían ser bots de IA, pero solo 2,219 pasaron la verificación contra las listas publicadas de los proveedores. Aproximadamente cuatro de cada cinco visitas fallaron el paso de verificación, por lo que el volumen de rastreo por sí solo no es una buena medida de visibilidad en IA. **¿Por qué hay que separar las visitas de bots afirmadas de las verificadas antes de comparar páginas?** Porque una cadena de user-agent es una declaración, no una identidad: cualquiera puede enviar User-Agent: GPTBot con curl desde un portátil. Las visitas afirmadas incluyen a cualquier persona que finge ser un bot; las visitas verificadas pasan comprobaciones como las listas de IP publicadas de OpenAI o el feed bots.json de Anthropic. Los fetches de respuestas en vivo son un tercer grupo que mide la recuperación de respuestas, no el rastreo de entrenamiento. **¿Permitir GPTBot en robots.txt también permite a OAI-SearchBot o PerplexityBot?** No. Permitir GPTBot no hace nada por OAI-SearchBot ni por PerplexityBot, y bloquear GPTBot por sí solo no elimina un sitio de las respuestas de ChatGPT, mientras que bloquear OAI-SearchBot sí puede hacerlo. Cada bot tiene un trabajo diferente (entrenamiento, búsqueda, recuperación bajo demanda), por lo que las reglas y los métodos de verificación deben coincidir con el bot específico. **¿Qué páginas recibieron los fetches de respuestas en vivo en groas.com?** Tres URLs recibieron 524 fetches de respuestas en vivo en total: la guía de anuncios de YouTube 2026 con 290, la guía de configuración y datos de AI Max con 144, y Google Ads updates 2026 con 90. Cada página ofrece detalles acotados y verificables como precios fechados, pasos ordenados o fechas de entrada en vigor. **¿Las páginas de categoría con mucho tráfico de bots de IA recibieron fetches de respuestas?** No. En el caso de groas.com, tres páginas de categoría registraron más de 3,000 visitas de bots de IA afirmadas cada una durante 30 días, pero sus recuentos de fetches de respuestas en vivo fueron cero. El aparente tráfico de bots no predijo la actividad de recuperación, que se concentró en unas pocas publicaciones fechadas y específicas. **¿Un fetch de un bot de IA significa que el contenido fue citado en una respuesta?** No. Un fetch muestra que un bot verificado recuperó la página para una respuesta, no que el contenido se mostrara a los usuarios como una cita. Un análisis separado del comportamiento de ChatGPT Search encontró que alrededor del 85% de las páginas recuperadas nunca fueron citadas, por lo que la recuperación en sí ya es una medida más limitada que el rastreo. **¿Qué cambios recomienda hacer en un sitio de negocio para la visibilidad en IA?** Informe de los fetches verificados junto con los totales de rastreo, rastreando dos ratios cada mes: visitas verificadas divididas por visitas afirmadas, y fetches de respuestas en vivo divididos por visitas verificadas. Luego, construya menos páginas más nítidas en torno a una pregunta de comprador por URL, con una respuesta citable en las primeras 150 palabras, materiales fechados y números sustanciales con fuentes citadas. **¿Qué debo comprobar antes de reescribir el contenido para los bots de IA?** Compruebe la obtención (fetchability) antes de reescribir la copy: las reglas de bot, la respuesta real que recibe el bot y si su archivo robots permite a los crawlers de recuperación a los que desea llegar. Una página pulida no puede ayudar a un bot bloqueado en el borde o que recibe HTML en blanco sin JavaScript, por lo que pulir una página que el fetcher previsto no puede leer no tiene sentido. ## Related Posts [![A foggy crystal ball beside a clipboard of green-ticked tasks: the agency sells the verifiable checklist, not a prediction of what AI will say.](https://cdn.prod.website-files.com/6823bbd57170ea42b357cf81/6ac49220d54ff28579b596c5_88e2eb67-b856-4d22-962a-a4e3dc5d7df6.png) ##### The AEO Retainer Swipe File: Tiers, Scope Clauses and Client Scripts October 6, 2026 • 11 min read Written by Alexander Perelman](https://groas.com/post/the-aeo-retainer-swipe-file-copy-ready-t) [![Clay figure pours a wheelbarrow of articles into a wall funnel whose pipe is disconnected, so the pages pile on the floor beside an unused wrench.](https://cdn.prod.website-files.com/6823bbd57170ea42b357cf81/6ac48e5808a82e2ea5358099_e3125d33-6dbe-4978-b7a4-40d772753208.png) ##### Can ChatGPT Read Your Site? A 45-Minute Check Before You Write More AEO Content October 6, 2026 • 11 min read Written by Alexander Perelman](https://groas.com/post/can-chatgpt-even-read-your-site-a-45-min) [![Cartoon of a marketer noting 'position two' after one pull of a slot machine whose reels are already spinning to a new result.](https://cdn.prod.website-files.com/6823bbd57170ea42b357cf81/6ac48e47904ce2271e972a6f_9b960565-71b9-49f2-906a-482b1c4c2a39.png) ##### Six PPC Habits That Misread AI Visibility October 6, 2026 • 12 min read Written by David](https://groas.com/post/i-measured-ai-visibility-like-a-ppc-acco) ![](https://cdn.prod.website-files.com/6821efca072e48f6f495a47e/6823c03839b2b618430d5ae6_Light-p-500.png) [![White stylized owl eyes with green background icon.](https://cdn.prod.website-files.com/6821efca072e48f6f495a47e/6a68a036a5dd5627409d3579_Groas%20Icon.png)](https://groas.com/post/we-logged-30-days-of-ai-bots-on-our-own#) [contact](mailto:scale@groas.ai) Explore [Home](https://groas.com/)[Philosophy](https://groas.com/our-philosophy)[Blog](https://groas.com/blog) What We Do [Paid Search](https://groas.com/paid-search)[Earned Search](https://groas.com/earned-search) Who We Serve [Businesses](https://groas.com/for-businesses)[Agencies](https://groas.com/for-agencies) MCP [ChatGPT](https://chatgpt.com/plugins/plugin_asdk_app_6a9c2d7108f08191beb5b3d736be8655?q=groas)[Claude](https://claude.ai/directory/mcp-groas-ai) Legal [Privacy Policy](https://groas.com/legal/privacy-policy)[Terms of Service](https://groas.com/legal/terms) Get Started [Apply](https://groas.typeform.com/to/xC1bQNUT) © 2026 groas 🇺🇸 [![](https://cdn.prod.website-files.com/62434fa732124a0fb112aab4/62434fa732124a389912aad8_linkedin%20small.svg)](https://www.linkedin.com/company/groas/) ```json { "@context": "https://schema.org", "@graph": [ { "@type": "BlogPosting", "@id": "https://www.groas.com/post/we-logged-30-days-of-ai-bots-on-our-own#article", "headline": "11,793 AI Bot Hits on Our Homepage. Only 2,219 Were Verified.", "description": "", "url": "https://www.groas.com/post/we-logged-30-days-of-ai-bots-on-our-own", "image": { "@type": "ImageObject", "url": "https://cdn.prod.website-files.com/6823bbd57170ea42b357cf81/6ac1e225f45c1574accb38f1_24489b89-9fce-46f1-9c97-1af943e87cb2.png" }, "thumbnailUrl": "https://cdn.prod.website-files.com/6823bbd57170ea42b357cf81/6ac1e225f45c1574accb38f1_24489b89-9fce-46f1-9c97-1af943e87cb2.png", "datePublished": "2026-10-04T05:20:39.194Z", "dateModified": "2026-10-04T05:20:39.194Z", "inLanguage": "en-US", "isAccessibleForFree": true, "articleSection": "AI For Google Ads", "keywords": "Google Ads, AI For Google Ads", "mainEntityOfPage": { "@type": "WebPage", "@id": "https://www.groas.com/post/we-logged-30-days-of-ai-bots-on-our-own" }, "author": { "@id": "https://www.groas.com/author/david#person" }, "publisher": { "@id": "https://www.groas.com#organization" }, "about": [ { "@type": "Thing", "name": "Google Ads" }, { "@type": "Thing", "name": "Pay-per-click advertising" }, { "@type": "Thing", "name": "Performance marketing" } ], "mentions": [ { "@type": "Organization", "name": "groas", "url": "https://www.groas.com" }, { "@type": "Thing", "name": "Google Ads" } ], "speakable": { "@type": "SpeakableSpecification", "cssSelector": ["h1"] } }, { "@type": "Person", "@id": "https://www.groas.com/author/david#person", "name": "David", "description": "", "jobTitle": "Founder & CEO @ groas", "email": "", "url": "https://www.groas.com/author/david", "image": { "@type": "ImageObject", "url": "https://cdn.prod.website-files.com/6823bbd57170ea42b357cf81/686a2a76611e759fd8d8a3fd_David%20LinkedIn%20Profile.jpeg" }, "sameAs": [ "" ], "knowsAbout": [ "Google Ads", "Performance Max", "AI Max", "Pay-per-click advertising", "Conversion tracking", "Bid management", "Search advertising" ], "worksFor": { "@id": "https://www.groas.com#organization" } }, { "@type": "Organization", "@id": "https://www.groas.com#organization", "name": "groas", "alternateName": "groas.com", "url": "https://www.groas.com", "logo": { "@type": "ImageObject", "url": "https://cdn.prod.website-files.com/6821efca072e48f6f495a47e/6834a970e03a7016560e3515_Logo%20Design%20256x256.png" }, "description": "Dedicated strategists run your account and a proprietary engine trained on $500B in profitable ad spend optimises the execution underneath them", "sameAs": [ "https://www.linkedin.com/company/groas" ], "knowsAbout": [ "Google Ads", "Performance Max", "AI Max for Search", "Pay-per-click advertising", "Autonomous campaign management", "AI advertising agents" ], "areaServed": "Worldwide" }, { "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.groas.com" }, { "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://www.groas.com/blog" }, { "@type": "ListItem", "position": 3, "name": "AI For Google Ads", "item": "https://www.groas.com/category/AI For Google Ads" }, { "@type": "ListItem", "position": 4, "name": "11,793 AI Bot Hits on Our Homepage. Only 2,219 Were Verified.", "item": "https://www.groas.com/post/we-logged-30-days-of-ai-bots-on-our-own" } ] } ] } ``` ```json {"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"¿Qué porcentaje de las visitas de bots de IA a la página de inicio de groas.com eran crawlers verificados?","acceptedAnswer":{"@type":"Answer","text":"Solo el 18.8%. En 30 días, la página de inicio registró 11,793 solicitudes que decían ser bots de IA, pero solo 2,219 pasaron la verificación contra las listas publicadas de los proveedores. Aproximadamente cuatro de cada cinco visitas fallaron el paso de verificación, por lo que el volumen de rastreo por sí solo no es una buena medida de visibilidad en IA."}},{"@type":"Question","name":"¿Por qué hay que separar las visitas de bots afirmadas de las verificadas antes de comparar páginas?","acceptedAnswer":{"@type":"Answer","text":"Porque una cadena de user-agent es una declaración, no una identidad: cualquiera puede enviar User-Agent: GPTBot con curl desde un portátil. Las visitas afirmadas incluyen a cualquier persona que finge ser un bot; las visitas verificadas pasan comprobaciones como las listas de IP publicadas de OpenAI o el feed bots.json de Anthropic. Los fetches de respuestas en vivo son un tercer grupo que mide la recuperación de respuestas, no el rastreo de entrenamiento."}},{"@type":"Question","name":"¿Permitir GPTBot en robots.txt también permite a OAI-SearchBot o PerplexityBot?","acceptedAnswer":{"@type":"Answer","text":"No. Permitir GPTBot no hace nada por OAI-SearchBot ni por PerplexityBot, y bloquear GPTBot por sí solo no elimina un sitio de las respuestas de ChatGPT, mientras que bloquear OAI-SearchBot sí puede hacerlo. Cada bot tiene un trabajo diferente (entrenamiento, búsqueda, recuperación bajo demanda), por lo que las reglas y los métodos de verificación deben coincidir con el bot específico."}},{"@type":"Question","name":"¿Qué páginas recibieron los fetches de respuestas en vivo en groas.com?","acceptedAnswer":{"@type":"Answer","text":"Tres URLs recibieron 524 fetches de respuestas en vivo en total: la guía de anuncios de YouTube 2026 con 290, la guía de configuración y datos de AI Max con 144, y Google Ads updates 2026 con 90. Cada página ofrece detalles acotados y verificables como precios fechados, pasos ordenados o fechas de entrada en vigor."}},{"@type":"Question","name":"¿Las páginas de categoría con mucho tráfico de bots de IA recibieron fetches de respuestas?","acceptedAnswer":{"@type":"Answer","text":"No. En el caso de groas.com, tres páginas de categoría registraron más de 3,000 visitas de bots de IA afirmadas cada una durante 30 días, pero sus recuentos de fetches de respuestas en vivo fueron cero. El aparente tráfico de bots no predijo la actividad de recuperación, que se concentró en unas pocas publicaciones fechadas y específicas."}},{"@type":"Question","name":"¿Un fetch de un bot de IA significa que el contenido fue citado en una respuesta?","acceptedAnswer":{"@type":"Answer","text":"No. Un fetch muestra que un bot verificado recuperó la página para una respuesta, no que el contenido se mostrara a los usuarios como una cita. Un análisis separado del comportamiento de ChatGPT Search encontró que alrededor del 85% de las páginas recuperadas nunca fueron citadas, por lo que la recuperación en sí ya es una medida más limitada que el rastreo."}},{"@type":"Question","name":"¿Qué cambios recomienda hacer en un sitio de negocio para la visibilidad en IA?","acceptedAnswer":{"@type":"Answer","text":"Informe de los fetches verificados junto con los totales de rastreo, rastreando dos ratios cada mes: visitas verificadas divididas por visitas afirmadas, y fetches de respuestas en vivo divididos por visitas verificadas. Luego, construya menos páginas más nítidas en torno a una pregunta de comprador por URL, con una respuesta citable en las primeras 150 palabras, materiales fechados y números sustanciales con fuentes citadas."}},{"@type":"Question","name":"¿Qué debo comprobar antes de reescribir el contenido para los bots de IA?","acceptedAnswer":{"@type":"Answer","text":"Compruebe la obtención (fetchability) antes de reescribir la copy: las reglas de bot, la respuesta real que recibe el bot y si su archivo robots permite a los crawlers de recuperación a los que desea llegar. Una página pulida no puede ayudar a un bot bloqueado en el borde o que recibe HTML en blanco sin JavaScript, por lo que pulir una página que el fetcher previsto no puede leer no tiene sentido."}}]} ```