Skip to main content

POV - How does the SCRUNCH acquisition mattes the most at this point from Sitecore?

Hello Everyone,


By now, everyone in the Sitecore ecosystem has heard it, Sitecore acquired Scrunch. LinkedIn is full of takes on what it means for the product roadmap, the partner network, the AEO/GEO category. Before I add to that pile, I want to talk about something which raised my eyebrows, and i want yours to raise too

Do you know? Search engines never had a traffic drop in last 20 years, but now first time in history, Search engines are seeing traffic drop.


We are witnessing the shift in a technology and use of it and we are at the very intersection of that change where your site audiences are changing, first time in a history people are not going to search engines, They are going to LLMs for their discovery / research / or day to day tasks.

Back in February 2024, Gartner published a prediction that quietly rattled the marketing world: by 2026, traditional search engine volume would drop 25%, with search marketing losing ground to AI chatbots and virtual agents, Generative AI was becoming a substitute for the search query itself, not just a new feature bolted onto it.

25% is not a small number. A 25% contraction in the channel that most B2B and B2C marketing strategies were built around, in a window of roughly two years.


Cloudflare CEO Matthew Prince expected the crossover by the end of 2027. It arrived in June 2026.

According to Cloudflare Radar, which monitors traffic across roughly 20% of the web, bots now generate about 57% of requests to web pages, compared with 43% from humans.

That means we have more bots than a human on the net already.




What if you have the best site and digital experiences and product catalog, but no one is visiting your site? the content which you curated in years of efforts and created those connected journeys are suddenly not showing results? 

What if the full marketing digital ecosystem feels like to rewritten for this new ERA of AI? 

That sounds scary right? If you are a CMO or a CTO or a Consultant or a Content creator, This article is for all of us who are in the same boat of this era of AI and how the audiences is no more humans, but bots.

You can only fix for which you know "Why" something is not working, Right now, When your website or experiences or campaigns are live, you know bots will visit, but if majority of your traffic comes from there, Then you do not know how to overcome it, Your content is not working, Not because its bad but for because it was created for HUMANS, now the audience is changed, you have to now think how can it be cited by bots or LLMs instead of the old age approaches which were only targeting humans.

We've lived through this kind of shift before

Think back to the dot-com boom. The internet flooded with websites and experiences, all built for one audience: humans, clicking, scrolling, reading. That was the paradigm for thirty years.

Now ask the uncomfortable question: what happens if your experience — no matter how brilliant the content, how polished the design, how strong the brand — simply stops getting that traffic? Not because it's bad. Because the audience reading it has quietly changed from people to machines acting on people's behalf.

That's not a marginal shift. That's the kind of shift that means your entire marketing ecosystem — built for human eyes over the last two decades — may need to be rewritten from the content layer up.

Old friends are getting new neighbors

We all used robots.txt from years, It has quietly governed how search engines crawl the web for about thirty years. In September 2024, AI researcher Jeremy Howard proposed a new file to sit alongside it: llms.txt. Its entire purpose is different from robots.txt, It doesn't tell bots where they can't go, it tells them where the content that actually matters lives, stripped of navigation, ads, and JavaScript that AI models don't need and can't easily parse. 

SEO too, Nearly every marketer has lived and breathed this discipline for years, now has new siblings: AEO, Answer Engine Optimization, and GEO, Generative Engine Optimization. Different mechanics, different signals, same underlying question: will your brand be the one an AI system cites when someone asks it a question your competitors also want to answer?

You can love this shift or resist it. You cannot ignore it. We're sitting at the exact intersection of the change. The real question isn't whether it's happening, it's whether you're ready for it.

Why the Scrunch acquisition is the important part of this story

This is exactly the gap Sitecore just spent real money to close. Sitecore's CEO Eric Stine framed the rationale directly that buyers are now consulting large language models ChatGPT, Claude, Gemini about products and vendors before they ever reach a company's website, and by the time they arrive, if they arrive at all, their opinion is often already formed.

Scrunch's co-founder Chris Andrew has described the company's founding bet, made back in 2023, in a single sentence worth sitting with: that the most important visitor to a website would eventually not be a person, but an AI agent acting on that person's behalf. Two years later, that bet looks less like a gamble and more like a forecast that arrived early.

This is why the acquisition matters to every Sitecore partner, customer, and brand they represent, Not because it adds another logo to the marketplace, but because it's aimed squarely at helping brands show up and get cited in an era where ChatGPT and Claude are becoming primary visitors to their sites, not secondary crawlers.

What Scrunch actually does, and why the name fits

Here's the simplest way I can describe it: Scrunch, quite literally, scrunches your website or a page.

credit : https://scrunch.com/blog/ai-site-crawlability-questions-answered

AI doesn't need the fancy design, the hero images, the animation, the layout choices your team debated for weeks. It needs the content that actually matters which can be clearly stated, easy to parse, free of the visual noise built for human persuasion. So Scrunch's Agent Experience Platform (AXP) creates an alternate, lightweight version of your page, Think of it as a "Human View" and an "AI View" running in parallel. It scrunches the page down, in the literal sense of the word, to just what a model needs to understand and cite it accurately, without touching the experience your human visitors actually see.

That distinction matters more than it sounds like on the surface. The compute cost or the "budget" a bot spends crawling and interpreting a page to process your full, heavy webpage versus your scrunched version is dramatically lower. Which means your value proposition, from an AI system's perspective, is dramatically higher. You're not just easier to find. You're cheaper for AI to read. And cheaper-to-read, well-structured content is exactly what gets selected and cited.

In a study with Akamai, pages enabled with Scrunch's AXP saw a 364% increase in brand presence for non-branded AI prompts and a 218% increase in citations across AI-generated results. In a separate case, Runpod used the platform to identify indexing and rendering issues limiting its AI discoverability, and reported a 400% increase in paying customers tied to that work.

The bottleneck every marketer already feels

Talk to almost any CMO or marketer right now and you'll hear the same thing, in slightly different words. They know AI is here. They know people are asking ChatGPT which product to buy, and that their competitors are the ones showing up in that answer. They know they should be optimizing for AEO and GEO.

What they don't have is the tool, the guide, or a clear picture of how to look at their own content the way an AI system does.

And that's the real bottleneck. If you don't know the intent of who or what is visiting your site, and you don't have a feedback loop telling you what content is actually working versus what's just sitting there unread, you can't make the decisions that matter like how to build your asset library, what content should power which campaign, how to build genuinely personalized journeys. It all comes back to one question, Who's visiting your site, and what do they actually want?

That's the gap Scrunch is built to close giving brands a map of who their visitors really are, human and machine, and the tooling to close the distance between the content they already have and what these next-generation AI engines need in order to cite them instead of the competitor.

Conclusion

This is the reason why it is one of the most important acquisition from Sitecore, You would never want your competitors to show up before you in LLMs, Instead you would want your partners and their billions of customers and their brand so they are cited on LLMs.

Your competitors are getting ready to be cited in LLMs, are you ready too? If not that's exactly the conversation worth having next.

Be cited. Not just searched ;-) Cheers !!!

Comments

Popular posts from this blog

Set up leprechaun code generation with Sitecore XM Cloud Starterkit

Hi Sitecorians, It has been amazing learning year so far and with the change in technology and shift of the focus on frontend frameworks and composable products, it has been market demand to keep learning and exploring new things. Reasons behind this blog Today's topic is something that was in my draft from April-May, and I always thought that there is already a good documentation out there for  Leprechaun  and a blog post is not needed, Until I realized that there was so many of us facing same kind of issues and same kind of problems and spending same amount of time, That is where I thought, if I could write something which can reduce that repetitive troubleshooting time, That would really help the community. 1)  In a project environment, if we get into some configuration issues, we resolve them, we make sure we are not blocked and continue, but if you think same issue, same step and same scenario will come to other people, so if we can draft it online, it will help othe...

401.1 Unauthorized with windows authentication error code 0xc000006d

How many of you have faced this hosting issue when you do everything what it takes to run the site with windows authentication but still you are getting the same error again and again? If you think you also have faced the same issue and you tired of reading MSDN KBs for it and still have not found the issue (If KB has solved the issue, well and good, if not you can try this trick),Please Read below Typical scenario In typical hosting with IIS, i did every possible things like enabling windows authentication, changing it in web.config, configuring connection pool, authorization rules, it asks me for window authentication login and despite of entering correct credentials it always fails and keeps on asking for login, and when pressed cancel it gives 401.1 with 0xc000006d error code Solution (Which worked for me at-least after trying for almost 6-9 hrs) You need to change the Loop Back Check in registry so that it allows the host names which you are giving in url are allowed and au...

Sitecore SXA creative exchange export appends hyphen(-) number to the static assets

Hello There, So, today i will be sharing some information which i think will be useful for many as this might come as a blocker just like me, where i was planning for a next sprint for which i was checking prerequisites and suddenly found out that, Export functionality of SXA is not working properly, it was exporting things but i open the page which was exported (index.html), it was loading without any CSS or JS functioning. Problem I have been using SXA but i never had this issue before, where page or site gets exported but when we open the page, it comes up without CSS or JS functioning properly on the page. So, first thing like any developer i opened up the source of the HTML and tried to see why CSS is not working properly and checked its path and found out following  I was surprised at first point as i never saw this behavior, but one thing was confirmed that, SXA is adding these "-number" at the end of CSS when we export so, i tried to de-assemble the DLL just to see wh...