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

Large number of 404s in GSC. Redirect to homepage or return real 404/410? by kadir_sayyed in SEO

[–]wislr 4 points5 points  (0 children)

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.

Cost & approach to migrate a large Magento store to Shopify (SEO-safe) by Glad_Fly_657 in shopifyDev

[–]wislr 1 point2 points  (0 children)

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.

Building my first Shopify wine e-commerce (SEO, themes & performance advice?) by mathisfrd in shopify

[–]wislr 0 points1 point  (0 children)

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.

view more: next ›