Storyblok – the headless CMS where the marketing team publishes independently

Definition

Storyblok is a headless CMS from the Austrian company Storyblok GmbH (founded in 2017) that stands out for its visual editor with live preview. It is often the strongest choice when editors need to work independently.

Storyblok is a headless CMS from the Austrian team behind Storyblok GmbH (founded in 2017). The platform stands out from the other major headless CMSs on one specific point: it has a visual editor with live preview that lets editors see exactly how the content will look on the front end while they are editing. That is not a given in the headless world – it is a deliberate attempt to combine developer-friendliness with an editing experience reminiscent of WordPress or Webflow.

For teams where marketers or content producers need to work independently, without involving developers, Storyblok is often the headless option we look at first.

How Storyblok is structured

Storyblok is built on three central concepts:

• Stories. Stories correspond to pages or content units. Each story has a URL path, a number of fields and usually a number of blocks.
• Blocks (components). Content is assembled from small reusable components – a hero block, a text-and-image block, a pricing table, a feature list. These components correspond to React or Vue components on the front end, so the same data model describes both how content is edited and how it is rendered.
• Visual Editor. Storyblok loads your website in an iframe in the editor, and editors click directly on elements to edit them. Content is updated immediately in the preview, and the front end can be built in any modern framework – Next.js, Nuxt, Astro, SvelteKit and so on.

What Storyblok is good at

• The editing experience. Storyblok has the strongest editing experience in its category: a visual editor with live preview, drag-and-drop blocks and fields that make sense without training. Marketers become productive in days, not weeks.
• Component-based architecture. Because blocks map 1:1 to front-end components, developers and editors end up sharing the same mental model. That means fewer misunderstandings, faster implementation of new layouts and fewer cases of "the design doesn't work in the CMS".
• Internationalisation. Storyblok offers two models – field-level translation and folder-level translation – and both are well supported. For Swedish clients with export ambitions this is a plus; Swedish companies that need several languages are a typical fit for the platform.
• Image Service and CDN. Built-in image optimisation with sensible defaults, focal points and on-the-fly transformations.
• A good pricing model. On price, Storyblok sits between Sanity and Contentful. The free tier is useful for small projects and the upgrade steps are reasonable.
• Real-time collaboration. Several editors can work in the same story at the same time.

Where Storyblok is not the obvious choice

• The visual editor requires the front end to be configured for it. For live preview to work, your website has to be set up to load in Storyblok's iframe with its "Bridge". It is not difficult – but it takes work and has to be maintained.
• The data model is less rigorous than Sanity's. Storyblok is pragmatic. It leaves more in the developer's hands, which is both an advantage and a disadvantage. The structure can get messy if you do not set conventions early.
• A less powerful query language. Storyblok has a REST API and GraphQL, but nothing in the same class as Sanity's GROQ. For complex joins and aggregations you need to make more calls or restructure the data model.
• Less advanced roles and permissions than Contentful. For very large organisations with complex approval flows, Contentful is stronger. Storyblok is more than enough for teams of up to a few dozen editors.
• A smaller Swedish ecosystem. Fewer agencies in Sweden have as much experience of Storyblok as of WordPress or Webflow.

When we recommend Storyblok

At SEOS Design we lean towards Storyblok when:

• The marketing or content team needs to be self-sufficient, without developers having to be involved every time something is published.
• The website has many landing pages that are rebuilt every quarter.
• Internationalisation is an explicit part of the roadmap.
• The front end is built in Next.js, Nuxt or Astro – a set-up we go through in AI-assisted web development.
• The design system is component-based and the development team is used to that way of thinking.

We do not recommend Storyblok when the data model is extremely complex, with many cross-references and historical migrations that need strict versioning (Sanity is the better choice there), when compliance and enterprise governance are central (Contentful is better there), or when it is a marketing website where Webflow is the faster choice.

Storyblok vs Sanity vs Contentful

Some quick rules of thumb:

• Sanity for teams where the data model and structure are at the core, where the developers own publishing, and where the front end is a modern code stack.
• Contentful for large organisations with enterprise requirements, internationalisation across many markets, and governance that has to stand up to audit.
• Storyblok for teams where the marketing department needs to be able to work independently, where visual preview matters a lot, and where you want a reasonable compromise between flexibility and editor-friendliness.

For an in-depth look at choosing a platform for a larger organisation, see Website platforms for large companies.

What does Storyblok cost?

Storyblok has a free plan that is enough for developers who want to try the platform or build smaller projects. The paid plans have a much lower entry price than Contentful's, which makes Storyblok realistic even for smaller teams – the cost then rises with the number of users, environments and features such as advanced workflows. For larger organisations, the enterprise tier is priced on request.

Prices change regularly, so check the current levels on Storyblok's pricing page before you budget. Also allow for the implementation cost: in a headless project, the CMS licence is rarely the biggest item – front-end development is.

Storyblok and SEO

• Per-page SEO in the editor. Storyblok lets you define SEO fields (title, description, canonical, OG image, indexing) as standard fields on story types. Having editors see and fill them in as part of their normal flow is a big SEO win.
• Structured data. Because blocks are typed and well modelled, schema markup can be generated automatically at component level. An FAQ block can automatically render FAQ schema and a review block review schema – the value lies in machine-readable structure that AI search services can cite, not in rich snippets.
• Speed depends on the front end. Storyblok itself is fast. SEO-related performance – Core Web Vitals – depends on your front end. In practice, Storyblok websites built in Next.js or Astro score very well in Lighthouse.
• Preview as an SEO tool. The visual editor lets editors see how the title, meta and OG image look before publication. When editors see the consequences straight away, there is less risk of sloppy metadata going live.

Storyblok for e-commerce

In e-commerce, Storyblok is used as a content layer on top of an e-commerce platform – a set-up often called composable commerce. The e-commerce platform owns products, inventory and checkout; Storyblok owns landing pages, campaign areas, guides and editorial content. Ready-made integrations exist for Shopify, among others, so that editors can pull product data straight into their blocks.

The set-up suits shops where content and campaigns are a central part of sales and the team wants to be able to rebuild pages without developer input. For a smaller shop, the e-commerce platform's built-in content tools are usually enough – composable commerce is something you grow into, not a starting point.

Migrating to Storyblok

Migrating to Storyblok from WordPress or Webflow is usually straightforward – content exported in a structured format can be imported via the CMA API. The biggest challenge is remodelling content into component-based blocks; the payoff is a model that is clearly better suited to further development. We explain how to plan a move without losing your Google rankings in Migrating a website without losing rankings.

Migrating from Storyblok to another CMS is entirely possible – the data is accessible via the API and can be exported.

Summary

Storyblok is a headless CMS that takes the editing experience seriously. For teams where marketers and content producers need to be able to work independently, it is often the strongest choice in its category. It is not as structured as Sanity or as enterprise-oriented as Contentful – but it strikes a pragmatic middle ground and solves the most common real-world problems that small and medium-sized Swedish companies and scale-ups run into. If your problem is publishing speed rather than structure, start here.