HubSpot’s August 2026 release touched on marketing, sales, service, ops and AI. In this article we will dive into the seven changes that matter most for RevOps and marketing teams: AEO recommendations can now be ranked by estimated citation lift, the ChatGPT and Claude connectors can now read and write more of the CRM, Claude Design can send landing pages straight into HubSpot, Bombora Company Surge signals are now native to the CRM, price books centralise pricing across deals and quotes, imports now catch more duplicate records automatically, and recorded meetings stop creating duplicate CRM activities.
We know there is a lot to go through, so we’ve selected the updates worth knowing about and broken down what they do and where they can make a difference.
How does estimated citation lift change HubSpot AEO?
HubSpot’s AEO recommendations now carry an Estimated Citation Lift score, based on current citation performance, recommendation type and historical citation data. Teams can sort by projected impact and start with the changes HubSpot expects to move the needle most.
That solves a real problem: a long list of AEO recommendations doesn’t tell a marketer what to do first. The new ranking adds that missing layer helping you prioritise.
- See the Estimated Citation Lift for each recommendation under Marketing > AEO > Recommendations.
- Prioritize recommendations based on their projected citation impact, so you can focus on the changes with the greatest potential effect.
- Estimates are based on your current citation performance, the recommendation type, and historical citation data.
How much more can you do with HubSpot directly from ChatGPT and Claude?
HubSpot has expanded its ChatGPT and Claude connectors to cover Contacts, Companies, Deals, Tickets, Notes, Tasks and Meetings. That means more CRM context available in natural language, plus the ability to create or update records from inside the AI conversation and verify the result in HubSpot.
That’s a step beyond asking an assistant questions about CRM data — it pulls day-to-day HubSpot work, from prepping follow-up notes to updating records, into the conversation itself.
For RevOps teams, the real consideration is permissions. Write access is a different risk than read-only. Before switching it on, define what data the connector can touch, who can use it, and which actions still need a human to sign off.
What changes when Claude Design can send pages directly to HubSpot?
Claude Design can now connect to HubSpot and push a landing page into the portal as a draft: build it in Claude Design, choose Share > More formats and apps > Send to HubSpot, then review before publishing. Send the same design again and it updates the existing draft; send it after the page is published and it creates a new version instead.
The real value is the handoff… no more rebuilding or reformatting the page by hand in a second tool. It’s also a sign of where HubSpot is heading: AI workflows don’t have to start and end inside Breeze. The open question is governance. Before connecting an external AI tool to a company or client portal, confirm what data it can access and what approvals it needs.
What do Bombora Company Surge signals add to Buyer Intent?
HubSpot now includes Bombora Company Surge signals natively. These signals indicate which companies are ramping up research on relevant topics, often before they ever visit your site. HubSpot classifies that activity as High, Medium or Low, and portals can select up to 12 Bombora topics, swappable to better match their ICP and buying journey.
Once inside HubSpot, Company Surge signals work as workflow triggers, segment filters, personalisation tokens or lead-scoring criteria alongside whatever intent data you already use. The value for RevOps teams isn’t just another intent source, it’s that the signal lives in the CRM and can feed the same routing and scoring logic already running there.
How do price books change pricing management?
Price books give RevOps teams a central place to define and apply product pricing across deals and quotes. Sellers pick an active price book from the deal line-item editor, and product properties sync automatically to add context when products are added. Breeze can also assist with importing existing price books skipping manual entry.
For any organisation running different pricing by market, customer type or commercial model, the win is consistency: pricing logic lives in one place instead of getting rebuilt deal by deal.
How is HubSpot reducing duplicate records during imports?
HubSpot has added Smart Duplicate Handling to multi-object imports. Identical rows in the same import now create or update a single record instead of duplicating it; rows with conflicting data are still kept separate rather than merged on a guess.
It’s a small fix for a common problem. Imports will no longer quietly create duplicate records and associations across the CRM.
One limitation worth flagging: this isn’t a deduplication strategy on its own. It only catches identical rows within a single-file, create-and-update import that has no unique ID. Teams should still define reliable unique identifiers and check import settings before data goes in.
Will recorded meetings still create duplicate activities in HubSpot?
From 31 August, meetings recorded through HubSpot’s Notetaker or a supported video-conferencing integration create a single meeting record instead of a call and a meeting. The goal is fewer duplicate activities cluttering CRM timelines, workflows and reporting.
This matters most for sales reporting. A meeting logged as two activities inflates rep activity counts and skews any metric built on logged touchpoints.
You gain cleaner activity history and reporting that doesn’t need manual correction for duplicated meetings.
- Review workflows triggered by Call creation for recorded meetings and update them to reference the Meeting object instead.
- Key properties including transcript, transcript ID, and duration are being added directly to the Meeting record.
- Update reports or integrations tracking recorded meetings via the Call or Engagement object to use the Meeting object.
What should HubSpot teams do next?
Don’t switch on everything just because it shipped. IV-Lead always suggests starting with the operating problem you actually have. If AI assistants already touch your CRM workflow, scope the new ChatGPT and Claude write permissions before opening them up; if AEO work is piling up unordered, start with estimated citation lift. Marketers rebuilding AI-generated pages by hand should test the Claude-to-HubSpot flow, and teams running Buyer Intent or working from inconsistent pricing should check Bombora signals and price books against their own process. On the hygiene side, teams with duplicate-prone imports or reporting that looks inflated by meeting/call double-counting have two straightforward fixes ready to turn on.
Availability and feature status shift over time, so confirm what’s live in your own HubSpot account before building a process around it.
Want to know which of these updates fits your HubSpot setup?
IV-Lead helps teams assess HubSpot configuration, data structure and operating process before adding new automation or AI workflows. If you want a read on which updates are worth pursuing in your portal, book a HubSpot review with IV-Lead.
