Skip to content
← Guides & updates

SEO · FOR HONG KONG BUSINESSES

Google’s November 2026 core update is rolling out: what Hong Kong SMEs should do now

Google’s Search Status Dashboard shows the November 2026 core update started on 10 November 2026 (US/Pacific). It applies globally and to all languages, and the rollout may take up to two weeks. This guide follows official advice for Hong Kong SMEs: what not to change mid-rollout, and how to check Search Console after it finishes.

Articles in this section are prepared with AI assistance. Sources are listed below.

The incident page on the Google Search Status Dashboard shows that the November 2026 core update started at 10:06 on 10 November 2026, US/Pacific time (about 02:06 on 11 November, Hong Kong time). The official note at 10:07 PST says the update applies globally and to all languages, and that the rollout may take up to two weeks to complete. The dashboard lists this as system information affecting Ranking, not as a crawling, indexing, or serving outage.

This is a core update, not the September 2026 spam update, and it does not mean your website is broken. Google’s core-updates documentation explains that several times a year it makes significant, broad changes to its search algorithms and systems, with the aim of presenting helpful and reliable results for searchers overall. These changes do not target specific sites or individual pages. Google also says that, in general, most sites do not need to worry about core updates and may not even realise one has happened.

A ranking shift is not proof you did something wrong

Google uses a restaurant-list analogy: when you reconsider which places are most worth recommending now, the list changes. A restaurant that moves down is not necessarily “bad”; there may simply be other options that better match what searchers need today. The official guide to debugging Search traffic drops also reminds site owners that results are dynamic, because the open web is constantly changing with new and updated content, and that positions are not fixed. Seeing impressions, clicks or average position move during the rollout is not, by itself, evidence of a penalty.

What not to rush while the rollout is still underway

  • Do not decide from one or two days of Search Console data that the site has been “hit” or has “risen” before the rollout has finished. Google recommends confirming on the Status Dashboard that the core update has completed, then waiting at least a full week before analysing the data.
  • If your service pages or main content already help customers, do not rewrite them heavily because of a small position change. Google’s example of a small drop is moving from position 2 to 4; in that case it advises against drastic changes to content that is already performing well.
  • Avoid “quick fix” changes, such as deleting a page element because you heard it was bad for SEO. Google recommends focusing on changes that make sense for your users and are sustainable in the long term.
  • Do not add large amounts of extra content, or remove older content, mainly to make the site look “fresh”. Google’s people-first content guidance states that this will not improve the site’s overall search performance.
  • Do not lump a core update together with technical faults, security issues, or spam-policy actions. If the site suddenly goes down, many pages have a noindex tag, or Search Console shows a manual action or security issue, treat those separately rather than blaming this update for everything.

What you can prepare now

  • Bookmark the Status Dashboard incident page so you can later confirm the start and end dates. Google’s core-updates guidance says to confirm that the update has finished rolling out, and to note those dates, before you analyse the change.
  • Make sure the site is verified in Search Console and that you can open the Performance (Search results) report. You will need date comparisons and the pages and queries tables later.
  • Note performance for the week before the rollout started, as a baseline for later comparison. Google recommends waiting at least a full week after the update completes, then comparing that week with a week before the rollout started, so you can better see what actually changed.
  • Keep maintaining clear, accurate service descriptions, coverage, contact details and enquiry paths. Write those for customers, rather than adding temporary copy just to “meet” this update.
  • If you have both Chinese and English pages, first make sure both languages are clear and factually consistent, instead of rushing out a large volume of new articles to “catch” the update.

How to check Search Console after the rollout ends

Both the core-updates documentation and the traffic-drop debugging guide recommend using Search Console to judge how large a change is and which type of Search it affected. When you compare periods, use the date filter’s Compare option in the Performance report, and look at Web Search, Images, Video and the News tab separately so you do not mix figures from different sources.

  • First confirm on the Status Dashboard that this core update has finished rolling out, and record the end date.
  • Wait at least one full week, then compare that week with the week before the rollout started.
  • Review your top pages and queries to see whether any position change is small or large. Google’s examples: a move from position 2 to 4 is a small drop; a move from position 4 to 29, or a fall well out of the top 10, calls for a deeper assessment.
  • Check Web Search, Google Images, Video mode and the News tab separately, to see whether a change is limited to one search type.
  • If you serve both local and overseas customers, use country or device filters to see whether a change is concentrated in Hong Kong, on mobile, or on a particular group of pages. The country filter reflects where the searcher was at the time of the query, not a target-market setting on the page.
  • Also rule out other causes: technical issues in the Page indexing or Crawl stats reports, notices in the Manual actions or Security issues reports, and seasonal changes in demand. The official debugging guide lists these common reasons so you do not attribute everything to one update.

If positions fall sharply and stay down, how to self-assess

If you see a sustained, large drop in position across the site and across a wide range of queries, Google recommends a self-assessment of the site as a whole, not just individual pages, to check whether the content is helpful, reliable and people-first. Answer the questions yourself first, and consider asking someone you trust who is not involved with the site to review them too.

  • Does the content provide information you are in a position to know first-hand, such as your actual service scope, methods, limits or on-the-ground experience, rather than simply rewriting other sites?
  • For the topics you want to be found for, is the description complete enough that a customer can decide how to enquire or book?
  • Does the main heading or page title give a clear, helpful summary, and does it avoid exaggeration or shocking language?
  • If someone came to your site directly, rather than from Search, would this content still be useful to your existing or intended customers?
  • Is it clear which company published the page, how to get in touch, and what sources or expertise sit behind the information, so a reader can trust it?
  • Are there easily checked factual errors, such as the wrong opening hours, service area, licence details or pricing explanation?
  • Is the content mass-produced mainly to attract search visits, or generated with automation and little human review?
  • Is this a page you would bookmark, share with a friend, or feel has already helped the reader achieve their goal?

Google also advises making changes that genuinely help users, for example by rewriting or restructuring content so it is easier to read and navigate. Deleting content is a last resort, and only if you think it cannot be salvaged; if you are considering removing entire sections, that may be a sign those sections were created for search engines first, not for people. After you make improvements, some changes can take effect in a few days, but it can take several months for Google’s systems to learn and confirm that the site as a whole is now producing helpful, reliable, people-first content in the long term. You do not necessarily have to wait for the next major core update to see an effect, because Google also makes smaller, unannounced core updates; even so, there is no guarantee that changes you make will have a noticeable impact in search results.

This is an observation and self-check list based on official guidance. It does not guarantee higher rankings, more traffic or more enquiries. Rely on the Google Search Status Dashboard and the latest Search Central documentation. This update is still rolling out; the completion date will be whatever the dashboard later records.

Sources

  1. November 2026 core update — Google Search Status Dashboard ↗
  2. Google Search Status Dashboard ↗
  3. Google Search's core updates and your website — Google Search Central ↗
  4. Creating helpful, reliable, people-first content — Google Search Central ↗
  5. Debugging drops in Google Search traffic — Google Search Central ↗
  6. Using the Google Search Status Dashboard — Google Search Central ↗
  7. Performance report (Search results): Overview and basic setup — Search Console Help ↗
  8. Performance report (Search results): Advanced filtering and comparison — Search Console Help ↗
WCAG 2.0Accessibility guidelines