Since Sitecore announced it was acquiring Scrunch in June, I’ve been wondering about something.

Could Sitecore Content Hub eventually become part of the way brands optimise how they appear in ChatGPT, Perplexity, Gemini and whatever comes next?

When I first started writing this post, my answer was going to be: conceptually yes, officially no.

But things have moved on.

Sitecore has now said Scrunch recommendations will be automated across SitecoreAI’s Content Management, Content Marketing and Digital Asset Management solutions.

And that last part immediately caught my attention.

In the previous post in this series, I looked at the DAM capabilities appearing inside SitecoreAI. My reading is that this is probably the DAM Sitecore is referring to here, rather than Sitecore Content Hub.

That’s an important distinction.

SitecoreAI DAM makes complete sense as an integration point for Scrunch, particularly when you’re trying to improve the content being created and published through SitecoreAI.

But I think there’s a much bigger opportunity.

I want to see Scrunch connected to Content Hub.

Not because Content Hub happens to have a DAM, but because it’s a much broader content platform.

For many organisations, Content Hub is where the governed version of their digital estate already lives: assets, metadata, taxonomy, product information, relationships, localisation, rights, approvals and workflows.

If Scrunch can tell an organisation what AI believes about its brand, Content Hub potentially contains the governed information that tells us what the organisation says is actually true.

That’s the connection I find really interesting.

Content Hub can govern the truth. Scrunch can tell you whether AI understands it.

So this post isn’t about an integration Sitecore has announced.

It’s about the integration I think Sitecore should build.

What’s actually confirmed

Scrunch is now a Sitecore company, but it hasn’t disappeared into SitecoreAI. Scrunch has said it will continue operating as a standalone platform, supporting its existing customers and partners while accelerating its roadmap with Sitecore behind it.

That’s important because Scrunch is solving a problem that exists well beyond Sitecore.

AI answer engines don’t particularly care whether your content originated in Sitecore, Adobe, Contentful, a PIM, a DAM or somewhere else entirely. They care whether they can access it, understand it, trust it and use it to construct an answer.

That’s why I think Scrunch is such an interesting acquisition.

It isn’t just another CMS feature. It’s a visibility layer across the content supply chain.

Scrunch can show where your brand appears in AI answers, where competitors appear instead, what sources are being cited and where AI systems are missing or misrepresenting information about you.

There isn’t currently a generally available Scrunch integration for Content Hub that I can install and demonstrate.

I’m probably going to build this myself.

And that’s exactly why I think it’s worth exploring what one could look like.

Think about what already exists inside a mature Content Hub implementation.

You have approved assets. Metadata. Taxonomy. Product information. Relationships between entities. Brand information. Localisation. Rights management. Expiry. Workflow. Approval state.

In other words, you potentially have a structured, governed representation of what the organisation believes to be true.