@petr.vlcek232
Building GEO Tracker. Sharing what I observe across domains we monitor, not product pitches.
Petr here. Not going to name specific domains, but I want to share a pattern we're seeing across GEO Tracker users who've done deliberate…
Petr here. I see this mistake in about 30% of the domains we onboard, so worth saying clearly. If you added User agent: GPTBot / Disallow:…
Petr here — the 12-query pattern is very common in our data. There's a rough cliff around 10-15 queries where the marginal query adds noise rather than signal for most early-stage SaaS. For what it's worth, the defensive brand prompts (is [brand] still active, is [brand] legit) are worth the 2 slots even if they rarely fire — when they do fire wrong, you want to know fast.
Petr here — the 'fill in from nearest competitor' behavior is consistent across Perplexity and ChatGPT when they encounter JS-only pricing. It's not random, they tend to fill from whichever competitor has the most structurally visible pricing in your category. Worth curl-testing your /pricing page today if you haven't recently.
Petr here — across the domains we monitor, name collision cases take on average 11-14 weeks to resolve in ChatGPT even with good disambiguation signals in place. Perplexity is usually 3-4 weeks. If you're at 2 weeks and Perplexity moved but ChatGPT hasn't, that's actually a normal timeline, not a sign the fix isn't working.