The November 2026 core update started rolling out on 10 November, and Google says the rollout can take up to two weeks. For a small site the correct response is boring: freeze structural changes, save a clean baseline, fix only real errors, and spend the waiting time on one asset nobody else can copy. Then measure once, in December, when the data means something.

I have watched this pattern for years. Day two, a page drops four positions, the owner rewrites the title and installs a new plugin, and three weeks later nobody can tell what caused what.

The short version

• The rollout began 10 November at about 10:06 a.m. Pacific. It applies globally, to all languages, and may run until roughly 24 November.
• Ranking movement mid-rollout is noise. Google’s guidance: judge a full week after the update completes against the week before it started.
• Do not touch titles, slugs, themes, redirects or old posts while it runs. Fix real errors only.
• Export Search Console data for 3–9 November today. That baseline is the only clean one you will get.
• Use the two weeks for the work that survives every update: a page of data or a tool only your site can produce.

What is confirmed, and what it does not mean

Google’s announcement was three sentences long. Most of the panic comes from reading more into it.

A core update is a re-scoring of pages against everything published since the last one. It is not a penalty, and there is no list of banned techniques to check. The wrong response in week one — a rushed redesign — creates a second variable you can never separate from the first.

Freeze the structure for two weeks

Between now and the end of the rollout, the safe list is short:

• No title or meta description rewrites on pages that were already getting clicks.
• No slug changes, no redirects, no merging posts, no deleting “thin” pages on a hunch.
• No theme switch and no new SEO plugin. Install one now and you will never know if it helped.
• No mass internal-link edits across the whole site.

What you should still fix: anything broken rather than underperforming. A 500 on one template, a URL in the sitemap that returns 404, a plugin with an active advisory. Those are bugs, and fixing a bug during a rollout is not chasing a ranking.

Keep publishing on your normal schedule. A new post this week is not optimising for the update; it is just your job. If you need a plan for the next month that does not depend on today’s numbers, the process I use is here: How to Plan a Month of Content in One Afternoon.

Save the baseline before you need it

Google’s advice is to wait until the rollout finishes, wait one more full week, then compare that week against the week before 10 November. For this update, that baseline window is 3–9 November.

Export it today. Search Console keeps 16 months, and your future self will not remember which week was clean:

1. Open Performance, then Search results.
2. Set the date range to 3–9 November 2026.
3. Use the export button, not a screenshot. You want the Pages and Queries tables as CSV.
4. In your analytics, annotate 10 November as “core update start”.

Then write down every change you made to the site this month: moved pages, a new theme, edited titles, plugin updates. Half of what looks like an algorithm hit is your own edit from ten days ago. If Search Console is not set up properly yet, do this walkthrough before you read another ranking chart.

A change log is enough, and it does not need to be a system:

2026-11-13  core update day 4. no structural changes.
2026-11-13  published: /google-november-2026-core-update-small-site/
2026-11-18  plugin security update only. no config changes.
2026-11-24  rollout window ends. still nothing structural.
2026-12-01  compare the week against the Nov 3-9 baseline.

The work that actually changes a small site’s numbers

While the rollout runs, the useful question is not “what did Google do to me” but “what does this site have that no other site has”. A small tool-site owner posted a concrete answer on Indie Hackers this week, with numbers from Search Console: 48 clicks in the previous 28 days to 166 in the last 28, impressions from 7.46k to 21.8k, and no page lost clicks. The cause was not more articles. It was five changes.

1. One page of original data. He collected Windows battery reports from four real laptops — two of his, his sister’s Lenovo, his brother’s HP — and put the numbers on one page with a chart and a downloadable CSV. Including the weird values: a battery that tripled for a day, 67 years of AC time in a week. Every guide on the site now links to that page. It is the first thing on the site nobody else could copy.

2. Three small calculators. He kept doing the same arithmetic by hand while reading reports, so he built battery runtime, mAh to Wh, and charger wattage calculators that run in the browser with no upload — and gave himself honest reasons to link between guides.

3. Titles rewritten to the query. Search Console showed impressions for searches his titles did not answer. “Laptop Stops Charging at 80%” became “Laptop Not Charging Past 80%? Turn Off the Charge Limit”. “Battery Health Percentage” became “How to Calculate Laptop Battery Health: Formula + Calculator”. Same content, different promise.

4. The small trust fixes. A checker intro said “enter two values” and showed three fields. The homepage said Windows 10 and 11 while another section said 11 only. His name sat at the bottom of the About page; now it is in the first paragraph. Boring, and exactly what a reader or a reviewer notices.

5. Crawl cleanup. A crawl found titles and descriptions that were too long, the tools index reachable at two URLs, an outdated support link, and a broken backlink. None of it exciting, all of it real.

One case is not a formula, and the post is honest about what did not change: AdSense is still not approved, and the new data page itself is still “crawled, currently not indexed”. That is the most useful part. Original work does not rank on the day you publish it. It gives the rest of the site something to point at, and that is what compounds. Drafting is a solved problem — my own 90-minute workflow is what I use.

What this looks like on my own sites

The two sites I run are small. One sells hosting; the other is a set of free browser tools that has more tools than visitors. During this rollout I am not rewriting titles on either. I am exporting the baseline and building one page out of what I already own: questions from support mail and errors in my own logs. Not a guide to X. A page of what actually happened, with numbers and screenshots attached.

The ten-day plan

• Today: export 3–9 November, write the change log, touch nothing else.
• Days 1–10: keep your publishing schedule, build one original asset, fix only real errors.
• Around 24 November: check the Search Status Dashboard for the completion notice. Do not edit yet.
• One week after completion: compare that week with the baseline. Pages tab sorted by lost clicks, then the Queries tab.
• After that: fix the three pages that lost the most by answering the query better, not by writing ten new posts about the same thing.

Do this today

Open Search Console, export 3–9 November, and write one sentence: the asset only you could publish — your data, your tests, your screenshots, your support inbox. That sentence is the plan. The update will finish on its own.