Contentful SEO: headless CMS setup and fast LCP
Short answer Contentful only stores your content; the site your developer built on top of it decides your SEO. Check that every page has its own SEO title, description and slug, that pages reach Google as finished HTML, and that the top photo is resized, served as WebP or AVIF, and never lazy-loaded.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callContentful SEO checklist: what to check and who does it
Contentful is a headless CMS: it holds your words and photos, and a separate front end, written by a developer, turns them into the pages people and Google see. So most SEO on a Contentful site is code, not a settings tab. Go through this table with whoever built the site.
| # | Check | Where it lives | How to tell it's done |
|---|---|---|---|
| 1 | SEO title and meta description on every page type | Fields in the content model, printed by the site code | View the page source: your title and description are near the top |
| 2 | A slug field that must be unique | Content model | Two entries can't publish with the same slug |
| 3 | Pages reach Google as finished HTML | Site code (pre-built or server-rendered) | Your headline and service text appear in the page source |
| 4 | A "hide from search" switch | Field in the content model, printed as a noindex tag | Turning it on adds a robots noindex line to that page's source |
| 5 | Canonical tag pointing to the page's own address | Site code | The source shows a canonical link with the page's own URL |
| 6 | Sitemap and robots.txt | Site code or host | yourdomain.com/sitemap.xml and /robots.txt open |
| 7 | A 301 redirect when a slug changes or a page is deleted | Site code or host | The old address lands on the new page |
| 8 | Business details as structured data | Site code, filled from Contentful fields | Google's Rich Results Test finds it |
| 9 | Resized, modern-format images | Images API settings in the site code | Image addresses include w= and fm=webp or fm=avif |
| 10 | Site updates when you publish | A Contentful webhook to the host | A published change shows up on the live site |
| 11 | Google Search Console connected | Your Google account | The Pages report lists your pages |
Rows 1, 2 and 4 are fields a developer adds once; you fill them in per page. The rest is code. Sitemaps, robots.txt and redirects live on your own domain, so they come from the site's code or host, not the Contentful editor.
Is Contentful good for SEO?
It's neutral. Contentful doesn't make the pages Google reads, so on its own it can't help or hurt your rankings. Its documentation puts the job on the front end:
"To ensure that search engines can consume the SEO metadata, the frontend application needs to render the values in the corresponding HTML meta-tags." (Contentful Docs: Compose content model and SEO)
On hosted builders like Wix or Squarespace, SEO settings come built in. On Contentful, SEO fields exist only if someone adds them. Even pages made in Contentful's visual page builder, Studio, typically come with just a title and slug; its guide shows developers adding SEO title and description fields themselves (Contentful Docs: Experience reference fields for metadata).
The trade: one set of content can feed a website, an app and more, but every SEO feature a builder includes has to be built and kept working.
SEO fields to add to the Contentful content model
Ask your developer for these fields on every content type that becomes a page:
| Field | Contentful field type | Setting | Becomes on the page |
|---|---|---|---|
| SEO title | Short text | Required, unique | The title tag, the blue link in Google |
| Meta description | Short text | Required | The snippet that often shows under the link |
| Slug | Short text | Required, unique | The end of the page address, like /drain-cleaning |
| Hide from search | Boolean | Off by default | A robots noindex tag when on |
| Canonical URL | Short text | Optional, blank by default | A canonical tag; blank means the page's own address |
| Share image | Media | Optional | The picture shown when the page is shared |
Contentful's "unique" setting blocks publishing when another entry already has the same value: it "Validates that there are no other entries that have the same field value at the time of publication" (Contentful Docs: Content types). Use it on titles and slugs, so no two pages share a title or collide on one address. Google's JavaScript SEO guide says unique, descriptive titles and meta descriptions help searchers pick the right result.
Skip a keywords field. Contentful's older Compose SEO model includes one, but Google says:
"The meta-keyword tag is not used by Google Search, and it has no effect on indexing and ranking at all." (Google Search Central: Meta tags and attributes that Google supports)
The fields can sit on each page type, or in one "SEO" content type linked from every page, as Compose did. The second keeps them in one place.
Will Google index a Contentful site?
Yes, if pages reach Google as readable HTML. A 30-second test: open a service page, right-click, choose View Page Source, and search for a sentence on the page. Found it? The page is pre-built or server-rendered. Mostly scripts around an empty container? The page is assembled in the visitor's browser, called client-side rendering.
Google can run that JavaScript, after a wait in a rendering queue. Its advice:
"Keep in mind that server-side or pre-rendering is still a great idea because it makes your website faster for users and crawlers, and not all bots can run JavaScript." (Google Search Central: JavaScript SEO basics)
AI assistants are among those bots. In a December 2024 study of traffic on Vercel's hosting network, Vercel and MERJ found that none of the major AI crawlers rendered JavaScript, including those from OpenAI, Anthropic and Perplexity; Google's Gemini used Googlebot's setup and could. So a page built only in the browser may be blank to ChatGPT and Claude.
| How pages are built | What Google gets first | AI crawlers (2024 study) | Effect on load speed |
|---|---|---|---|
| Pre-built at publish (static) | Finished HTML | Could read it | Usually fastest |
| Server-rendered on each visit | Finished HTML | Could read it | Fast; server time adds a little |
| Built in the browser (client-side) | A near-empty shell, rendered later | Didn't read it | Slow: the main image waits for scripts |
| Dynamic rendering (bots get HTML, people get scripts) | Finished HTML | Depends on setup | Slow for people, as above |
On the last row, Google says "Dynamic rendering was a workaround and not a long-term solution," and recommends server-side rendering, static rendering or hydration instead (Google Search Central: Dynamic rendering as a workaround).
A pre-built site also needs a Contentful webhook, a message to the host when someone publishes, to "trigger a website rebuild" (Contentful Docs: Webhooks overview). Without it, a fixed title can sit in Contentful and never go live.
Two more checks from Google's JavaScript guide:
- Menus use real links with an address, not click handlers or # fragments. Google says it can only discover links that are proper HTML links with an href.
- Look at what Google rendered. In Search Console, URL Inspection shows the rendered HTML. Google: "If the content isn't visible in the rendered HTML, Google won't be able to index it."
Pages found but left out of Google: crawled or discovered, currently not indexed.
How to fix LCP on a Contentful site
LCP (Largest Contentful Paint) is when the biggest thing on the first screen, usually the top photo or headline, finishes showing. Google's PageSpeed Insights counts 2.5 seconds or less as good, up to 4 seconds as needs improvement, and over 4 seconds as poor. How much it moves rankings: Core Web Vitals and Google ranking.
On Contentful sites the usual culprit is the top photo. Check these in order:
| Cause | Fix |
|---|---|
| The photo is served as uploaded | Add Images API settings to its address: w (width, up to 4,000 px), fm=webp or fm=avif (format), q (quality, 1 to 100). Example ending: ?w=1600&fm=webp&q=75 |
| Phones get the desktop-size file | Request smaller widths for small screens |
| The top photo is lazy-loaded | Remove loading="lazy" from that one image |
| The browser doesn't know it matters | Set fetchpriority="high" on that image; web.dev says doing it on more than one or two images makes it unhelpful |
| Images load from a second domain | Contentful serves them from images.ctfassets.net, which costs an extra connection. Preconnect to it; web.dev says serving images from your own domain is best |
| The page is built in the browser | Pre-build or server-render it, so the photo is in the HTML from the start |
| The server is slow to send the page | Pre-build pages, or cache server-rendered pages on a CDN (content delivery network) |
Two facts settle the most common mistakes. Contentful's default format "is the original image format" (Contentful Docs: Images API), so a 5 MB phone JPEG stays 5 MB unless the code asks for less. And from Google's web.dev team:
"Never lazy-load your LCP image, as that will always lead to unnecessary resource load delay, and will have a negative impact on LCP." (web.dev: Optimize Largest Contentful Paint)
web.dev also warns that some tools add lazy loading to images automatically, so check the first one.
Two Contentful limits: AVIF conversion works only from source images up to 9 megapixels, and uploads over 100 MB aren't transformed at all (Contentful Docs: Technical limits). A 12-megapixel phone photo (4,000 × 3,000) is over the AVIF limit, so resize it before upload or use WebP.
Skip AMP. Google "applies the same standard to all pages, regardless of the technology used to build the page" (Google Search Central: About AMP on Google Search).
What Contentful costs, and whether you need it
Contentful's pricing page lists three plans (as archived July 2026; the live page blocked automated reading):
| Plan | Price | Main limits |
|---|---|---|
| Free | $0 | 10 users, 2 locales (language versions), 100,000 API calls and 50 GB of image and file bandwidth a month, no overages; 25 content types and 10,000 records |
| Lite | $300 a month | 20 users, 3 locales, 1 million API calls and 100 GB a month |
| Enterprise | Custom | Studio, the visual page builder, and personalization are offered here |
Hosting and the developer are separate costs. A pre-built site calls Contentful's API when it rebuilds, not on every visit, while photos served from Contentful count toward bandwidth.
For a 10-page service business site, headless is usually more machine than you need: a hosted builder ships the settings in the checklist above without code. Headless pays off when one set of content feeds several sites, apps or languages. If an agency built yours, make sure your business owns the Contentful organization, the code and the hosting account: leaving your agency without losing your site.
Example
Illustrative cases; the numbers are invented.
A dental group with a slow homepage (US dollars)
The hero photo is a 6 MB JPEG, lazy-loaded by the template, and mobile LCP is 5 seconds. The developer adds ?w=1600&fm=webp&q=75, removes lazy loading and marks it high priority. The file drops to about 300 KB. Cost: two developer hours, about $300.
A law firm whose pages are blank in the source
The agency built a browser-only app. View Page Source shows an empty container, Search Console lists most pages as not indexed, and ChatGPT can't describe the practice areas. The firm switches to pre-built pages with a rebuild webhook and keeps its Contentful content.
A landscaper who renamed a slug
The owner changed "services-1" to "lawn-care" in Contentful. The old address now shows a 404, and a $400-a-month ad still points there. The developer adds a 301 redirect at the host, the "permanent server-side redirect" Google recommends when an address changes (Google Search Central: Redirects and Google Search).
FAQ
Does Contentful add title tags and meta descriptions by itself?
No. Contentful stores the text, and the site's code must print it into the page. Check the page source of a few pages to confirm.
Does a headless CMS make a site faster?
Not by itself. Speed depends on how the front end builds pages and handles images; a browser-built page can be slower than a plain site builder.
Do I need a sitemap for a small Contentful site?
Google says a site of about 500 pages or fewer, well linked internally, might not need one. On a headless site nothing makes one automatically, so ask the developer to generate it from your slugs if you want one.
Can I change a page's slug in Contentful?
Yes, but the old address breaks unless a 301 redirect is set up in the site code or at the host. Change slugs only when you must.
Different for you?
- Still choosing a platform: Wix, Squarespace or WordPress for SEO.
- Moving to or from Contentful: traffic dropped after a website redesign.
- Pages found but not in Google: crawled or discovered, currently not indexed.
- Adding business details for Google and AI: local business schema markup.
- Learning the rest of Search Console: Google Search Console for a small business.
- An agency holds the accounts: who owns my website?
- Want a fast site built and kept fast: Website Agent.