On this page · 12 sections
- What changed between 17 and 19 November 2026
- Temporary threads: what Google says, point by point
- What Google has not said
- Why personalisation matters, and what temporary threads switch off
- Attribution and referrers: what reaches your analytics
- Measurement plan for the next 30 days (US and UK)
- Worked example: isolating a desktop sidebar effect
- Decision table: what to do, by team
- Rank tracking and query mix: what to expect
- US and UK notes
- How eCorpIT can help
- References
Summary. Google launched temporary threads in AI Mode on 17 November 2026, rolling out worldwide on desktop and mobile browsers in every AI Mode language. A temporary thread is cut off from the user's Google account: answers ignore past activity, nothing feeds later personalisation and the thread is not saved to history. Google's help page adds that it disappears after 24 hours and cannot use Connected Apps, sharing or image generation. On 19 November, Robby Stein, Google's VP of Product for Search, said on X that a collapsible sidebar for reopening recent AI searches is rolling out on the desktop Google homepage globally. Google has published no blog post or help page on the sidebar, and the report that new AI shortcuts replace the Google Search button comes from the press. For measurement, these visits look like any other Google visit: Search sends only the origin, such as https://www.google.com/, as the referrer, and an AI Mode link click counts as a normal Search Console click. The November 2026 core update was still open on 21 November. US and UK teams should annotate 17 and 19 November, split desktop from mobile, keep 9 to 11 November out of AI impression baselines and judge AI Mode on conversion paths, not last click, through Black Friday on 27 November.
About this article. For SEO, analytics and ecommerce leads with US or UK search traffic. On 21 November 2026 we checked every Google statement against the Google Keyword blog, Google Search Help, Search Console Help, Google Search Central, Google Analytics Help and the Google Search Status Dashboard, and read Robby Stein's post on X through the summary text the page publishes. Sidebar and homepage details that only the press describes are attributed to the outlet that reported them. Our recommendations are analysis, not Google guidance; the worked figures are illustrative and no vendor paid for inclusion. Researched with AI assistance and checked against the primary sources listed in the references.
What changed between 17 and 19 November 2026
Three interface changes landed in three days, in the middle of the November 2026 core update and five to seven days after Google brought Gemini 4 Hydrogen to Search for all users on 12 November. Their confirmation levels differ, so treat them separately. The table draws on Google's posts and help pages, Stein's post and the Search Status Dashboard, with the shortcut row from 9to5Google and Startup Fortune.
| Change | Date | Status | Where it applies |
|---|---|---|---|
| Temporary threads in AI Mode | 17 November 2026 | Confirmed by Google blog and help page | Desktop and mobile browsers, all AI Mode languages, worldwide |
| Collapsible sidebar for recent AI searches, new threads, thread search and notebooks | 19 November 2026 | Announced on X by Google's Robby Stein; no blog post or help page | Desktop Google homepage, global rollout |
| AI shortcuts under the search box in place of the Google Search button | 19 November 2026 | Reported by 9to5Google and Startup Fortune | Desktop homepage |
| Notebooks in AI Mode, synced with Gemini and Gemini Notebook | Already documented | Feature confirmed; sidebar entry point reported | Computers, signed-in personal accounts |
| New Connected Apps for groceries, credit and tax in Search | 20 November 2026 | Confirmed by Google blog | United States |
| November 2026 core update | Began 10 November 2026 | No end date on 21 November | Global, all languages |
Some coverage dates the sidebar to 20 November, when The Decoder wrote it up, but the post is timestamped 19:34 UTC on 19 November, and Search Engine Roundtable, 9to5Google and Digital Trends covered it that afternoon, US time.
The sidebar is not new to testers. Search Engine Roundtable reported on 14 October 2026 that Google was testing the AI Mode left sidebar on the main results page, and Barry Schwartz saw it on his own account from 30 October. Stein's post turns that test into a stated global rollout.
Temporary threads: what Google says, point by point
The Keyword post is three short paragraphs. The help page carries the detail that matters for marketers, summarised in the table below.
| Google's statement, paraphrased | What it means for you |
|---|---|
| The thread is not shown in Search or AI Mode history | The user cannot reopen it from the sidebar, so one-off research leaves no trail to return to |
| Answers do not use past activity | A signed-in user gets an unpersonalised AI Mode answer |
| Nothing from the thread personalises later answers | Gift or sensitive research does not feed later recommendations |
| Access ends on leaving, and threads disappear after 24 hours | No return visits from the same thread |
| No Connected Apps, sharing or image generation | App actions, such as the new US grocery apps, are off inside the thread |
| Not used to train Google's generative AI models, unless the user sends feedback or safety requires it | A training opt-out with stated exceptions |
| Google still collects data that is not tied to the account | Aggregate data still exists on Google's side |
| Sites visited from the thread, and services such as Google Analytics, still collect data, and the browser may keep its own history | Your analytics records the visit as normal |
The last row matters most to SEO teams. A temporary thread is private from the user's Google account, not from your site: privacy ends at the click.
The Connected Apps limit gained weight on 20 November, when Google added Albertsons, Safeway, Shaw's and Target grocery apps, Experian and H&R Block to Search in the US, with Angi and Thumbtack due in the coming weeks. A shopper who builds a basket through one of those apps cannot do it in a temporary thread.
What Google has not said
Read the announcements for their gaps. As of 21 November 2026:
- Search Console treatment of temporary threads. Search Console Help explains how AI Mode clicks, impressions and positions are counted, but neither it nor the generative AI report page mentions temporary threads. Google says it still collects data not tied to an account, so inclusion is plausible. That is our inference, not a Google statement.
- Usage figures. Google gives no share of AI Mode sessions run as temporary threads and no count of desktop users who see the sidebar. Stein said only that the sidebar helped testers make progress and keep exploring the web.
- A formal post on the sidebar or homepage. The Keyword blog's feeds carry no sidebar post up to 21 November, and no help page describes the sidebar or the shortcut buttons.
- Mobile. Digital Trends and Startup Fortune both note that the announcement covers the desktop homepage only. Temporary threads, by contrast, are on mobile browsers too.
- Gemini chats in the sidebar. 9to5Google describes the sidebar pulling in Gemini chat history and tasks, while Digital Trends describes a list of past AI Mode conversations. Google's notebooks help page says notebook sources and instructions sync across AI Mode, Gemini and Gemini Notebook, but Gemini chats do not sync with AI Mode. Until Google documents the sidebar, assume the reports differ.
- New Search Central guidance. None. Google's page on AI features still says there are no extra requirements, special optimisations or special schema needed to appear in AI Overviews or AI Mode.
Why personalisation matters, and what temporary threads switch off
The answer-engine question here is simple: do temporary threads change personalised results? Yes. Google's AI Mode help page says personalisation through Personal Intelligence is open to users aged 18 or over with history and personalised recommendations enabled. It draws on searches and activity saved in Search Services History, can learn from past interactions and, if the user opts in, can use connected Gmail, Google Calendar and Google Photos. A temporary thread turns all of that off for the session.
That has three effects on how your pages surface.
Brand familiarity stops helping in that session. If a returning customer has searched your brand before, a personalised AI Mode answer may lean toward it. In a temporary thread, Google says past preferences do not inform the answer. Google has not said which other signals, such as location or language, still apply.
Gift and sensitive research moves out of view. Google's own example is brainstorming a surprise gift. Retail teams should expect some Black Friday gift research to run in temporary threads, where no history builds up for later recommendations. That does not reduce clicks to you. It reduces the chance that personalisation nudges the same user back to you later.
Manual rank checks get cleaner. Signed-in SEO staff checking AI Mode answers have always seen results shaped by their own history. A temporary thread is the nearest Google-provided way to see an unpersonalised AI Mode answer without signing out. It is not a tracking method: Search Console Help warns that any single search can differ from the average position because of search history, location and other factors.
Attribution and referrers: what reaches your analytics
Google updated its guide to identifying Google Search traffic on 12 November 2026. It says Google Search uses the origin referrer policy, so the Referer header carries only the scheme and host, such as https://www.google.com/ or a local domain like https://www.google.co.uk/, and never the query or path.
AI Mode runs on Google Search itself (google.com/ai is one of the entry points Google lists), so an AI Mode click and a classic blue-link click look the same in GA4 and in server logs. Temporary threads change nothing here: the help page confirms that sites and Google Analytics still collect data when a user follows a link out of one. The table below combines the referrer guide, Search Console Help and the generative AI report page.
| Signal | Classic result | AI Mode, normal thread | AI Mode, temporary thread |
|---|---|---|---|
| Referer header | Origin only: www.google.com or local domain | Same | Same, and Google says sites still collect data |
| Search Console click | Counted | Counted as a normal click | Not stated by Google |
| Generative AI report impression | Not applicable | Counted, as AI Mode is included | Not stated by Google |
| Follow-up question | Not applicable | Counted as a new query | Not stated |
| Saved to the user's history and sidebar | If history is on | If history is on | No; gone after 24 hours |
| Personalised answer | Possible | If history and personalisation are on | No |
Three consequences follow.
You cannot split AI Mode from classic organic by referrer. Any report that claims to do so from GA4 alone is guessing. The generative AI performance report, live for all sites since 31 August 2026, gives impressions for AI Overviews and AI Mode by page, country, device and date, with dates in Pacific Time. It does not give clicks, and it uses Web search type data from the Performance report, where AI Mode clicks sit.
The sidebar lengthens journeys. A user who opens a thread on Monday, reopens it from the sidebar on Thursday and then clicks through is one person on a multi-day path. Search Console Help treats a follow-up question in AI Mode as a new query, so the click is credited to whichever query produced the link, not the first one. In GA4, that user may already have visited from the same thread. Last-click reports will undercount AI Mode's role.
Some visits lose the referrer entirely. Google lists private browsing, anti-fingerprinting protections, opening results in a new tab in some browsers and strict privacy extensions among common causes of a blank Referer. Those sessions land in Direct, and GA4's attribution models give direct visits no credit unless the whole path is direct. A user who picks a temporary thread for privacy may also browse privately, so expect a little more Direct traffic, not less.
Measurement plan for the next 30 days (US and UK)
The calendar is crowded. The core update began on 10 November with an estimate of up to two weeks and had no end date on the Search Status Dashboard on 21 November. Search Console also logged too few generative AI impressions for 9 to 11 November because of a logging error. Hydrogen arrived on 12 November. Thanksgiving is 26 November in the US, Black Friday is 27 November in both markets and Cyber Monday is 30 November. Separate the effects before anyone writes a post-mortem.
- Annotate. Add Search Console custom annotations for 17 November (temporary threads) and 19 November (sidebar and homepage). Keep notes for 9 to 11 November (logging error), 10 November (core update) and 12 November (Hydrogen).
- Pick a clean baseline. Use 2 to 8 November, a full Monday to Sunday week before both the core update and the logging error.
- Split by device. The sidebar and homepage change are desktop only; temporary threads are on both. A shift that shows on desktop but not on mobile, in both the Performance report and the generative AI report, points to the sidebar.
- Split by query length. Stein's rationale is questions that need more than one search. Search Console's Custom (regex) query filter uses RE2 syntax, so
^(\S+\s){7,}\S+$isolates queries of eight words or more for comparison with shorter ones.
- Split by country. Use the Countries dimension to separate the United States from the United Kingdom, because Thanksgiving shifts US demand only.
- Check GA4 channel rules. Confirm that
google.co.ukand other local Google domains map to Organic Search, not Referral. Google names custom channel rules, referral exclusions and filters as common causes of misclassified Search traffic.
- Credit conversion paths. GA4 now offers only data-driven attribution, paid and organic last click and Google paid channels last click; the position-based, linear, time decay and first click models went in November 2023. Use data-driven attribution, keep the key event lookback window at 30 days or more (90 is the default for most key events) and read the Attribution paths report, so a sidebar return visit gets credit.
- Read server logs. Match the
Refererfield on landing-page requests only, as Google advises, and count blank referrers by device. A rise in blank desktop referrers after 19 November is worth logging.
- Freeze big content changes. Google's core update guidance says to confirm the rollout has finished, wait at least a full week, then compare with a week before it started. With Black Friday in the window, hold large rewrites on affected page groups until December.
- Re-check sources. Look for a Google blog post or help page on the sidebar before sharing conclusions internally.
Worked example: isolating a desktop sidebar effect
The figures below are illustrative, not client data. They show the arithmetic a US and UK home-goods retailer could run once clean post-change data exists, which on 21 November it does not.
Baseline week, 2 to 8 November 2026 (before the core update and the logging error), organic clicks from the Performance report:
- Desktop: 40,000 clicks
- Mobile: 60,000 clicks
Comparison week, 7 to 13 December 2026. If the core update finishes on 24 November, as Google's two-week estimate allows, this is the first full Monday to Sunday week that starts at least seven days later and it also clears Cyber Monday. If the rollout runs longer, move the week.
- Desktop: 36,800 clicks, a change of 36,800 ÷ 40,000 = 0.92, so down 8%
- Mobile: 58,200 clicks, a change of 58,200 ÷ 60,000 = 0.97, so down 3%
Mobile did not get the sidebar, so it acts as the control for seasonality and the core update. The desktop change relative to the control is 0.92 ÷ 0.97 = 0.948, about 5.2% lower.
In clicks: had desktop moved like mobile, it would have earned 40,000 × 0.97 = 38,800 clicks. It earned 36,800, a shortfall of 38,800 minus 36,800 = 2,000 clicks a week (2,000 ÷ 38,800 = 5.2%).
Now check the generative AI report for the same two weeks. If desktop AI impressions rose 15% while desktop classic position held flat, more desktop searches are being answered inside AI Mode threads. If desktop position fell instead, the core update is the more likely cause.
Put a value on it. At a 2.5% conversion rate, 2,000 × 0.025 = 50 orders. At an average order value of $85 in the US, that is 50 × $85 = $4,250 a week. For a UK storefront with a £70 average order value, the same 50 orders are worth 50 × £70 = £3,500 a week. That is a ceiling on the last-click loss, not the true loss, because some of those users will return through a sidebar thread and convert later. Compare it with the Attribution paths view before you act.
Decision table: what to do, by team
Paid search teams should read our AI Mode ads playbook for the US and UK alongside the last row.
| Role | Do this now | Why |
|---|---|---|
| Ecommerce SEO lead before Black Friday | Annotate 17 and 19 November, split desktop and mobile, freeze large rewrites | The core update is still rolling out and demand is seasonal |
| Analytics lead | Fix channel rules for local Google domains and use data-driven attribution with path reports | AI Mode and classic clicks share one referrer; sidebar returns lengthen paths |
| Content lead | Cover the sub-questions of each buying decision on one strong page | Longer, multi-turn sessions reward pages that answer follow-ups |
| Brand or PR lead | Do not assume returning customers will see you first in AI Mode | Temporary threads remove personalisation for that session |
| Owner of rank and AI visibility reporting | Use temporary threads for manual spot checks; keep a tool for trend data | Spot checks are cleaner, but answers still vary between runs |
| Publisher | Watch desktop homepage sessions and Discover separately | The homepage change is desktop only and Discover is a different surface |
| Paid search lead | Watch the desktop query mix and AI Mode ad placements | Ads inside threads sit differently from the classic results page |
Rank tracking and query mix: what to expect
Ask your AI visibility vendor whether its checks run signed in; if they do not, temporary threads do not affect them. Treat tool data as a trend line, not a ranking. Google's help page describes Hydrogen as the model for fast, all-round help on most AI Mode questions, while Google AI Ultra subscribers aged 18 or over can pick Gemini 4 Carbon from the menu, within daily limits. Two signed-in users can legitimately see different answers; our Hydrogen analysis covers the model change. For internal QA, run each priority query three times in a temporary thread from a US and a UK location, record which pages are linked and repeat weekly.
The reported homepage shortcuts send desktop users toward AI features from the first screen, but Startup Fortune reports that pressing Enter still runs an ordinary search, so typed short queries should behave much as before. The sidebar matters more, and its effect could go either way (our inference). Search Engine Roundtable's Barry Schwartz expects it may lead to more queries for Google Search and AI Mode, and follow-ups count as new queries. Equally, a user who reopens a thread may never type a fresh search. Your own desktop data will show which dominates; our piece on AI Mode inline links shows how to measure it with a control group.
US and UK notes
- Rollout scope. Temporary threads are global on desktop and mobile browsers. The sidebar is described as a global desktop rollout, and Digital Trends notes it may take days or weeks to reach everyone. AI Mode itself is available in both the United States and the United Kingdom, per Google's availability list.
- Personalisation eligibility. Personal Intelligence requires users aged 18 or over with history and personalised recommendations on, in both markets. For Workspace users whose administrator has turned off Search and Assistant, Search history is unavailable, so there are no saved threads to return to.
- Consent. A temporary thread does not change your consent obligations. If your consent banner blocks analytics until a visitor opts in, those visits stay unmeasured whatever thread they came from; Google lists consent management among the reasons analytics misses visits.
How eCorpIT can help
eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our SEO, AEO and GEO audit service separates interface changes, model changes, core updates and seasonal demand in your Search Console, GA4 and server-log data, then fixes the channel rules, attribution settings and pages that matter. Talk to us at /contact-us/.
Last updated: 21 November 2026.