Securitylab•August 28, 2026•🇷🇺Translated from Russian

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

AntiMalware•Other

Survey Shows 42% of Organizations Unify Multi-Vendor Security Tools into Single Protection Contour

A live AM Live broadcast on cybersecurity ecosystems revealed that 42% of participants have already combined solutions from multiple vendors into one unified security contour. Another 23% reported partial integration of tools, while 24% keep their protections operating independently and only 11% rely exclusively on a single vendor. Panelists emphasized the need for clear responsibility assignment, seamless data exchange, and formation of shared security context across products. Key selection criteria for ecosystems included breadth of product lines for 32% of viewers and discounts or bonuses for 28%. Experts advised practical testing of interoperability and evaluation of total cost of ownership before committing to any model. Service provider responsibilities for integration, SLA compliance, and outcomes must be defined in advance, according to CURATOR director Edgar Mikaelyan. After the session, 32% of attendees stated plans to launch or expand a security ecosystem project.

AntiMalware•Other

Yandex Tests Compass Device for Taxi Navigation During GPS Outages

Yandex is conducting trials of a compact Compass device in 10,000 taxis connected to its service to maintain accurate vehicle positioning when GPS signals are lost or jammed. The device connects to the OBD diagnostic port and pulls wheel speed data via the CAN bus while using its built-in gyroscope and accelerometer to determine direction of travel. These readings are sent over Bluetooth to the Yandex Pro driver app, which combines them with the last known GPS coordinates and frequent Wi-Fi access point scans to update the map in real time. The initiative addresses ongoing navigation problems that have affected Russian cities since spring 2022 and have been compounded by regular mobile internet outages since spring 2025. Earlier, Yandex tested a similar OBD-connected gadget called Yandex Pathfinder in 2023. The company has not disclosed timelines for completing the current trial or rolling the solution out more widely, though it plans to make Compass available to ordinary drivers later. Yandex navigation apps have also offered an offline step-by-step routing mode since 2025.

Habr•Other

Apple Attributes Widespread Service Outage to Faulty Internal IT Update

Apple has confirmed that the large-scale outage affecting its systems and user services on November 17, 2026, was caused by an incorrect internal update within the company's IT infrastructure. The incident impacted multiple consumer-facing services including the App Store, iCloud, Apple Pay, and Apple ID authentication. Users reported inability to download applications, sign in to accounts, or activate devices during the disruption. Internal corporate tools such as AppleWeb, AppleConnect, employee VPN access, corporate calendars, and the internal incident-tracking site were also taken offline. Retail operations in Apple Stores worldwide experienced interruptions to sales, repairs, and customer service processes. Company engineers restored most systems within four hours and stated they were working to return remaining services to normal operation as quickly as possible. Apple explicitly ruled out any external cyberattack or third-party interference as the cause of the outage.

Habr•Other

Global Outage Disrupts Apple Services Including App Store, iCloud and Apple Pay

On November 17, 2026, widespread disruptions affected multiple Apple services worldwide, including the App Store, iCloud, Apple Pay, and Apple ID authentication systems. The incident impacted users attempting to download applications on iPhone devices, sign into accounts, or activate new hardware. Apple confirmed problems with Apple Music and App Store functionality, along with performance degradation or complete unavailability of iCloud for all users. The outage was explicitly stated as unrelated to any country-level internet traffic filtering or restrictions. Service interruptions prevented normal operation of cloud storage, music streaming, and payment processing features tied to Apple ID. No official timeline for full restoration was provided in the initial reports from the company.