---
title: "Aldo (@aldoquantic) | Hashnode"
description: "Building web data & SERP APIs for AI agents. Read the latest articles by Aldo on Hashnode."
url: "https://hashnode.com/@aldoquantic"
---

@aldoquantic

# Aldo

@aldoquantic · Joined November 2026

Building web data & SERP APIs for AI agents

## Comments

[One useful extra control is to treat each query run as a sample, not a verdict: hold wording, locale, language, signed-in state, and mode constant, then repeat the same prompt across several days. Save the exact prompt and timestamp alongside the cited URLs, not only the brand mention, since a citation to the page you’re evaluating is a different outcome from a mention or a homepage link. I’d compare citation frequency and source overlap over a rolling window; for technical queries, verify each cited claim against the primary documentation. This makes the five-query test much easier to reproduce when answers fluctuate.](https://hashnode.com/posts/perplexity-vs-chatgpt-search-vs-google-ai-mode/6af7c6748cbf6d1eb5394e97/comment/6af83b48ec7b027a28806c17)

Comment · Article · 3d ago · [AI Search Showdown: Perplexity vs ChatGPT Search vs Google AI Mode](https://hashnode.com/posts/perplexity-vs-chatgpt-search-vs-google-ai-mode/6af7c6748cbf6d1eb5394e97)

[The 16-of-32 to 12-of-32 example needs a within-week baseline before I'd call it a real loss. Those 32 answers combine different prompts and engines, and one generation per cell can move quite a bit without anything changing on the site. I'd repeat each fixed prompt a few times in fresh sessions, retain the answers and citations, then compare mention frequency per engine and prompt. Record search mode, locale and the model/version when exposed. Keep “recommended by name”, “linked as a source” and “described accurately” as separate columns; a brand can lose a citation without disappearing from the recommendation. Also, “why didn't you include us?” is a follow-up generated explanation, not an execution trace of the original answer. It can suggest things to verify, but shouldn't establish the cause of the drop. For a team building its own monitoring pipeline, QuanticData's AI Visibility API is worth evaluating alongside a manual baseline; I work on QuanticData. I'd still validate automated observations against the particular consumer/search experience the team actually cares about, rather than treating every API answer as identical to that UI.](https://hashnode.com/posts/how-to-know-when-chatgpt-stops-recommending-your-product/6af5bc2decc4c89b789822ba/comment/6af651d40aa4ca2c7b95ba89)

Comment · Article · 4d ago · [How to Know When ChatGPT Stops Recommending Your Product](https://hashnode.com/posts/how-to-know-when-chatgpt-stops-recommending-your-product/6af5bc2decc4c89b789822ba)

[One thing I'd make explicit in the dataset docs: are the keyword/country rows requested independently, or as a shared comparison? Trends' 0–100 scale is relative to the query context. Two independently normalized series peaking at 100 don't imply equal demand, and the same applies to comparing countries. An optional shared anchor term, with the exact geography/timeframe/category/search property retained, would make the competitor-comparison use case much safer. On the reliability side, distinguishing a legitimate low-volume/empty series from a transport failure would help consumers too. Otherwise a rerun can quietly turn “no data” into zero interest. I'd keep a status alongside the series and cache successful keyword/parameter combinations so a retry of a large batch only does the missing work.](https://hashnode.com/posts/pull-google-trends-for-hundreds-of-keywords-without-the-429s/6af5c89b5a4a19e78bb478e2/comment/6af61c1d574443422daee81a)

Comment · Article · 4d ago · [Pull Google Trends for hundreds of keywords without the 429s](https://hashnode.com/posts/pull-google-trends-for-hundreds-of-keywords-without-the-429s/6af5c89b5a4a19e78bb478e2)

[I would separate training permission from search eligibility in the conclusions. GPTBot and OAI-SearchBot have different jobs: blocking GPTBot is not a guarantee of zero ChatGPT search traffic. A browser-UA fetch of robots.txt also cannot establish what the CDN serves to the actual crawler. For a follow-up, test representative cited URLs rather than only homepages, include OAI-SearchBot, and accept sitemap indexes as well as urlsets. Then measure citations on a fixed prompt set separately from those access checks. That would make the comparison much stronger without treating llms.txt as a ranking requirement. I work on QuanticData, where we have an AI crawler checker. Keeping a rules check separate from evidence of a real bot visit or citation is an important distinction for this kind of audit.](https://hashnode.com/posts/i-checked-30-top-websites-for-ai-crawler-readiness-the-ones-chatgpt-cites-most-scored-worst/6af52b98b9e8f367e65ec56a/comment/6af5b89c7928a346d67e9ed4)

Comment · Article · 5d ago · [I checked 30 top websites for AI-crawler readiness. The ones ChatGPT cites most scored worst.](https://hashnode.com/posts/i-checked-30-top-websites-for-ai-crawler-readiness-the-ones-chatgpt-cites-most-scored-worst/6af52b98b9e8f367e65ec56a)
