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
redb.Identity Adds gRPC Transport for OpenID Server Alongside Existing HTTP Facade
redb.Identity has introduced a second transport layer using gRPC next to its existing HTTP interface, sharing the same core routes, client registry, token store, and authorization logic. The new facade exposes standard OAuth and OpenID Connect operations such as Token, Introspect, Revoke, UserInfo, Discovery, and Jwks through protobuf-defined methods under identity.v1.Identity. Both transports enforce identical verdicts based on a single centralized scope table located behind direct-vm addresses, ensuring that a client authorized via HTTP receives the same result when calling gRPC. Error handling on gRPC uses status codes and trailers to carry machine-readable OAuth error codes and retry-after values, preserving compatibility with existing interceptors and tracing. Browser-facing flows, DPoP proofs, and user self-service remain on HTTP, while administrative operations are available on a separate management port. The implementation was validated through 64 unit tests, cross-language interop with @grpc/grpc-js clients, and a conformance run against the official OpenID Foundation suite.
Nvidia to Cease Regular GeForce Driver Updates for Windows 10 After October 2026
Nvidia has announced the end of regular driver support for Windows 10 in its GeForce Game Ready and Nvidia Studio driver lines starting October 2026. The first driver package without Windows 10 support will arrive in November of that year. Microsoft ended the base lifecycle of Windows 10 on October 14, 2025, and Nvidia is extending support by one additional year. Existing games and applications will continue to function after the change, while quarterly security patches for critical vulnerabilities will remain available until October 2029. Users will no longer receive optimizations for new games, fixes for graphics issues, or new GPU features. Newer technologies such as DLSS may also skip Windows 10 compatibility. The transition is described as gradual rather than abrupt, allowing older titles to keep running while newer releases increasingly encourage migration to a supported Windows version.
Rospotrebnadzor Introduces Age-Based Screen Time Limits for Russian School Students
Russia's consumer protection agency Rospotrebnadzor has established recommended maximum durations for schoolchildren working with computers and interactive whiteboards during lessons. The limits vary by grade, ranging from 20 minutes for first and second graders up to 35 minutes for students in grades 10 and 11. Separate rules apply to interactive boards, capping usage at 20 minutes for children under 10 and 30 minutes for older students. Schools must ensure students perform eye exercises when electronic devices are used, while traditional paper-based classes require such exercises only during breaks. Starting September 1 2026, a nationwide ban on mobile phones during lessons will also take effect, with individual schools deciding rules for recess periods.
From Root CA to User Authorization in nginx and Apache: Client Certificate Login Explained
This is the third installment in a detailed tutorial series covering the deployment of a two-tier PKI infrastructure with Root CA and intermediate CAs for Person, Server, and Code. The article provides comprehensive configuration guidance for enabling mTLS in nginx and Apache, including full references for all ssl_client_* variables and SSL directives. It explains the differences between password-based and certificate-based authentication, the TLS handshake steps involving CertificateRequest and CertificateVerify, and the importance of proper extendedKeyUsage settings such as clientAuth. Readers learn how to issue client certificates, package them in PKCS#12 format, enforce revocation checks via CRL and OCSP, and safely pass certificate fields to backend applications while mitigating risks from header spoofing. The guide also covers scenarios where the application itself terminates TLS without a reverse proxy and demonstrates login flows protected against CSRF using one-time tokens.