A notebook site is a faster way to make research readable. It is not a substitute for synthesis, and it is not a website for your product.
Gemini Notebook sites for designers: what shipped and how to use it
Gemini Notebook sites for designers is a quick way to turn a pile of research (interview notes, survey exports, competitor teardowns, a brief) into a small interactive page that a team can click through instead of scroll past. Google released it on 16 November 2026, according to its official announcement, Transform notes, research, and sources into interactive sites with Gemini Notebook. You type "make me a site" in the notebook chat, describe what you want, and Gemini builds it from the sources already in that notebook.
The honest pitch for designers is narrow and practical. It is a research communication tool, not a website builder and not a prototyping tool for your product. Use it to make findings explorable for stakeholders, to sketch an information structure from real content, and to keep a lightweight project tracker next to the evidence. Do not ship what it makes to customers.
What Google actually shipped
Everything below comes from the official Google post. It is a short announcement, so the list of what is not stated matters as much as what is.
How to start: type "make me a site" in your Gemini Notebook chat with a description of what you want to build.
Examples Google gives: visual explainers such as an interactive periodic table or a historical timeline, interactive dashboards to explore data such as quarterly sales, and project management trackers for tasks and deadlines.
Viewing and sharing: once built, choose "Open in a new tab" to interact with it, or share it with others.
Availability: rolling out globally on the web for Gemini Notebook users aged 18 and over, including Google Workspace subscribers. The mobile app is listed as coming soon.
What Google has not published: which model builds the sites, usage limits, whether there is extra cost, how sharing permissions work in detail, and whether you can export the code. Treat each of those as unknown until Google documents them, and check your workspace admin settings before you share anything built from client material.
Hype vs reality
The hype reading is that research tools now build websites, so the designer who makes the readout is redundant. The reality is closer to this: the slowest part of a research readout is not the findings. It is turning findings into a format people will actually open. A clickable timeline of a customer journey, or a filterable view of interview quotes by theme, gets more attention than a forty-slide deck. Gemini Notebook now produces that format in minutes.
What does not hold up is the idea that the site is the insight. The site can only arrange what is in your sources. If the notes are thin, biased or badly tagged, you get a polished page built on weak evidence, and polish makes weak evidence more persuasive, not less. That is the real risk for design teams. Verdict: useful for communication and early structure, dangerous as a substitute for synthesis.
A five-step playbook for designers
1. Build a clean notebook first
Add only sources you would defend in a review: interview notes with participant codes instead of names, the research plan, the brief, survey exports, analytics summaries. Remove drafts and duplicates. The quality of the site follows the quality of the notebook, and personal data you add can travel into anything you share.
2. Ask for one job, not a website
A good prompt names the audience, the decision and the structure. For example: "Make me a site for the product team that shows the onboarding journey as a five-stage timeline. For each stage, show the top pain points with the supporting quote and the participant code. Add a filter by user segment." Vague prompts ("make a site about our research") give generic pages.
3. Pick the format that fits the question
Research question | Site format to ask for | What to check before sharing |
|---|---|---|
Where does the journey break? | Journey timeline with stages and quotes | Every quote matches a real source line |
Which segments behave differently? | Dashboard with filters by segment | Numbers match the original export, no rounding drift |
What did competitors ship? | Comparison explainer with feature rows | Each claim links to a dated public source |
What is left to do this sprint? | Project tracker with owners and deadlines | Owners and dates reflect the real plan |
How should the content be organised? | Explainer with sections and navigation | Labels reflect user language, not model language |
4. Verify like a reviewer, not a fan
Open it in a new tab and click everything. Check each quote against its source, each number against the original file, and each label against the words participants actually used. Generated dashboards are where small errors hide best, because a clean chart looks trustworthy whether or not the number behind it is right.
5. Move the structure into your real tools
When the site reveals a good structure (a navigation model, a way to group features, a dashboard layout people understood), rebuild it properly in Figma or code with your design system. The notebook site is evidence for a decision, not the deliverable. If you want a related workflow for messier early thinking, the Claude Whiteboards workflow for designers covers clustering before you have clean sources, and the guide to AI prototyping for product teams covers the step after.
Where it fails
It fails when the sources are the problem. It fails when the audience needs accessibility guarantees, since Google has not documented accessibility behaviour for generated sites. It fails as a client deliverable, because you cannot yet say where the site is hosted, how long a share link lives, or who else can see it. And it fails for anything that needs your brand, components or real product interactions. For those, you still need proper UI/UX design services or a coded prototype.
Where design work is going
Over the next one to three years, research tools, document tools and design tools are converging on the same idea: any body of knowledge can be rendered as an interface on demand. Readouts, specs and onboarding docs will increasingly arrive as small generated apps rather than files. That pushes designers toward two jobs: curating what the model is allowed to know, and setting the rules for how generated interfaces should look and behave. The second job is the same one that appears in generative UI, just applied to internal tools first.
Teams building products on top of this pattern, with sources, retrieval and generated views, are doing AI product development, and the design questions (trust, verification, provenance) are identical to the ones in this playbook.
The fear, answered
If you spend a large part of your week building research decks, some of that work is going away. The layout part is the easiest part to automate. What is not going away is deciding what the research means, which finding should change the roadmap, and how to say it so a team acts on it. Designers who move up to synthesis and decision framing become more valuable when the formatting is free. Designers who only format do not.
The concrete next move: run one real readout through Gemini Notebook this week, verify it line by line, and note where it was wrong. That list is your edge.
FAQ
Can Gemini Notebook build a real website for my product?
No. Google positions it for explainers, dashboards and trackers built from notebook sources. It has not documented custom domains, code export, brand controls or accessibility behaviour, so use it for internal communication and early structure, not for a customer-facing site.
Is Gemini Notebook interactive sites free?
Google's announcement does not mention pricing or usage limits. It says the feature is rolling out on the web to Gemini Notebook users aged 18 and over, including Google Workspace subscribers. Check your own plan and admin settings.
Will AI research tools replace UX designers?
They replace formatting, not judgement. A notebook site can arrange findings, but it cannot decide which finding matters or whether the evidence is strong enough to act on. Designers who own synthesis and decisions gain time; those who only produce readouts should shift toward that work now.
Is Gemini Notebook sites overhyped?
Partly. It is genuinely fast for turning sources into something clickable, and that improves how research gets read. It is overhyped if people treat the generated page as the analysis. The output is only as good as the sources and your verification.
How do I keep client research safe when sharing a notebook site?
Remove names and personal details before adding sources, check your Workspace sharing rules, and share with named people rather than broadly. Google has not published detailed sharing controls for sites yet, so assume anything shared can be forwarded.
Getting help with the part AI cannot do
Generated research sites make the readout faster. Turning those findings into a product people trust is still design work. If you want a team that pairs AI speed with careful product thinking, talk to a UI/UX agency in Casablanca that works with clients globally: DIGCY is a Dribbble Selected Agency with 50+ projects delivered, and you can start a conversation through the DIGCY contact page.
Let’s keep in touch.
Discover more about high-performance web design. Follow us on Twitter and Instagram.




