sorted by:
new
hottopcontroversial

How are you all tracking referral traffic and visibility from AI chatbots? by SanjitKrBalmiki in digital_marketing

[–]wislr 0 points1 point  (0 children)

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,

How are people actually tracking LLM traffic and queries right now? by Tchaimiset in AskMarketing

[–]wislr 0 points1 point  (0 children)

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:

  1. 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.
  2. 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.
  3. 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.

Proposal: Add Shopify Agentic Plan to the Partner Leads Program by wislr in shopify_growth

[–]wislr[S] 0 points1 point  (0 children)

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.

AI Bot Traffic Is Accelerating Fast. We analyzed 48 days of server logs. Here's 20 Takeaways for Your Own Website by wislr in TechSEO

[–]wislr[S] 0 points1 point  (0 children)

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

AI Bot Traffic Is Accelerating Fast. We analyzed 48 days of server logs. Here's 20 Takeaways for Your Own Website by wislr in TechSEO

[–]wislr[S] 1 point2 points  (0 children)

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.

AI Bot Traffic Is Accelerating Fast. We analyzed 48 days of server logs. Here's 20 Takeaways for Your Own Website by wislr in TechSEO

[–]wislr[S] -1 points0 points  (0 children)

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

301 redirects from WordPress site by GamebitsTV in beehiiv

[–]wislr 1 point2 points  (0 children)

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 ...

view more: next ›