ChatGPT links without tracking can hide AI referrals in direct traffic
A reported ChatGPT link change may move some AI-driven visits into Direct. Learn how to compare sources, landing pages, and conversions before changing your marketing plan.
Measuring the visitors AI assistants send you, and what to do with the numbers. New articles publish daily.
A reported ChatGPT link change may move some AI-driven visits into Direct. Learn how to compare sources, landing pages, and conversions before changing your marketing plan.
OAI-SearchBot and ChatGPT-User represent different request types. Separate their log entries before comparing AI discovery activity with visits from people.
AI referrals can look important when measured alone. Compare them with organic search, conversions, and direct traffic before changing your marketing plan.
AI referral reports can show only the visits that preserve source signals. Add confidence labels, compare direct traffic, and make decisions without overstating the channel.
Missing campaign tags can move AI-assisted visits into Direct traffic. Learn how to identify the reporting gap, protect decisions, and document affected dates.
AI assistants can generate both human clicks and automated page requests. Separate those signals in your logs so referral reports show people, bots, and uncertainty.
A temporary loss of ChatGPT referral signals moved some AI visits into Direct traffic. Learn how to mark the gap and read October reports fairly.
A visit from an AI assistant to an insecure web address can arrive with no referrer. Here is how to find those gaps and keep your AI referral counts honest.
A robots.txt edit can change AI bot hits and AI referral visits weeks later. Log every change date in your traffic report so you do not misread the trend.
A new IETF draft describes how bots can sign requests so sites can verify who sent them. Here is what it means for separating AI bots from people in your reports.
A user-agent string can be faked by anyone. Learn how to check AI bot hits against the IP ranges the platforms publish, so your bot counts and referral reports stay honest.
Google-Extended is a robots.txt token, not a crawler with its own user agent. Learn what that means for filters, bot reports and AI visit counts in your traffic data.
AI referrals can show clear source signals while other visits remain unattributed. Learn how to read the visible minimum without turning missing referrers into false totals.
ChatGPT adds a utm_source tag to links it sends. Redirects, link cleanup and referrer settings can erase it. Learn how to check your site and keep AI visits countable.
AI referral reports can miss an important cause of low visibility. Check robots.txt, firewall rules, and server responses before treating crawler activity as a traffic problem.
OpenAI says its crawler user-agent version numbers can change and that it marks robots.txt requests. Here is how to build log filters that keep working and keep bots out of your visit counts.
AI referral studies can report very different results because platforms classify visits differently. Use consistent definitions, source checks and conversion data before changing plans.
A new reporting category separates visits from AI assistants, giving website owners a clearer way to compare referrals, landing pages and conversions.
Google Gemini now adds UTM parameters to outgoing links, giving website owners a clearer way to separate AI referrals from direct traffic and compare results.
Some visits from AI assistants arrive with no referrer and look like direct traffic. Learn why it happens and how to read your report so you do not undercount AI.
AI browser agents can look like ordinary people in website data. Learn how to separate known crawlers, agent-assisted visits, and uncertain traffic without overstating what reports prove.
ChatGPT-User and Google-Agent fetch your pages when a person asks, and they ignore robots.txt. Learn how to sort these hits from crawlers and real visitors in your reports.
Compare automated AI crawler requests with identifiable human referrals to prevent misleading traffic reports and make better content, hosting, and measurement decisions.
A bot fetching your page for an AI assistant is not a customer visit. Learn which signals separate AI crawlers from real people, and how to keep your reports honest.
New September data shows sharp growth in AI referrals, but referral sessions and crawler requests measure different things. Learn how to read both numbers.
Our commitment to digital accessibility and inclusive design
AppWT Web & AI Solutions is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply the relevant accessibility standards to achieve these goals.
The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.
AppWT Web & AI Solutions is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.
Accessibility of AppWT Web & AI Solutions relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:
These technologies are relied upon for conformance with the accessibility standards used.
We welcome your feedback on the accessibility of AppWT Web & AI Solutions. Please let us know if you encounter accessibility barriers:
Phone: (888) 565-0171
Email: sales@appwt.com
Address: 33300 Five Mile Rd, Livonia, MI 48154 (by Appointment Only)
AppWT Web & AI Solutions assessed the accessibility of our website by the following approaches:
This statement was created on January 15, 2025 using the W3C Accessibility Statement Generator Tool.
Last updated: