Contentful SEO

I manage a 500-page site across three languages. In Contentful, I defined a content type 'Article' with fields for meta title (max 60 chars), meta description (max 160), canonical URL, and schema type. That means every page inherits these fields and editors cannot publish without filling them. I use the API to generate a sitemap with <lastmod> timestamps, which reduced my indexing lag by about two days.

Contentful's CDN delivers content quickly. After I moved a client's blog from a traditional CMS to Next.js and Contentful, Lighthouse scores jumped from 45 to 92. But be careful: a poorly optimised front end can waste that speed. I once saw a team load a 500KB JavaScript bundle on every page, destroying the performance gain. Run a [website speed test](/website-speed-test/) before and after to confirm.

Locales in Contentful make it easy to create field-level translations. I set up hreflang tags using a custom field that outputs language-region codes. That cut duplicate content issues by 80%. I also generate JSON-LD from custom fields for articles, FAQs, and products. This got a client a rich result for a recipe site, increasing CTR by 12%. The structured content modelling is what keeps me coming back.

Contentful gives you no meta boxes, no readability scores, no redirect manager. Everything must be built. I spent two weeks coding a custom preview so editors could see how a snippet looked in Google. It still breaks when the preview API times out.

I originally thought I could use Contentful's App Framework to add SEO features easily. But the App Framework is for extensions, not core SEO functionality. I ended up writing more code than I would with a traditional CMS. When pages fail to index, you cannot rely on a plugin to tell you why. You need to use [Screaming Frog](/screaming-frog/) to simulate Googlebot and then check your front end's server response. I have done this three times this month.

If your content model is not designed for SEO from day one, you will have to rebuild it. I once had to add a 'noindex' field after the site was live because we forgot to exclude some staging pages. That migration took a full sprint and caused a temporary spike in crawled staging URLs. Editors also want to see the meta title as it appears in search results. Without a custom preview component, they cannot. I built one with Contentful's Preview API, but it required a separate staging environment and constant maintenance.

If you need quick SEO wins without a developer, pick WordPress with Yoast or Rank Math. I use it for small sites because you get instant SEO feedback and automatic sitemaps. But for large multilingual sites, WordPress becomes slow and plugin-heavy.

Sanity offers stronger real-time collaboration and customisable previews through its Vision plugin. I considered it for a project with 10 editors, but Contentful's API was more mature and had a larger ecosystem of integrations.

Strapi is open-source and self-hosted. Good if you need full control, but you have to manage infrastructure and SEO plugins yourself. I tried it for a side project and the lack of built-in SEO fields slowed me down significantly.

Decision rule: if your team has three or more developers and you need to support multiple locales, choose Contentful. If you have one developer and want to ship in a week, use WordPress. If you need real-time editing with a smaller team, Sanity. After the migration, track your rankings with a [rank tracker](/rank-tracker/) to measure impact. For a broader toolkit, browse other [SEO tools](/seo-tools/) that complement your headless setup.