Why Contentful Teams Need a Sitemap App – and Why Bright Arboretum Is the Right Answer.

Contentful is one of the most powerful headless CMS platforms on the market – but it provides no native sitemap management. For teams running websites with hundreds of pages across multiple languages, this is a real operational problem. This article explains why that is the case, what it means in practice, and how Arboretum closes the gap.

Contentful

A Powerful But Deliberately Generic CMS

Need a hand with Arboretum or Contentful?

Reach out and let's see how we can solve it together. We know Arboretum and Contentful in and out.

Book a meeting

Why a Dynamic Sitemap in the CMS Matters

Four scenarios where the absence of a sitemap slows down everyday work.

Editors Lose Track of Large Websites

When a website grows beyond 50–100 pages, Contentful’s standard entry list view is no longer sufficient. Editors no longer know which pages exist, where to insert new content, or how the website navigation is structured. This leads to duplicated work, orphaned pages, inconsistent navigation, and a growing dependency on developers for questions editors should be able to answer themselves. A visual sitemap view directly in the CMS solves this: editors see the complete hierarchy at a glance and can navigate independently.

Multilingual Websites Become Unmanageable

Managing multilingual websites without a central sitemap is particularly problematic. When new languages are added, developers frequently need to intervene to replicate the page structure for each new locale. Editors have no way to verify whether all language versions are complete, whether URLs are correctly localised, or whether pages exist in one language but are missing in another. Arboretum solves this with native locale support: the sitemap view can be switched for each configured language, and URL prefixes for localised versions are automatically handled.

Hardcoded Page Structure Creates Bottlenecks

When Contentful is used without dynamic sitemap management, developers often end up hardcoding parts of the website structure in frontend code – navigation, breadcrumbs, internal links. This works short-term but creates real problems long-term: every structural change requires developer intervention and a new deployment cycle. Editors cannot move pages or adjust navigation without requesting technical support. What was intended as a simple CMS solution turns into a system that requires more maintenance overhead than the legacy system it was meant to replace.

App and Website Show Different Structures

Without a shared, SDK-backed foundation for the sitemap logic, a drift frequently develops between what the CMS shows and what the website actually delivers. An editor sees a particular hierarchy in Contentful – but the actual page structure of the website does not match it. The Arboretum SDK ensures that the sitemap logic in the frontend and in the Arboretum app are identical: both are built on the same underlying code. What the editor sees in Contentful corresponds exactly to the structure the frontend processes.

Editors Lose Track of Large Websites

When a website grows beyond 50–100 pages, Contentful’s standard entry list view is no longer sufficient. Editors no longer know which pages exist, where to insert new content, or how the website navigation is structured. This leads to duplicated work, orphaned pages, inconsistent navigation, and a growing dependency on developers for questions editors should be able to answer themselves. A visual sitemap view directly in the CMS solves this: editors see the complete hierarchy at a glance and can navigate independently.

Who Needs Arboretum Most

Not every Contentful project needs Arboretum. These six characteristics are reliable signals.

  • +50 Pages in the CMS

    Once a website manages more than 50–100 pages in Contentful, the native entry view becomes a bottleneck. Arboretum brings the structure back.

  • Multiple Languages or Locales

    Anyone managing multilingual content in Contentful needs a sitemap view that supports locale switching and localised URLs. Arboretum does this natively.

  • Multiple Content Editors

    Teams with multiple editors benefit especially from a shared, clear sitemap view – it reduces coordination overhead and prevents structural errors.

  • Frequent Structural Changes

    Anyone regularly adding, moving, or renaming pages needs a CMS-side sitemap – to make those changes without developer intervention and deployment cycles.

  • Custom Frontend with Next.js or React

    The Arboretum SDK integrates seamlessly into Next.js, React, and other modern frameworks – providing shared sitemap logic between CMS and frontend.

  • Multi-Country or Multi-Brand Platforms

    For enterprise platforms with multiple country sites or brands, Arboretum is a critical foundation for a clear, governable page structure.

Contentful is a headless CMS designed for a very broad range of use cases – websites, apps, digital signage, e-commerce, and more.

This universality is a strength: the content model is completely open, and the API-first architecture enables integration with any frontend system. At the same time, it means Contentful makes no assumptions about the structure of a website.

There is no native concept of “pages”, no native concept of “parent-child relationships”, and therefore no native sitemap view. For developers this is usually not a problem – they see the content model and understand how entries are connected. For content teams without a technical background, however, it is a real barrier: they see a list of entries, but have no sense of which ones are pages, how they are hierarchically arranged, and what appears where on the website.

How Arboretum Solves the Problem

Minimal impact on the content model. Maximum benefit for editors and developers.

The Arboretum App (for editors)

The Arboretum Sitemap App is installed directly into the Contentful environment – via the Contentful Marketplace. During setup, you define which content types represent pages and how parent-child relationships are encoded. This requires minimal adjustments to the existing content model – the conventions are lightweight and non-intrusive. After setup, editors see a complete visual sitemap inside Contentful: the full page hierarchy of the website, navigable, filterable by language, and with direct links into the entry editor. The app stores no data outside Contentful – all information remains in your own Contentful instance.

Install from Contentful Marketplace

The Arboretum SDK (for developers)

The Arboretum SDK is a framework-agnostic TypeScript library that exposes Arboretum’s sitemap logic to developers as a programmatic interface. It enables mapping of URL paths to content entries, traversal of the page tree, and sitemap refreshing. Crucially: the app and SDK share the same underlying code. This means the page structure the editor sees in Contentful corresponds exactly to the logic the frontend processes – no drift, no inconsistencies. The SDK works with Next.js, React, Nuxt, and other modern frameworks and is available as open source on GitHub.

Bright Global
  • Expertise
  • Work
  • Approach
  • Partners
Arboretum with Next.js
Bright IT
  • For Digital Leaders
  • For Technical Leaders
  • For Agency Partners
  • Overview
  • References & Industries
  • HDI Global
  • Swarovski Optik
  • Mischek
  • Dachstein Salzkammergut
  • Salzburg AG
  • Tyrolit
  • Vaillant
  • Our Philosophy
  • Direct-to-Expert
  • Nearshoring 2.0
  • Security & Compliance
  • Partner Overview
  • Storyblok
  • Optimizely
  • Contentful
  • Shopify
  • Medusa
  • commercetools
  • Ecosystem Integrations
Blog
Contact
Bright IT
Insights
  • Legal Notes
  • Privacy Policy
  • Follow us on LinkedIn
© 2026

Partners