Sitecore Content Hub Roundup: Search lean-up, better notifications, and useful fixes

A practical take on three new Sitecore Content Hub entries, including the search indexing fix that will probably matter most in real projects.

Sitecore pushed a small batch of Content Hub changes on April 17. None of these look flashy, but a couple of them fix real friction points that teams actually run into.

This update is mostly about polish: better search behaviour, clearer user feedback, and a grab bag of fixes around import/export and editing. That's not just some exciting marketing copy, it's useful platform maintenance.

What changed

Custom notification messages for external actions

Sitecore now lets you customize the notification message shown when an external action starts during entity operations. In plain English, that means you're no longer stuck with a generic confirmation message. You can choose the default message or use a custom one, and you can select or create a translation for it.

Why that matters:

• It gives admins a cleaner way to explain what just happened
• It should reduce user confusion when an action kicks off something outside the immediate screen flow
• It matters more in multilingual setups where vague system messaging gets old fast

Who should care:

• Content Hub solution owners
• Teams building custom external actions into editorial workflows
• Admins supporting multilingual business users

Watch-out: the changelog doesn't say anything about where these messages can be managed in bulk or whether there are any limits around translation reuse. So I'd treat this as a helpful UI/workflow improvement, not a major architecture change.

HTML tags are now excluded from the search index

This is the most practical item in the batch. For HTML string properties, Sitecore now strips HTML tags before indexing. The full HTML still stays in the system for rendering and audit, but search only uses the visible text.

That matters because large chunks of markup can absolutely mess with search relevance and discoverability. If you've ever had content that should have matched a search but didn't, buried HTML noise may have been part of the problem.

Who should care:

• Teams storing rich text or HTML-heavy content in Content Hub
• Search-dependent editorial teams
• Implementers who get blamed when search feels inconsistent

Practical impact:

• Search results should better reflect what users actually read
• Indexed content should be less polluted by markup noise
• Advanced search should be more useful on HTML-backed properties

Watch-out: if anyone had built expectations around searching raw HTML fragments or tags, that behaviour may change. For most real-world teams, that's probably a good trade.

Resolved issues in Content Hub

The third entry is a broader fix rollup rather than one feature.

A few items stand out:

• Import/Export V2 now includes non-system-owned schema definitions, bringing it closer to V1 behaviour
• Import logic fixes should reduce some dependency resolution pain during package moves
• Entity detail loading was fixed for cases with large number of related entities
• The dynamic Today filter now correctly matches DateTimeOffset values set to today
• Relation editor filtering and conditional import behaviour both got fixes

Why this matters:

• Import/Export reliability problems waste a lot of time and confidence
• Schema and dependency issues tend to show up during deployments, migrations, and environment sync work.
• Fixes around large related-entity loads can matter a lot in messier real production models

Who should care:

• Platform owners moving configurations between environments
• Developers and admins handling Content Hub packaging schemas
• Teams with heavier data models or complex conditional schemas

My read: this is the kind of changelog entry that looks boring until you've spent half a day chasing one of these bugs. Then it suddenly feels rather useful.

What this means in practice

If you can use Content hub day to day, this batch looks like steady maintenance rather than a big strategic shift.

The search indexing change is the most broadly useful update. The custom notification option is a nice workflow improvement. The resolved issues list is where the more operational value probably sites, especially if you've had import/export oddities or UI friction in larger implementations.

So no, this is not a headline release.

But it is the kind of update that can make the platform a little less annoying to live with.

Upgrade and watch-out notes

• Test search behaviour on any HTML-backed properties that matter to editors
• Review external actions where clearer confirmation text would reduce support noise
• If Import/Export V2 has been giving you grief, this is a sensible set of fixes to validate in a non-production environment
• Don't assume every bug mentioned here maps directly to your tenant: verify the affected area before promising internal stakeholders that a pain point is fully gone

Source

• Custom notification messages
• Excluding HTML tags from search index
• Resolved issues in Content Hub for April 17, 2026