ChatGPT Knows Your Company but Google Doesn't: Step-by-Step Guide to Diagnosing AI Visibility Issues
The complaint “we are not in the neural networks” is not a single diagnosis but a symptom of at least six different failures, each fixed by contradictory actions. A model may simply never have learned the brand. A search crawler may be receiving an immediate refusal. A single line in a page template may be blocking the text from being used in a generative answer. A page may be indexed yet consistently lose to competitors during source selection. A system may mention the company without a link. Traffic may arrive yet disappear into “direct” visits.
Verification is required to turn the complaint into concrete diagnoses. The recommended workflow measures what needs to be measured, in what order, with which tool, and how to avoid mistaking noise for signal. A complete first pass takes one working day and requires no paid services.
Three separate layers produce the same-looking answer
Model knowledge is tested by asking questions with search disabled. The fact that ChatGPT knows a company does not prove the site itself was in the training set; the information may have arrived from third-party publications.
Search layer crawlers such as OAI-SearchBot, Claude-SearchBot and PerplexityBot fetch pages in advance and can cite them with links. Their activity is visible only in server logs and in “search-enabled” mode.
Agent layer bots such as ChatGPT-User, Claude-User and Perplexity-User open specific URLs on user request. Only server logs can confirm their visits; robots.txt rules may not apply.
Mixing the layers in one table is pointless. Blocking a search bot will not fix stale model knowledge, and an analytics report will not update outdated training data.
Step-by-step verification
Step 1. Disable search, open a fresh dialogue without memory, and ask about the company, products, people, prices and specifications. Record concrete factual errors and the competitors named instead of you.
Step 2. Examine 30 days of server logs. Separate requests by purpose (training, indexing, user-directed agents, maintenance). Persistent 403 responses for named AI crawlers indicate access problems; repeated 429 responses indicate rate limiting.
Step 3. Audit four locations that commonly suppress AI usage: page-level meta tags (nosnippet, data-nosnippet, max-snippet:0), robots.txt entries for each distinct agent name, Cloudflare AI-bot toggles (Search / Agent / Training), and the new generative-functions switch in Google Search Console.
Step 4. Disable JavaScript and confirm that title, main text, date, author and internal links remain visible. If core content loads only after rendering, some AI systems will see an empty page.
Step 5. Run at least 20 user-style questions, each three times, separately with and without search. Track six metrics independently: mention rate, linked citations, source ranking, factual accuracy, freshness and competitive share.
Step 6. Pull the new “Visibility in Alice AI” report from Yandex Webmaster and the generative-functions report from Google Search Console.
Step 7. Verify that utm_source=chatgpt.com tags and the new AI Assistant channel in Google Analytics are correctly attributed; roughly 70 % of AI referrals currently arrive as direct traffic.
Step 8. Review content and auto-generated files for hidden instructions aimed at agents. Malicious prompt-style directives have been observed in HTTP headers, comments, structured data and metadata.
After completing the checklist, the generic complaint “we are invisible to AI” is replaced by specific, actionable diagnoses with different timelines and costs.
Related articles
Yandex Black October: How Architectural Flaws and Capacity Mismanagement Turned Data Center Losses Into a 11-Day Fintech Coma
In October 2026 three Yandex data centers in Central Russia were physically destroyed within days, triggering the collapse of Yandex Cloud and multiple core services. Between the first and third site failures engineers had 74 hours to restore quorum and rebalance workloads yet failed to do so because Control Plane components remained tied to the lost zone and spare capacity had been eliminated to cut costs. Core banking and BNPL systems entered Read-Only mode after losing quorum, forcing a complete stop-the-world reconciliation that lasted until 22 October. Backups stored inside the same regional S3 buckets proved unusable, resulting in a seven-day RPO and primary-key collisions after restoration. The incident exposed that Metro-Cluster designs had been incorrectly treated as full Disaster Recovery and that aggressive AP microservice patterns created logical split-brain conditions outside the database layer.
Astra Group Releases Low-Code Astra AI Platform for Building Corporate AI Agents in Closed Environments
Astra Group has launched the Astra AI Platform, a low-code constructor designed for creating corporate AI applications that operate entirely within closed circuits without reliance on foreign clouds. The platform targets small and medium businesses as well as large corporations, enabling rapid deployment of AI secretaries, technical support assistants, and other agents in days rather than months. It forms part of the broader Astra AI ecosystem and includes two main constructors: one for machine learning model training and deployment, and another for LLM-based language assistants, document search, and process automation. Users can assemble scenarios from visual blocks, debug them in real time, or extend functionality with custom Python code when needed. The solution supports RAG-based knowledge bases, integration with external tools such as CRM and ERP systems, and the coordination of multiple agents for distributed task handling. One demonstrated use case involves processing ten pages of engineering drawings and specifications in five minutes to prepare data for downstream systems. The product is already listed in the Russian domestic software registry and available to customers.
Multi-Tenancy Isolation in VictoriaMetrics, VictoriaLogs and Grafana: Building Client Separation in a Shared Stack
Voltir runs a single shared monitoring stack consisting of VictoriaMetrics, VictoriaLogs, Grafana and vmalert for all customers instead of deploying separate instances per tenant. Isolation relies on numeric account IDs enforced at every layer: nginx validates tokens against the platform API before proxying writes, Grafana data sources hard-code tenant accounts, and vmalert rules receive automatic account filters. The team discovered that a single malformed rule or template could break alerting for every tenant because vmalert loads the entire rules directory at once. They also found that Grafana automatically created personal organizations granting Org Admin rights, accumulating hundreds of orphaned organizations and users that consumed disk space and resources. A dedicated cleanup module plus hourly reconciliation now removes rules, organizations, series and users when a tenant is deleted, while isolation tests verify both data and API objects across tenants.
The Real Costs of Using Claude and GPT for Russian Businesses Exposed
Accessing generative AI models like Claude and GPT has become straightforward for Russian companies, yet calculating their true expenses remains complex. Hidden factors such as intermediary commissions, currency conversion rates, taxes, and the often-overlooked costs of model reasoning tokens can double or triple initial estimates. Founder Vitaly Nagay of the Heli service analyzed these financial and organizational risks for Russian firms relying on foreign AI providers. In one example, a support department processing 20,000 monthly queries sees costs rise from $240 to $480 when reasoning tokens are included. Nagay recommends evaluating providers by dividing actual ruble charges by the model's official dollar pricing to reveal hidden markups. Additional concerns involve data control, document compliance, and access history when employees use personal subscriptions. Companies are advised to verify billing details, data storage policies, and issue dedicated API keys with spending limits before procurement.