---
title: "Hafiz Waleed Ahmed (@hafizwaleedahmed5) | Hashnode"
description: "Web Developer & Marketing Manager | SEO, Web Development & AI. Read the latest articles by Hafiz Waleed Ahmed on Hashnode."
url: "https://hashnode.com/@hafizwaleedahmed5"
---

@hafizwaleedahmed5

# Hafiz Waleed Ahmed

@hafizwaleedahmed5 · Sharaqpur Sharif, Punjab, Pakistan · Joined October 2026

Web Developer & Marketing Manager | SEO, Web Development & AI

[Website](https://www.youtube.com/@hafizwaleedahmed5)

## Comments

[Splitting crawlers into training, search, and user-triggered jobs is the part most robots.txt files get wrong. Blocking GPTBot does not block OAI-SearchBot, so a site can drop out of ChatGPT answers while still being eligible for training, or the reverse. The named-group trap is easy to miss: once GPTBot has its own group, it ignores User-agent: \* and can reach paths you only disallowed there. Repeating private paths inside every named group, and treating robots.txt as a request rather than a lock for user-triggered fetchers, is the checklist I would run before publishing the file.](https://hashnode.com/posts/robots-txt-rules-for-gptbot-claudebot-and-perplexitybot/6b0203b8bf4508e1a2d7a528/comment/6b02a5abfa93654d05300848)

Comment · Article · 11m ago · [robots.txt rules for GPTBot, ClaudeBot and PerplexityBot](https://hashnode.com/posts/robots-txt-rules-for-gptbot-claudebot-and-perplexitybot/6b0203b8bf4508e1a2d7a528)

[The useful part is treating the user agent as the source of truth, not screen size or navigator.webdriver. Meta's crawlers render like a normal desktop Chrome, so a filter that only drops HeadlessChrome or webdriver=true will keep counting them as people. Matching the crawler token before the analytics beacon, and reusing that same pattern on older queries, keeps live traffic and dashboards aligned. It is also worth testing the regex against real device names so a loose "bot" match does not drop phones such as Cubot.](https://hashnode.com/posts/meta-externalagent-webindexer-analytics/6b02700936535fe8c8d4b748/comment/6b02a598bf10f5aed4c1234e)

Comment · Article · 11m ago · [meta-externalagent and meta-webindexer: crawlers were a third of my visitors](https://hashnode.com/posts/meta-externalagent-webindexer-analytics/6b02700936535fe8c8d4b748)

[Separating named from cited, and keeping the by-name questions out of the headline number, is what makes the 4 of 72 figure readable. A trend only works if the original questions stay fixed, which you called out, because a reword hides whether the assistant changed or the prompt did. The cost jump when Claude search results come back as input tokens is a useful warning if someone starts from a cheap first estimate.](https://hashnode.com/posts/do-ai-assistants-recommend-your-app-i-built-a-small-weekly-tracker-to-find-out/6b00ffad8ef3e6ec53a2746b/comment/6b01539926b829fc64b359de)

Comment · Article · 1d ago · [Do AI assistants recommend your app? I built a small weekly tracker to find out](https://hashnode.com/posts/do-ai-assistants-recommend-your-app-i-built-a-small-weekly-tracker-to-find-out/6b00ffad8ef3e6ec53a2746b)

[The confirmed versus verify split is the part that stands out. Treating a fuzzy signal as a half deduction, and showing the evidence, is more honest than a flat fail, especially on keyword-stuffed names. The live Maps bugs you listed, non-US domains, European review counts, and the Visited link suffix, are a useful reminder that content scripts have to be tested on the real page, not just with unit tests.](https://hashnode.com/posts/i-built-and-shipped-a-paid-chrome-extension-for-local-seo-here-s-the-stack-and-what-i-learned/6b011321caef1967c8e2f4cb/comment/6b015350c66cad906dc724ad)

Comment · Article · 1d ago · [I built and shipped a paid Chrome extension for local SEO: here's the stack and what I learned](https://hashnode.com/posts/i-built-and-shipped-a-paid-chrome-extension-for-local-seo-here-s-the-stack-and-what-i-learned/6b011321caef1967c8e2f4cb)

[That single-hop point is a good addition. Dropping the query string, or bouncing between www and non-www or a separate http to https hop, is the kind of chain that can leave the visit looking like Direct. I did not split blank referrers by mobile versus desktop in this article, so I would not claim a bigger mobile share from it. If the gap looks uneven, it is worth checking the device reports on their own.](https://hashnode.com/posts/why-your-analytics-never-matches-search-console-how-to-spot-google-search-traffic/6afb017b905c9945f096660b/comment/6afcd3caeabc6e7573e041a7#reply-6b01530e69c11d9c3bec0734)

Reply · Article · 1d ago · [Why Your Analytics Never Matches Search Console: How to Spot Google Search Traffic](https://hashnode.com/posts/why-your-analytics-never-matches-search-console-how-to-spot-google-search-traffic/6afb017b905c9945f096660b)
