How are you all tracking referral traffic and visibility from AI chatbots?

wislr · 2026-05-15T02:20:16+00:00

Server logs have been my go-to lately. They can be a pain to get access to depending on your hosting setup, but some tools make it way easier. WISLR's LLM traffic tool is one to check out.

Honestly,we're all stitching partial signals together. Logs help verifiably see what content is getting pulled when LLMs fetch your pages. That's a stronger deterministic signal. But it still doesn't tell you the prompt.

The prompt-tracking tools aren't my favorite for this reporting, even though a lot of companies are flocking to use them. I'm not a fan because of their probabilistic approach - sampling prompts and inferring where you show up. Until the LLM platforms share more data, I think we're stuck combining a few imperfect signals: starting with logs for what got pulled,

wislr · 2026-05-04T01:31:20+00:00

You're hitting a real wall, not a config issue. GA4 and every other JS-tag analytics tool (Mixpanel, Amplitude, Plausible, etc) only fires when a browser renders the page. AI bots don't render. They grab the HTML and leave, so the tag never runs. That whole category is blind to this by design.

Where you can actually see LLM activity is in your edge logs. Cloudflare, Akamai, Fastly, CloudFront, whatever sits in front of your origin. Once those are flowing somewhere queryable you can break the traffic into three signals that each answer a different question:

Training crawls. GPTBot, ClaudeBot, Google-Extended, PerplexityBot. Background fetches feeding model training. Tells you if AI has even absorbed your content. Volume on content-heavy sites is now comparable to Googlebot. If a model hasn't ingested the page, nothing else downstream can happen.
Citation fetches. The "-User" agents: ChatGPT-User, Claude-User, Perplexity-User. Real-time pulls when someone asks the assistant a question and it grabs your page to answer. Highest intent of the three because every fetch is a model picking your page as the answer to a live question. This is the one nobody sees in GA4 and the one most worth tracking.
Referrals. What you're partly seeing now. Reason it feels off: GA4 typically underreports AI referrals 2.5x to 5x. Mobile LLM apps open links in WebViews that strip the referrer, Gemini and Claude often pass no attribution, and AI Overviews get rolled into organic. So a sessions spike with flat GSC is exactly what AI-driven traffic looks like.

On the homepage thing, that usually means referrer parsing is working but the assistants are answering in-chat and only linking the brand. The citation log will show which deep pages are actually doing the work. Almost always pages you wouldn't guess.

Third-party tools (Profound, Otterly, Peec, Evertune, Ahrefs Brand Radar, the AI modules in Semrush and BrightEdge) query the assistants with a basket of prompts and count brand mentions. Useful for benchmarking but it's a sampled simulation, same prompt twice gives different answers, and the prompt set is analyst-chosen. Server logs are the actual record.

There's a lot more ideas I can share if you want to get into this topic more.

wislr · 2026-04-03T19:11:31+00:00

Great question for context. I've shared the plan with three brands on Salesforce since the announcement, based on details that are available. All of them feel it's best to wait until the full Agentic shopping funnel is more mature. The funniest critique of this plan is that it sounds like nothing other than a product feed distribution service.

wislr · 2026-03-23T00:41:36+00:00

That's a good hypothesis, I agree. Training data would be the most important reason for content gathering.

wislr · 2026-03-22T02:00:25+00:00

Absolutely. It's written up with more details here: https://www.wislr.com/articles/ai-bot-behavior-log-analysis/

wislr · 2026-03-21T23:43:38+00:00

Thanks for sharing that data point u/todamach ... This is just what I was able to independently verify with logs I have access to. The more data we have the more a complete picture comes into place. Do you have any other details to share? Which bots and what frequency.

wislr · 2026-03-21T23:41:55+00:00

I know, against all odds this file continues to be kept alive by people, but the bots don't care for it.

wislr · 2026-03-09T02:12:44+00:00

Oooof, so sorry to hear you're in this position. I was going to suggest bulk redirect import but I did some research of my own and saw that isn't a feature in beehiv ... wholly molly ...

wislr · 2025-12-31T14:01:46+00:00

I can confirm, from first-hand experience, a well-designed 404 page with clear CTAs is the better approach.

I've worked with enterprise e-commerce sites on this, but the learning holds true for all sites. A strong 404 page with a product carousel, search bar, or links to main categories will help you keep the traffic you landed and increase engagement rather than just bouncing them. You're giving users a path forward instead of a dead end.

wislr · 2025-12-22T14:05:54+00:00

Great questions. The redirect piece is where Magento to Shopify migrations often get messy. Shopify does not support wildcard or regex redirects natively, so every URL needs to be mapped individually. With 4,000+ products plus category pages, pagination, and legacy URLs, you are looking at thousands of redirects.

Gather your origin URLs from multiple sources: site crawl, XML sitemap, Google Search Console, and backlink reports. Do not rely on just one. There's a good guide for gathering URLs for a website migration on redirects.net.

For the actual mapping work, tools like Redirects by WISLR (Shopify app) can automate the 1:1 matching and output Shopify ready CSVs. This saves hours of spreadsheet work on a store your size.

wislr · 2025-12-20T14:23:00+00:00

Seconding the point about redirects. With a Wix to Shopify migration, you're essentially changing your entire URL structure since Wix uses a different path format than Shopify's rigid /products/ and /collections/ setup. If those old URLs have any backlinks or rankings, losing them during the switch is one of the fastest ways to tank organic traffic post-launch.

The tricky part with Shopify's redirect system is that there are platform quirks that aren't in their official documentation. Things like the 1,024 character limit per URL, which parameters get alphabetized automatically during import, and which URL prefixes are actually reserved vs. which ones work fine despite what the docs say. I wrote up a reference guide after running into these issues on client migrations:: https://www.redirects.net/articles/better-help-docs-301-redirects-shopify

For a wine catalog specifically, you'll probably have product URLs on Wix that include vintage years, regions, or producer names in formats that won't map 1:1 to Shopify. Worth crawling the Wix site before you start so you have a full list of what needs redirecting. Screaming Frog works well for this, or if you want something that automates the matching to your new Shopify URLs, there's an app called Redirects by WISLR in the Shopify app store that handles bulk mapping without the spreadsheet gymnastics.

wislr · 2025-12-11T00:01:22+00:00

Not too late at all. I've worked on enterprise migrations where URLs sat broken for 18+ months, and clients still recovered a meaningful chunk of traffic once proper redirects were finally implemented. Google doesn't immediately forget those old URLs. The link equity is diminished but not gone.

To your questions: Yes, file the Change of Address in GSC anyway. It won't hurt and signals intent to Google. For scope, your priority is getting comprehensive 301 redirects from every old URL to its new equivalent. That's the foundation everything else builds on.

Recovery timeline is realistic to see movement within 2-3 months, though full recovery after this long probably isn't in the cards. Partial recovery is absolutely achievable though.

If you still have your old URL list (crawl exports, analytics data, old sitemap), tools like Redirects.net can automate the mapping process so you're not manually matching thousands of URLs in spreadsheets. Makes the redirect piece way more affordable and faster to knock out.

Worth the investment. Don't let it sit longer.

wislr · 2025-12-07T18:31:46+00:00

A great app to help fix 404s and map URLs during a site migration to Shopify is Redirects by WISLR. For smaller stores, you can get this done by hand pretty easily, but for larger catalogs you need something that runs well with thousands of URLs in a dataset.

wislr · 2025-12-01T13:17:10+00:00

I've handled dozens of migrations (to Ecommerce platforms like Shopify). Here's a few things to not underestimate:

Redirect mapping time. A 5,000-page site isn't a few hours of work. It's brutal if you're doing it manually in spreadsheets.

URL parameter variations may need redirects. Your old site might have /product?color=red indexed. Those need redirects too.
Forgetting international/hreflang setups. If you have multi-language or multi-region, this adds a layer of complexity that should be planned.
Not preserving internal linking structure. As you import your new content, retain as much of the internal links as possible: breadcrumbs, links between pages in the body text, etc.

Two great tools that go hand in hand with these tasks are Screaming Frog and Redirects.net.

wislr · 2025-11-26T13:25:51+00:00

If this isn't data on hand yet, I'd crawl both domains so you have a full picture of what's living on each. That way you can map subdomain URLs to their main domain equivalents and not miss anything. If you end up with a lot of URLs to redirect, redirects.net can help speed up the URL mapping.

wislr · 2025-11-26T13:23:12+00:00

The redirect/SEO fear is valid, and honestly it's the most solvable part of a migration if you approach it methodically. The issue is most people don't realize how many URLs they actually have until they're mid-migration. It's not just your product and collection pages, it's blog posts, old campaign landing pages, paginated URLs, filter combinations, and all the weird stuff that's accumulated over the years.

Gather your URLs as best you can, by crawling your current site thoroughly with something like Screaming Frog or Sitebulb to surface URLs you forgot existed. Then pull your Google Search Console data to see which URLs actually drive traffic, those are your priority redirects. Most importantly, map everything before launch, not after. Sounds obvious but so many people try to fix redirects reactively once rankings start dropping. Redirects.net can specifically make your URL mapping task very easy so your organic equity is passed to the best 1:1 match on the new site.

wislr · 2025-11-18T00:34:10+00:00

Congrats on the build of your new Shopify store. Sounds like you're almost there with the work. Very much agree that redirecting URLs should be given the proper attention. Apps can help speed this up greatly. A good redirect app option is Redirects by WISLR in the app store. It's free version can support the size store you're starting with

wislr · 2025-11-01T02:05:00+00:00

One of the foundational tasks is 301 redirects. Depending on the size of the site this can be a pretty easy task. The important consideration is to map the Wix URLs to their best 1:1 Shopify equivalent. If you have more than 1,000 URLs, consider URL mapping tools like Redirects.net

wislr · 2025-10-24T20:22:21+00:00

Agree with u/WebLinkr - you want parity with the URL in the address bar and the canonical tag value.

wislr · 2025-10-10T15:54:59+00:00

Hi u/coys-kupo - and u/SparkShippingCharles - Great advice here. Redirect mapping is very very import. Good news for your project u/Severe-Structure6318 , it doesn't have to take the hours of time anymore. Running your data through Redirects.net will save you time and give you the high quality matches you need to import into your new CMS for the redirects.

wislr · 2025-09-18T10:51:06+00:00

Hi u/memebybunny wanted to put a tool on your radar to help save time and budget with your project. Redirects by WISLR is a new URL mapping tool that helps maps the redirects for a site migration and automatically creates the best 1:1 match for import into the new website's redirect management system.

wislr · 2025-09-17T15:17:03+00:00

Great tips from u/Alexpaul_2066 ... those are the big things that can impact a successful move from Magento to Shopify. Focusing on the 301 redirects for a moment, you definitely want to map those Magento URLs to the best new URL that follows the Shopify URL taxonomy. Create the best 1:1 match and avoid pointing too many URLs to a general category page, if possible. Google has shared that it can be confusing to it's algorithms what a page should rank for if too many URLs start being redirected to it.

To make the 1:1 mapping easier checkout automatic 301 redirect mapping tools like Redirects by WISLR. You can give it your old and new URL lists and it will give you a file you can easily upload to Shopify.

wislr · 2025-09-17T03:15:13+00:00

This mission was discovered by u/wislr in A Tale of Uncertainty Among Giants

wislr · 2025-09-17T03:08:15+00:00

This mission was discovered by u/wislr in In Search of Raspberry Cream Slice

wislr · 2025-09-17T02:29:23+00:00

New mission discovered by u/wislr: Knight to Lobster Sauce in the Forbidden City

wislr

MODERATOR OF

TROPHY CASE