Muttdata has published around 60 customer stories, more than most consultancies ten times its size, but a buyer cannot use them. The sitemap holds more than 40 stories under /case-study/ and 18 more under /success-stories/. The same story appears in both: the Mabe story sits at both addresses under an identical slug with two different headlines, and the Trafilea forecasting story is also published twice. The /case-studies hub shows six cards per page, has no filter for industry, solution or platform and no search, and links only to the /success-stories/ versions, so a bank looking for a Databricks migration in financial services has to page through a carousel to find it. Older addresses still carry dates and typos.
First action
Export every /case-study/ and /success-stories/ address into one sheet and mark the pairs that tell the same story.
How to measure it
Story-page contact requests
- Now
- –
- Target
- 2x the current monthly count
- By
- 90 days
Steps
List every story
Export both address families from the sitemap into one sheet with customer, industry, solution, platform, country, headline number and date.
Content lead 1 day
Pair the duplicates
Mark stories that exist twice, such as Mabe and Trafilea, and pick the version to keep. Keep the short summary as the top of the long page.
Content lead 1 day
Choose one address family
Pick /case-study/ or /success-stories/, write clean slugs without dates or typos, and prepare a redirect map from every old address.
Webflow developer 2 days
Tag the collection
Add industry, solution, platform, country and headline-result fields to the Webflow collection and fill them for every story. Check the template for unfilled fields and leftover default text.
Content lead 3 days
Rebuild the hub
A grid with filters and search, 12 or more cards per view, the headline number on each card, and a contact or booking button on every story.
Webflow developer 3 days
Redirect and resubmit
Apply the redirects in English and Spanish, update internal links from the homepage, industry and Databricks pages, and resubmit the sitemap.
Webflow developer 1 day
Link filtered views
Each industry, solution and Databricks page links to its own filtered view of the library.
Head of Marketing – LATAM & US 1 day
Measure
Track story views, filter use and contact requests that began on a story, monthly in HubSpot and Google Analytics.
Marketing operations monthly
Why it works
Make one library. Choose a single address family, redirect the other to it so each story has one page, and tag every story with industry, solution, platform (Databricks, AWS), country and the headline number. Rebuild the hub as a filterable grid with search, showing the result on each card (for example "reporting from 15 days to 2"). Put a short and a long version on the same page instead of on two addresses. Link each industry and solution page to its filtered view, and mirror the structure in Spanish.
Enterprise buyers and partner sales teams look for proof that matches their own industry and stack before they take a meeting. One page per story also concentrates search and AI-assistant signals that are split between two addresses today, which matters for a team whose new marketing lead is asked to build a content engine that ranks in search and in AI answers.
Ready to use
ChecklistStory library launch list
[ ] One sheet with every story and its tags [ ] Duplicate pairs marked, one version kept [ ] One address family, clean slugs, redirect map [ ] Industry, solution, platform, country and headline-result fields filled [ ] Hub with filters, search and the result on each card [ ] Spanish mirror with the same tags [ ] Filtered views linked from industry, solution and Databricks pages [ ] Contact or booking button on every story [ ] Sitemap resubmitted and redirects checked
Risks and how to handle them
Redirects lose search traffic to older stories
Redirect each old address to the exact matching story, never to the hub, and watch Search Console for four weeks.
Tagging 60 stories stalls
Tag the 20 most viewed stories first and launch the filters with those.
Evidence
- Your websiteCase-study hub (checked November 16, 2026): /case-studies shows six cards per page with no industry, solution or platform filter and no search; every card on the first two pages links to a /success-stories/ page, and the only calls to action are "Read Article" and "Contact Us".Source
- Your websiteSitemap (checked November 16, 2026): more than 40 English customer stories under /case-study/ and 18 more under /success-stories/, each with a Spanish mirror and hreflang links; about 120 /insights/ articles and 27 /events/ pages; older story addresses carry dates and typos, for example "/case-study/2022-11-09-cdojo-cast-study".Source
- Your websiteThe same customer story is published at two addresses: the Mabe story sits at /case-study/ and at /success-stories/ under the identical slug with two different headlines ("Mabe Case Study | Impression Share Optimization" and "How Mabe Maximized Impression Share"), and the Trafilea forecasting story sits at both /case-study/ and /success-stories/smarter-forecasts-fewer-stockouts-better-margins.Source
- HiringHead of Marketing – LATAM & US (posted October 20, 2026, reports to the Global CRO): "Own Marketing's contribution to pipeline, not MQL volume."; "Define lead and attribution standards with Sales, and make sure both teams adopt them."; "Lead a content engine that ranks in search, GEO, and LLMs"; "Build a brand in a market where we're still unknown"; "case studies with real numbers, and memorable events"; requires "HubSpot and funnel dashboards" and ABM experience; the 12-month goal is "an AI-enabled team that grows impact faster than headcount".Source