ChatGPT Searches Beyond the Prompt

The Visibility Report #38 | Week of October 6-12, 2026

Ahrefs analyzed 66.6 million free, logged-out ChatGPT responses from August and September. Only 14.4% triggered web search. When ChatGPT did search, it ran about 1.6 fan-out queries per searching response.

The details inside those searches are more useful than the phrase "query fan-out." ChatGPT increasingly looked for official sources, prices, specifications, and reviews. Audit whether a machine can find the factual answers on your own site, then check whether outside sources support the comparisons your site cannot settle by itself.

ChatGPT searched the web for one in seven responses

Ahrefs' study covered 66.6 million free, logged-out GPT-5.6 Luna responses and 15 million fan-out queries. Web search appeared in 14.4% of responses. Among responses that searched, ChatGPT ran about 1.6 fan-out queries on average. The dataset describes free, logged-out sessions, so it does not establish how paid plans, memory, or personalized chats behave.

Of the 15 million fan-outs, 6.8% used a site: operator. Among roughly 160 of the most-searched sites, 75.9% of those searches pointed to a brand website. The word "official" appeared in 13.1% of English fan-out queries in September, up from 10.1% in August. "Price" rose from 6.0% to 8.9%.

Those findings support two different jobs. Put current prices, specifications, support details, and policies in crawlable text on the brand site. For comparisons and subjective questions, review the independent pages that ChatGPT retrieves. Ahrefs found a stronger official-source mix for factual questions than for comparisons, where outside sources carried more of the answer.

Do not build a page for every fan-out string. These queries are generated inside a probabilistic system and can change between runs. Use them to find missing buyer questions, then decide whether each answer belongs on an existing page, a distinct page, or an outside source you need to correct or earn.

Source: Ahrefs query fan-out study​

Google opened a separate fast lane for fresh UGC

Google documented its UGC Fresh Data Program on October 8. Approved platforms can send new user posts and interaction signals through a dedicated ingestion pipeline instead of waiting only for ordinary crawling. Google says the program is separate from the Indexing API and does not guarantee that submitted content will appear in Search.

This is not an indexing shortcut for company blogs. Google limits eligibility to large platforms centered on public user-generated content, social posts, or forum discussions. The content needs stable URLs, public creator profiles, active moderation, OAuth 2.0, validated JSON-LD, and rapid updates to engagement counters. Google says applicants should expect a response in six to eight weeks.

For qualifying communities, the immediate task is technical readiness and moderation. For ordinary brands, the consequence is indirect: fresh discussions from major platforms may reach Search faster. Monitor the communities where customers compare products, report problems, and explain workarounds. You cannot submit a marketing page through this program, but you can make sure the public facts those communities discuss are accurate.

Source: Google Search Central​

Anthropic banned source networks that hide who is behind them

Anthropic published a new usage policy on October 8 that takes effect November 12. Its deceptive-activity section prohibits using Claude to seed search engines or AI systems with material that misrepresents its origin, authorship, or independence. Anthropic gives the example of a network of sites posing as unaffiliated sources while repeating the same claims.

The policy governs how customers use Claude. It is not a Claude ranking update, and it does not prove that answer engines can detect every synthetic source network. Google separately treats attempts to manipulate generative AI responses in Search as spam. The direction is consistent even if enforcement remains uneven.

Audit agencies, content vendors, and satellite sites before the policy date. A group of pages under different names does not become independent evidence when one operator controls the claims. Disclose ownership, name real authors, link primary evidence, and remove fabricated personas or reviews.

Sources: Anthropic | Search Engine Journal​

iPullRank benchmarked whether AI refuses to guess at an SEO diagnosis

iPullRank's Warrant SEO benchmark tests whether an AI system recognizes that the available evidence is too weak to diagnose a search-traffic decline. A crawling problem, analytics change, ranking loss, seasonality, or release can produce similar symptoms. A fluent answer can still point a team toward the wrong fix.

The useful behavior is not a confident diagnosis. It is a bounded answer that separates observed evidence, plausible causes, and the data needed to choose among them. Use AI to form hypotheses, then check analytics, server logs, Search Console, release history, and incident records before changing the site.

Source: iPullRank Warrant SEO benchmark​

Google's hiring plans point to AI-generated content in Discover

Google job listings describe engineering teams that will generate and recommend AI content for Discover and Notifications. A current Senior Staff ML Software Engineer role calls for agentic content-generation flows plus quality checks for factuality, freshness, and coherence. Google is also hiring around Discover personalization and content design.

The listings show an active product direction, not a launch announcement. They do not say when the features will ship or how much of the Discover feed they would fill. Search Engine Journal also notes that Search Console already reports impressions when a site's links appear in Discover's generative AI features, although the report does not separate individual features.

Publishers should watch the Discover generative AI report rather than assume every new AI-generated card will send traffic. Keep the source pages behind those impressions current, and compare changes in impressions with clicks and downstream behavior.

Sources: Google Careers | Search Engine Journal​

Outside pages supplied most of the evidence in an ATS comparison study

Foundation tested 20 applicant-tracking-system buying prompts twice across ChatGPT, Perplexity, Gemini, Claude, Google AI Mode, and Google AI Overviews. The agency reviewed 240 answers and 2,695 recorded source presences. Greenhouse, Ashby, Lever, and Workable supplied 27% of the visible source presence. Outside sources supplied the other 73%.

The source mix changed with the question. In Foundation's analysis, dedicated comparison pages represented 12.6% of source presence for neutral category prompts and 42.1% for direct head-to-head prompts. The pages that appeared often put buyer fit, trade-offs, and recommendations near the top. This is one agency's study of one software category, so the percentages should not be treated as a universal benchmark.

Run your own high-intent comparisons. Record which pages supply claims about pricing, implementation, integrations, limitations, and fit. If a competitor or publisher is explaining your product for you, publish current first-party evidence on the same decision points.

Source: Foundation ATS source study​

From Practitioners

• ​Foundation: A current citation-tracking guide recommends reporting the fixed prompt set, sample size, engine mix, and time period beside any rate. Updated October 10.
• ​Lily Ray: Flagged Anthropic's new rule against using Claude to seed misleading sources. This is practitioner interpretation; the policy text remains the factual source.
• ​Justin Davis: Highlighted that page-level relevance can matter more than broad domain metrics in current citation studies. Treat the post as a lead to inspect the underlying research, not as proof by itself.
• ​r/SEO on AI citation trackers: Practitioners compare tracker results with referral data and manual checks. The thread is background evidence of measurement pain, not proof that any one tool is accurate.
• ​r/SEO on query fan-out: Practitioners discuss generated subqueries and why they should be treated as a changing research sample rather than a page-production checklist.

From the Tool Blogs

• Profound: Dynamic Bot Rendering serves a rendered copy to selected AI bots when important content depends on client-side JavaScript. Published October 11. This is a vendor product announcement; teams should compare the bot and human versions for material differences.
• Semrush: How to track AI citation sources shows the domains and pages cited when a tracked brand is absent, separating source citations from brand mentions. Published October 7.
• seoClarity: What Meta's Muse means for enterprise ecommerce focuses on product data, agent access, checkout paths, and order reporting. Published October 6.

What to watch

• Whether ChatGPT's shift toward official sources persists across models, paid plans, and personalized sessions.
• Which UGC platforms Google accepts and whether their fresh submissions appear more often in AI Overviews or ordinary results.
• How Anthropic enforces the source-manipulation rule against commercial content networks.
• Whether bot-rendering tools preserve parity closely enough to avoid confusing users, crawlers, or compliance teams.

What to do next

• Choose five revenue-relevant prompts and record whether ChatGPT searched the web.
• Capture the fan-out queries, final citations, and whether official brand pages supplied the factual claims.
• Fix missing prices, specifications, policies, and support details on the owned site.
• List the outside pages that influence comparisons and decide whether each needs outreach, correction, or no action.
• Run one recent traffic decline through an evidence checklist before accepting an AI diagnosis.

One prompt can open several retrieval paths, but most ChatGPT responses in this study did not search at all. Measure both conditions. Improve the facts a model can retrieve today, and build the credible evidence it may learn or retrieve later.

The Visibility Report | Will Scott​
This newsletter is produced collaboratively by Will Scott and Bob, an AI agent. Human oversight, AI efficiency.
​Subscribe at thevisibilityreport.com​