If a source is missing from your notebook, first find the stage that failed: extracting the page, saving it in the Toolkit library, or sending it to Google. Do not repeatedly click Send before checking the destination. A delayed result can look like a failure and repeated attempts can create duplicates.
This guide covers the extension-to-notebook workflow. It does not promise to fix a Google service outage, bypass a paywall or recover content that was never captured.
Identify where the source stopped
| What you see | Check next |
|---|---|
| Empty or irrelevant capture preview | Open the original page and inspect the readable text |
| Preview looks correct, but no library item | Check the save result, selected workspace and account limits |
| Library item exists, but not in the notebook | Check the notebook tab, account and send result |
| A request is still running | Wait and inspect the destination before retrying |
| Source appears twice | Stop sending and compare the entries before removing anything |
Check the page and permissions
Open the original page in the same browser profile as the extension. If you see a sign-in screen, the extractor may see that screen too. Sign in yourself where appropriate, or use accessible material you are permitted to process. If you only need one paragraph, capturing selected text can produce a cleaner source than taking the entire page.
Supported sites have their own access requirements. Broader all-site capture is optional; enabling it does not make every page readable. Browser-internal pages, restricted documents and content without usable text may not work. Review site access and permissions before changing settings.
Check the destination, not just the browser window
- 1Open the notebook you actually want to use, not only its home dashboard.
- 2Confirm the signed-in Google account has access to that notebook.
- 3Keep that notebook open while sending the source.
- 4Inspect the result and look for the new source in the destination.
- 5If you updated the extension while the tab was already open, refresh the notebook tab before a new attempt.
The extension supports both notebook.google.com and the older notebooklm.google.com address. The address alone does not identify the right notebook or account. Google describes the product rename in its official announcement.
Retry one item first
After correcting the likely cause, try a single small, public source. If it arrives, continue with a small batch. Check each failed item separately rather than resending everything. Local exports and cloud captures are different operations; upgrading a Toolkit plan does not remove Google's own restrictions. Review current plan limits.
Ask for help without exposing research
Send support the extension version, the stage that failed, the visible error message and whether the problem occurs with a harmless public page. Do not send passwords, account tokens or private source contents. A redacted screenshot can help if it does not contain confidential information. Contact support, then use the research-readiness checklist before your next batch.