Melbourne Marketing Brief / #060 / NEWS & ANALYSIS
Google’s November core update is rolling out
Published by Ajay Dabhi · · AI-assisted research and writing
12 November 2026 · VERIFIED SOURCE REPORTING · ROLLOUT IN PROGRESS
Google’s November core update is underway. For an Australian service business, the practical first step is to preserve useful search and enquiry evidence, rather than rewrite pages in response to a single quiet day. Two new HighLevel controls also need care: connecting an AI Studio domain can publish a project, and company suggestions require an identity check before choosing a record.
Google’s notice is dated 10 November 2026 in US/Pacific time; the rollout began at 5:06 am on 11 November in Melbourne. This edition reports that announcement with its original date, alongside HighLevel announcements dated 11 November. All sources were checked on 12 November. No rollout completion or individual-site impact has been confirmed here.
Research and writing use AI assistance. No customer account, ranking report, DNS setting or CRM record was inspected, changed or tested. Hypothetical examples are not client evidence. HighLevel is the underlying platform relevant to Growthcenter; its announcements do not establish availability in every Growthcenter plan or Australian account. No personal review by Ajay is claimed.
01 / GOOGLE SEARCH
Record the rollout dates before explaining a traffic change
Google notice 10November · Active at 12November check
What changed
Google’s official status notice says the November 2026 core update began on 10 November at 10:06 am US/Pacific, equivalent to 11 November at 5:06 am Melbourne time. Google says it applies globally and to all languages, and may take up to two weeks. The dashboard listed it as active when checked; the notice does not supply a completed rollout date.
Google’s existing core-update guidance recommends confirming completion, then allowing at least a full week before analysing the change in Search Console. It advises comparing appropriate periods, examining affected pages and queries, and separating search types. This is existing guidance, last updated 10 December 2025, rather than a new instruction issued with this rollout.
Published 10 November 2026. Source checked 12 November 2026.
Publication date not provided by the source. Source checked 12 November 2026.
Who this affects
Australian businesses that receive enquiries through organic Google Search, and the person reviewing their search performance. A global rollout includes Australia, but this notice does not establish that any particular website, Maps listing or paid campaign changed. Businesses without organic-search traffic can monitor the notice without starting a website rebuild.
Our analysis: what it means for your business
Our analysis: fewer enquiries and lower organic visibility are different observations. A quiet day might coincide with the rollout while a phone-routing problem, changed advertising spend or an unavailable booking link needs separate attention. Keep the search evidence and the lead-delivery evidence distinct before assigning a cause.
Hypothetical example: a Melbourne electrician sees fewer quote requests on Wednesday. The operator checks whether the contact form and phone route still work, records recent site and campaign changes, and preserves organic Search Console data for later comparison. Finding a broken enquiry route warrants a repair now; waiting for rollout completion is not a reason to leave it broken. No such test was performed for this edition.
Our recommendation is to note the official start date and check for Google’s completion notice. Then assess an appropriate pre/post period with the documented delay, using page/query and search-type detail. Avoid promising a recovery date, deleting useful pages or commissioning a broad rewrite solely because the update exists. No ranking loss, penalty, lead impact or recovery has been established here.
What to do next
- Keep a dated record of search performance, site changes and actual enquiry-delivery issues.
- Confirm rollout completion before the later Search Console comparison; investigate verified operational faults separately.
02 / AI STUDIO
Domain connection can be the step that publishes the site
Announced 11November · Never-published and live projects differ
What changed
HighLevel says an AI Studio project can now connect a custom domain before it has ever been published. Once DNS is verified and the domains are saved, the latest ready version publishes automatically to the domain. The connected domain becomes the main URL, while the preview URL remains available.
The vendor distinguishes already-live projects: connecting a new domain keeps their current version. If the first publication fails, it says the domain remains connected and the Publish panel opens for another attempt. These are documented product behaviours, not a DNS or publication test by this edition.
Published 11 November 2026. Source checked 12 November 2026.
Who this affects
An authorised operator preparing a first publication in HighLevel AI Studio. Existing sites on other builders do not need a migration because of this feature. Australian/Growthcenter account entitlement was not checked; a project already live follows the separate behaviour described by the vendor.
Our analysis: what it means for your business
Our analysis: domain setup is no longer safe to treat as an isolated preparation task for a never-published project. It can cross the boundary into public release. Have the actual ready version, business claims, contact destination and publication authority settled before the verified-domain save step.
Hypothetical example: a cleaning-business owner asks a contractor to connect the domain while the opening-hours copy and booking link are still drafts. Under the announced first-publish behaviour, that sequence could make the ready version public. The owner and contractor should agree which version is ready before completing the connection. This is a planning example, not an account we inspected.
Our recommendation is to verify the resulting public URL, current content and enquiry destination after an authorised publication. A connected domain or a success message is not proof that a quote request reaches the right person. The retained preview URL also deserves an access/content check; the announcement does not establish its indexing or privacy behaviour.
What to do next
- Confirm the exact ready version and release authority before connecting and saving a verified domain.
- After an authorised release, check the public page and intended enquiry route; distinguish a connected domain from a completed publication.
03 / CRM LABS
A similar company name is a prompt to check identity
Announced 11November · Labs opt-in per subaccount
What changed
HighLevel’s Preemptive Duplicate Detection for Companies is enabled in Labs for a subaccount. While entering a name or domain in Add Company, it suggests possible existing company records, including similar names, punctuation differences and common typos. An operator can open a suggestion to review it.
Suggestions can be dismissed and do not prevent saving a separate company. The feature does not scan or merge existing records. HighLevel cautions that similar names or a shared domain may still represent different businesses. It is an entry-time aid, not automatic historical CRM cleanup.
Published 11 November 2026. Source checked 12 November 2026.
Who this affects
Authorised staff adding company records in a HighLevel-based CRM where the Labs option is available. A business using only individual contact records, or lacking the feature, can ignore it. Growthcenter/Australian access was not verified, and no Labs setting was enabled.
Our analysis: what it means for your business
Our analysis: the useful decision is which business entity owns the contact, deal and service history. A possible match can help someone find that record, but choosing the wrong match can be as confusing as creating a duplicate. Review identifying details before attaching new work to an existing company.
Hypothetical example: a contractor works with two separately operated businesses under one franchise website. A shared domain may make a suggestion plausible without making the companies interchangeable. The operator checks the branch or entity details and keeps separate records where the business relationship requires them. No company record was created or merged here.
Our recommendation is to agree the identity fields staff should review and what to do when uncertain. Handle existing duplicates as a separate, authorised reconciliation task with relationship/history checks. Enabling the suggestion feature would not establish that historical deals and contacts are consolidated or that reporting totals are correct.
What to do next
- Have the authorised operator check feature eligibility and the intended company identity before using a suggestion.
- Keep historical duplicate reconciliation separate; suggestions alone neither merge records nor prove clean reporting.
ANALYSIS / BUSINESS CONTEXT
Where to spend your attention today
The shared decision is when to act and what evidence is enough. A Search update starts a monitoring window, a verified-domain save can trigger a first public release, and a company suggestion starts an identity review. Each needs a different confirmation; none establishes a ranking, booking, revenue or staff-time improvement on its own.
Commercial context: Ajay Dabhi sells local SEO, website, advertising and automation services for Australian service businesses. The invitation below is separate from the reporting. An existing authorised search, website or CRM operator may be able to perform the relevant checks. Growthcenter capability and plan access were not tested. Digital services are Australia-wide; on-site visits are available in Melbourne.
Practical checks
- Preserve useful search/enquiry evidence while the core update rolls out.
- Approve the ready site before completing a first AI Studio domain connection.
- Review company identity before selecting a possible duplicate match.
These checks are recommendations, not additional requirements announced by the platform. The appropriate work depends on your actual configuration.
Publisher and editorial information
Ajay Dabhi publishes this report and also sells marketing and automation services. The commercial invitation above is separate from the sourced reporting. No client account test or direct interview is claimed in this report.
Research and writing use AI assistance. Original documents are linked so readers can check the facts. Read our ownership, sourcing and corrections policy or report a correction to Ajay.
All Melbourne Marketing Brief editions →