ChatGPT Traffic Outperforms Organic Search in Engagement
ChatGPT traffic engagement outperforms organic search, driven by problem-solving capabilities and user trust in generative AI.
ChatGPT is emerging as a valuable traffic source, though its volume may be too small to appear in a Google Analytics 4 overview. Despite this, ChatGPT traffic often outperforms even organic search in engagement, according to observations from a professional optimizing client sites for AI answers.
While no studies have examined why ChatGPT traffic performs well, two theories are proposed: its problem-solving nature, similar to organic search, and the trust users place in generative AI due to its conversational format. As genAI tools become more mainstream, this trend may shift, requiring close monitoring of AI traffic now.
To track ChatGPT traffic in GA4, go to Acquisition > Traffic acquisition. Below the graph, select “Session source / Medium” from the drop-down menu. In the search field, type “gpt” and press Enter to filter session sources. Custom reports can then be created for quick access to this data.
Although ChatGPT does not disclose user prompts, their content can be inferred by examining the landing pages visited by ChatGPT users. Each page typically addresses a specific problem, suggesting the prompt sought a solution.
For analysis, go to Engagement > Landing Pages, click “Add filter” below “Landing page”, and select “Session source / Medium”. Choose “Contains” and type “gpt” to filter traffic sources. This displays landing pages sorted by the most clicks from ChatGPT.
The resulting report identifies pages cited by ChatGPT. To understand the context of these citations, query ChatGPT directly, asking, “What prompts would trigger ChatGPT to cite the page as a solution?”
Further investigation can be done using tools like Google Search Console and Bing Webmaster Tools to identify AI-driven queries that surface these pages.
A technical challenge arises as Google Analytics misclassifies some ChatGPT traffic as Direct or Unassigned due to the “noreferrer” attribute added by ChatGPT for privacy. This issue is common among clients, where growing ChatGPT traffic is incorrectly labeled as Unassigned.
