ContentfulContentful

Publish SiteLift articles as entries of a Contentful content type through the Content Management API, with the body as Rich Text, images as Contentful media and your own fields mapped.

How it works

SiteLift writes each article as an entry of one of your Contentful content types, using the Content Management API and a personal access token. You paste the space ID, the environment and the token, pick the content type, and match SiteLift’s fields to its fields. Every article is created and published; republishing an edited article updates the same entry, found by its slug. Images are uploaded to your space as media. Contentful is headless, so your own site decides how and where entries are shown.

Setup Guide

  1. 1

    Create and authorize a personal access token

    In Contentful open the space you publish from, then Settings → CMA tokens and click Create personal access token. Name it SiteLift, choose an expiration date, click Generate and copy the token right away: it starts with CFPAT- and is shown once.

    Return to the CMA tokens list and open Authorize access beside the token. Authorize the organization that owns your space if requested, and complete SSO if prompted. Organizations with token access control require this step; an Active token can still return 401 until organization access is authorized.

    Organization authorization does not replace space permissions. Your role in this space must also be allowed to create and publish entries and media (Admin or Editor do; Author-style roles often cannot publish). See Contentful’s token authorization instructions.

  2. 2

    Find the space ID and environment

    Open Settings → General and copy the Space ID. It is also the part after /spaces/ in the Contentful address bar.

    The environment is master unless you publish from another one. Environment aliases work too. Spaces with EU data residency are not supported yet.

  3. 3

    Prepare the content type

    Use an existing blog content type or add one under Content model. SiteLift matches fields by name, so these are mapped automatically: Title (Short text), Slug (Short text, unique), Body or Content (Rich text), Excerpt (Long text), Featured image (Media, one file), Meta title (Short text), Meta description (Long text), Tags (Short text, list) and Published date (Date & time).

    The slug field is how SiteLift finds an entry again, so it must be a Short text field. A JSON object field (for example Schema) can receive the article’s structured data.

  4. 4

    Connect and map the fields

    In SiteLift open Settings → Integrations, choose Contentful and enter the space ID, the environment and the token. Add your article URL pattern, such as https://example.com/blog/{slug}, so SiteLift can link to published articles. Pick the content type.

    SiteLift proposes a mapping from the field names and types. Fields with a fixed list of values take one of those values; reference fields take an entry you pick from the linked content type. Test publish writes a draft entry from sample content and deletes it straight away, so Contentful’s own validations run before you save.

  5. 5

    Publish

    Articles publish on your content calendar schedule. Each entry is published, not left as a draft, so your site can fetch it from the Content Delivery API at once (or rebuild, if it is static and listens to Contentful webhooks).

Tip

Once connected you never log into Contentful to publish. Articles go live on your SiteLift schedule, and edits made in SiteLift are pushed again when you republish.

What gets published

  • Title and featured image. Your site renders them from their own fields, so the H1 and hero image leave the body. The featured image is uploaded as a media asset with the alt text as its title and description.
  • Rich text body. Headings (H2 to H6), paragraphs with bold, italic, underline and code, links, numbered and bulleted lists, quotes, dividers and tables are converted to Contentful Rich Text. Code blocks become code-formatted paragraphs, because Rich Text has no code block. When the field turns some formatting off, that content is kept as plain paragraphs instead of being rejected.
  • Long text body. Map Content (HTML) to a Long text field and it arrives as plain text with paragraphs; map Content (Markdown) instead if your site renders Markdown. Rich text is the better choice for formatting and images.
  • Images. Images in the article become embedded media in the Rich Text body. Each image is uploaded once and reused when you republish; an image Contentful cannot process is left out rather than failing the article. Every image counts as one record on your plan.
  • Locale. Entries are written in the environment’s default locale. Other locales on an existing entry are kept. If required fields are localized, Contentful can require translations in additional locales before publication. Test publish checks this requirement too. SiteLift does not translate articles into those locales automatically.
  • Structured data. Map JSON-LD schema to a JSON object (or Long text) field and add it to the page head in your site’s template.
  • Article URL. Contentful entries have no public address. SiteLift builds the link from your URL pattern; without one, articles publish normally but have no View link.
  • Republishing. The mapped fields are overwritten; fields you did not map keep what you entered in Contentful.

Competitor comparison pages

Supported as blog posts in your existing Contentful content type, using the same connection and field mapping as your articles. They use the same blog layout and feed as your articles. No extra collection, content model, template or comparison mapping is needed. Existing supported tag or category fields can group them as Comparisons; no new field is required. SiteLift does not create a separate comparison hub or add a link to one. The blog controls the URLs, so the comparison URL prefix does not apply.

Troubleshooting

  • Contentful answered 401. First open Settings → CMA tokens → Authorize access beside the token and check that it is authorized for the organization that owns your space; complete SSO if prompted. An Active token can still lack organization authorization. Then check that it was copied correctly and has not expired or been revoked. If you replace the token, authorize the new one too, then retry the connection in SiteLift.
  • Contentful answered 404 for the space. The space ID or environment is wrong, or the token’s user has no access to that space. Check Settings → General and the environment name.
  • Contentful answered 403. Your role cannot create or publish entries or media in this space. Ask a space admin to give your user an Editor or Admin role, or to create the token.
  • Publication requires another locale, such as de-DE. The field mapping can be correct while a required translation is missing. SiteLift writes the environment’s default locale and preserves existing translations. If the other language is optional, open Contentful Settings → Locales, select that locale and enable “Allow required fields to be empty for this locale”. If translations are mandatory, add the missing values to the entry before publishing. A fallback locale does not satisfy this requirement.
  • Publish failed with a validation error. The content type has a rule the article does not meet, such as a size limit, a pattern on the slug or a required field with no value. The error names the field; adjust the rule in Contentful or the mapping in SiteLift.
  • A field is out of date or rejected. A field was removed, renamed or changed type in the content model. Open Integrations → Contentful → Edit field mapping and pick again.
  • The entry is published but not on my site. Contentful does not render pages. Your site fetches entries from the Content Delivery API; a static site needs a rebuild, usually triggered by a Contentful webhook on publish.

Still stuck? Use Test Connection on the Integrations page; the message comes straight from Contentful. Or write to support.