How to Track ChatGPT Traffic to Your Website

ChatGPT sends people to websites in three different shapes, and each shape leaves a different clue. This guide shows what those visits look like in real data, how to set up tracking, and which ChatGPT visits no analytics tool can see.

Three shapes of a ChatGPT visit

  1. A click that keeps its referrer. The browser reports chatgpt.com as the page that sent the visitor. This is the easiest shape to recognize.
  2. A click that carries only a tag. Many links clicked inside ChatGPT end in ?utm_source=chatgpt.com. When the app or browser withholds the referrer, that tag in the address is the only clue left.
  3. A copy and paste. Someone copies your address out of an answer and pastes it into a browser. There is no referrer and usually no tag, so the visit looks like someone typed your address.

What the numbers show

AppWT Analytics measured these shapes across the websites it tracked from July 10 to October 7, 2026. The counts come from the raw referrer and landing-address fields of each visit, not from any AI label.

1,035
visits landed with utm_source=chatgpt.com in the address
862 (83%)
of those arrived with no referrer at all
199
visits arrived with chatgpt.com as the referrer (166 of them also carried the tag)

These visits reached 77 different websites. Measured October 8, 2026.

The lesson is simple. A report that reads only the referrer misses most ChatGPT visits, because the tag is often the only clue. A report that reads both still cannot see the copy-and-paste visits, so treat every ChatGPT count as a floor, not the full total.

Set up ChatGPT tracking in AppWT Analytics

  1. Add the script tag to every page. Put it in the <head> section so it runs on each page load:
    <script src="https://analytics.appwt.com/appwt-analytics/assets/js/tracker.js" data-api-key="YOUR_API_KEY"></script>
    The step-by-step tutorial covers WordPress, Shopify, Wix and custom sites.
  2. Read the referrer visits under AI referrals. Visits that arrive with a ChatGPT referrer are labeled AI referrals from ChatGPT in the Traffic Sources report.
  3. Read the tagged visits in the UTM Campaign Performance report. Every visit that landed with utm_source=chatgpt.com appears there, including the ones with no referrer. Today a tagged visit with no referrer is labeled as an ordinary referral from chatgpt.com rather than as an AI referral, so add the two reports together when you want the full ChatGPT count.
  4. Set a goal. A goal, such as reaching your thank-you page, lets the campaign report show which ChatGPT visits turned into business. The guide on measuring conversions from AI search walks through it.

ChatGPT activity you will not see as a visit

The full list of signals, and the order the software checks them, is on How AppWT Detects AI Traffic. For the difference between people and bots, read AI referrals vs AI crawlers.

Common questions

Does ChatGPT pass a referrer to my website?

Often, but not always. In AppWT Analytics data from July 10 to October 7, 2026, 83% of the visits tagged utm_source=chatgpt.com arrived with no referrer, so the tag in the address was the only sign they came from ChatGPT.

What does utm_source=chatgpt.com mean?

It is a tag that appears on many links people click inside ChatGPT. Your analytics tool reads it from the page address when the visitor lands, even when the browser hides the referrer.

Can I see ChatGPT visits that were copied and pasted?

No. A link copied out of a ChatGPT answer and pasted into a browser carries no referrer and usually no tag, so it arrives as direct traffic in any analytics tool.

See your ChatGPT visits

30-day free trial, card required. Then $9.97 a month or $77 a year, per site. Unlimited pageviews. Cancel anytime.

Get Started Free

Accessibility

by AppWT Web & AI Solutions
🛡️ Accessibility Profiles
📝 Content Adjustments
Content Scaling 100%
Font Size 100%
Line Height 1.4
Letter Spacing 0px
🎨 Color Adjustments
Color Saturation 100%
🎛️ Orientation & Controls
♿

Accessibility Statement

Our commitment to digital accessibility and inclusive design

Our Commitment to Accessibility

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.

Conformance Status

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 Features

  • Built-in accessibility toolbar with multiple customization options
  • Keyboard navigation support throughout the website
  • Screen reader compatibility and proper ARIA labels
  • High contrast mode and color customization options
  • Text size adjustment and font modification capabilities
  • Reading guide and focus indicators for improved navigation
  • Alternative text for all images and media
  • Semantic HTML structure for better screen reader interpretation

Technical Specifications

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:

  • HTML
  • WAI-ARIA
  • CSS
  • JavaScript

These technologies are relied upon for conformance with the accessibility standards used.

Feedback

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)

Assessment Approach

AppWT Web & AI Solutions assessed the accessibility of our website by the following approaches:

  • Self-evaluation
  • External evaluation
  • Automated testing tools
  • Manual testing with assistive technologies

Date

This statement was created on January 15, 2025 using the W3C Accessibility Statement Generator Tool.

Last updated: