Skip to main content
Zhihe Growth 中文
Platform updates · Google Crawling

NotebookLM Renaming and Google-GeminiNotebook: Identifying the User-Agent

On July 16, 2026, Google documented the change from the NotebookLM user-agent name to Google-GeminiNotebook, retaining the old value during transition. Update logs and security rules, but do not count a Notebook request as Google Search crawling or an AI citation.

Author: Zhihe Growth Research Center Original publication: Date of event/observation: Sources checked: 2026-07-22

Key Takeaway

Classify Google-GeminiNotebook separately as user-triggered retrieval. Support the documented transition, but keep search indexing, training controls and user-imported research distinct. A Gemini name does not make the request equivalent to Googlebot or Google-Extended.

What's the official change?

Google Crawling Infrastructure's July 16, 2026 changelog renamed the NotebookLM user agent Google-GeminiNotebook following the product's rename to Gemini Notebook. Google said the old value would remain supported for a smooth transition; logs may therefore contain both during that period.

This is a naming change, not a change in Google Search indexing eligibility. Notebook tools retrieve sources in user-directed workflows, unlike continuous search crawling. Check the specific product documentation and company policy for robots behavior and any user-request exceptions.

Documentation update 2026-07-16
New identifier Google-GeminiNotebook
Transitional arrangements Old identifier supported during transition

Implications for International Brands

The identifier can help distinguish retrieval of knowledge pages, white papers and research imported into notebook tools. It may indicate user-directed use, but does not establish a public AI citation or organic-search impression.

Rules matching only the old name may eventually block legitimate requests; matching only the new name may miss transitional traffic. Recognize both where appropriate, record the migration window and verify origins using Google's applicable official methods and request behavior.

Public research should remain attributable through stable URLs, titles, authors, dates, versions and sources. Do not expose sensitive documents, customer data or internal reports for convenience. Access policy takes priority over GEO visibility.

Zhihe Growth's Assessment

Zhihe Growth recommends a separate user-triggered category in AI access records. It differs from continuous crawling and training permission. Record verified request volume and popular paths, but do not present them as platform recommendation data.

Check whether evidence pages work independently of site navigation: each should identify the company, scope, update history, original evidence and contact path. Agents and notebook tools may consume one page at a time.

Implementation Checklist

  1. 1. Add Google-GeminiNotebook to log classification while retaining the old NotebookLM identifier for the documented transition.
  2. 2. Check for WAF false positives caused by the rename and continue verifying request origins.
  3. 3. Record user-triggered retrieval separately from Googlebot requests, Google-Extended policy and other Gemini activity.
  4. 4. Check that public research pages include authorship, versions, sources, company identity and limitations.
  5. 5. Keep private documents, customer data and download endpoints protected by authentication and authorization.
  6. 6. Check logs and official guidance before retiring old rules after the transition.

Limitations

A user-agent string proves only that a request carried that string. It does not establish authenticity, a particular user's action, indexing or an AI citation.

The old identifier's support period may change. Follow the official changelog and do not promise a fixed compatibility deadline.

Official sources