Updates blog — Friday, June 5, 2026

HubSpot Updates: June 5, 2026

Seven updates came through Friday, and most of them point in the same direction: the everyday surfaces of HubSpot getting attention. A redesigned record page, a single home for dashboard settings, cleanup that finally deletes instead of just hiding, and sandbox parity for sequences all land in the same batch, alongside a new AEO content move and a runtime deadline worth a calendar note.

If you watched the show today, you already heard the conversation around two of these. If you did not: Watch the recap to hear our thoughts on these updates and more.

Platform Updates Detailed

Universal Record Page Beta

Universal Record Page is a redesigned contact, company, deal, and ticket record experience that opens as a full screen overlay, so you can view and work with a record without leaving your current context or juggling multiple tabs. Records load significantly faster than the current page, and a decluttered two column layout makes it easier to find and focus on the information you need. All Free and Starter customers can request the private beta, which is rolling out in phases to a limited group of customers.

Why it matters: The record page is the most visited surface in HubSpot, and an overlay that keeps you anchored where you started is a real rethink of how record work flows. HubSpot has added important notes since the first release, and they are the part to read closely: this is early and experimental, not all record features are supported yet, there is no GA date, and customizations made during the current beta will not carry over to future iterations. Treat this as a preview to evaluate, not a configuration to commit to. If you are on Free or Starter, requesting access costs you nothing.

For more details: Universal Record Page private beta.

Dashboard Settings Panel

Dashboard management is moving into a single panel covering name, owner, access, description, tags, and more, replacing the scattered drop-downs and links that used to handle those settings. This is in public beta and scheduled for release June 24, available across all hubs and tiers.

Why it matters: Managing a dashboard meant hunting through several action menus to change things that all belong together. Pulling them into one panel is a small efficiency, but it is the kind that adds up for anyone who maintains more than a handful of dashboards. The broad availability is the headline here: this reaches every hub and every tier, which is rare in a batch otherwise weighted toward beta and Enterprise.

For more details: Dashboard Settings Panel public beta.

AEO: Create a Blog Post From a Recommendation

The AEO tool shows where your brand is missing from answer engine results and recommends content to close those visibility gaps. You can now generate a full blog article directly from one of those recommendations, where the workflow previously produced only listicles. This is in private beta for Marketing Hub Professional and Enterprise.

Why it matters: AEO already turned recommendations into LinkedIn content, and this extends the same idea to structured blog posts, moving from insight to a ready to edit draft in a few clicks. The honest caution is that a draft is what you get. Generate one of these on autopilot and it will read like every other post built from the same recommendation. Bring real context about your audience and your product, treat the output as a first pass, and it becomes a useful way to close visibility gaps faster.

For more details: AEO blog post from recommendation private beta.

Cleanup Automation Deletes Unused Website and Landing Pages

Account Cleanup can now delete unused website and landing page drafts rather than only archiving them. Until now, cleanup moved identified clutter out of the primary view but stopped short of removing it, which meant an extra manual deletion step to actually clear it out. This is available across the Enterprise tiers of Marketing, Content, Sales, Data, Service, and Smart CRM.

Why it matters: Archiving without deleting is half a cleanup. It tidies the view while leaving the clutter in place, and the manual delete that followed was exactly the kind of work people put off indefinitely. Closing that gap makes Account Cleanup a more complete tool, though the usual judgment still applies: review what gets flagged before you remove it, because near duplicate and unused are easier for a tool to suggest than to be sure of.

For more details: Cleanup automation for unused website and landing pages private beta.

Price Books

Price Books give RevOps teams a centralized way to define, manage, and apply product pricing across deals and quotes, with this first release focused on structured pricing setup and basic end to end usage. This is in private beta for Commerce Hub Professional and Enterprise.

Why it matters: As pricing grows more complex across segments, geographies, and deal types, the fallback at most companies is a spreadsheet and a lot of tribal knowledge, which makes veterans fast and new hires slow. Price Books move pricing under governance: a small number of owners set it, everyone else applies it, and deals and quotes reflect the right numbers without manual lookup. That is less room for error and faster, more consistent quoting across the team.

For more details: Price Books private beta.

Sandbox Support for Copying Sequences

When you create a sandbox, sequences now get copied over from your production portal, so you can build, test, and refine outreach flows without affecting the people working in production. Sandboxes are an Enterprise feature, and sequences are available for Sales Hub Professional and Enterprise and Service Hub Professional and Enterprise.

Why it matters: Sequences are core to how sales and service teams run one to one outreach, and until now testing changes meant either working live in production or rebuilding sequences by hand in the sandbox. Neither is a good option. Copying them automatically brings sequences into line with the broader push to make sandbox a true mirror of production, which matters more as portals get more complex and the cost of an untested change goes up.

For more details: Sandbox support for copying sequences private beta.

Node 18.x and 20.x Runtime Deprecation for Chatflows Custom Code

The Node 18.x and 20.x runtimes will be deprecated for Chatflows custom code snippets on July 13, 2026. Both versions are reaching end of life and no longer receive security patches, so HubSpot is moving these snippets to Node 24.x, the current long term support release. This is in development and affects Data Hub Professional and Enterprise.

Why it matters: This is narrow, but it comes with a date and a small amount of homework. If you run custom code in chatflows, the snippets need to move to Node 24.x before July 13 to keep them on a supported, patched runtime. Most teams will not have any custom code in scope, but the ones that do should not let this slip, because an unsupported runtime is a security exposure, not just a deprecation notice.

For more details: Node 18 and 20 runtime deprecation for Chatflows custom code.

Key Takeaways and Next Steps

The everyday surfaces are getting attention: The record page redesign, the consolidated dashboard settings, the upgraded Account Cleanup, and sandbox parity for sequences are all the same kind of update: HubSpot smoothing the surfaces people actually work on every day. None of them is flashy on its own, but together they signal a focus on the daily experience rather than net new objects. The one to watch is Universal Record Page, with the caveat that current beta customizations will not survive to GA.

AEO keeps turning insight into action: Blog generation from a recommendation is the latest step in AEO moving from showing you gaps to helping you close them. The right posture is the same as it was for the LinkedIn content: use it to get a structured draft, then do the work that makes the draft yours. Anything you publish straight from the button will look like everyone else's.

One date for the calendar: If you run custom code in chatflows, the Node 18 and 20 deprecation on July 13 is the only item here with a hard deadline. Check whether any of your snippets are in scope and plan the move to Node 24 now, while it is a routine update rather than a scramble.