StrapiStrapi

Publish SiteLift articles into a Strapi collection type with an API token, with your fields mapped, images uploaded to the Media Library and Blocks or Markdown bodies.

How it works

SiteLift writes each article as an entry in one Strapi collection type through the REST API, using an API token you create in the Strapi admin. You give SiteLift your Strapi URL, the collection’s API ID and the token, then match SiteLift’s fields (title, slug, body, cover image, SEO fields and more) to the fields of your content type. Every article is created as a published entry; republishing an edited article updates the same entry, found by its slug. Strapi 5 is supported, and Strapi 4 works with the version switch in the connect dialog.

Setup Guide

  1. 1

    Create an API token

    In the Strapi admin open Settings → Global settings → API Tokens and click Create new API Token. Name it SiteLift, set Token duration to Unlimited and Token type to Custom.

    Under your articles collection tick find, findOne, create, update and delete. Under Upload tick upload (and destroy, so the test image from the mapping check is removed again). Save and copy the token: Strapi shows it once. A Full access token works too.

  2. 2

    Prepare the collection type

    Use a collection type for your posts (the Content-Type Builder is only editable in development mode, so add fields there before you deploy). SiteLift matches fields by name, so these are mapped automatically: Title (Short text), Slug (UID), Body or Content (Rich text), Excerpt (Long text), Cover or Featured image (single Media), Meta title and Meta description (Short text), Tags (Long text or JSON) and Published date (Date or Datetime).

    A UID field for the slug is strongly recommended: SiteLift finds an article’s entry by it when you republish. Strapi only fills a UID automatically in the admin panel, so SiteLift always sends the slug itself.

    Note the collection’s API ID (plural) in the Content-Type Builder, for example articles. It is the path of the REST route, /api/articles.

  3. 3

    Connect

    In SiteLift open Settings → Integrations and choose Strapi. Enter the Strapi URL (the address the API is served from, without /api or /admin), the collection API ID and the token, and pick your Strapi version.

    For exact field detection, paste the content type’s schema.json from your Strapi project, at src/api/<name>/content-types/<name>/schema.json. An API token cannot read Strapi’s content-type definitions, so without the file SiteLift reads the fields from an existing entry and asks Strapi which fields are required. That works when the collection has at least one entry with its fields filled in; the file is exact in every case and also gives SiteLift your enumeration values and which fields are Blocks or Markdown.

    Optionally give the public URL pattern of your front end, such as https://blog.example.com/posts/{slug}. Strapi is headless and does not know where an entry appears, so without a pattern SiteLift shows no live link for Strapi articles.

  4. 4

    Map the fields and run the test

    SiteLift proposes a mapping; adjust it where needed. Required Strapi fields must get a value, either a SiteLift field or a fixed value (enumerations offer their options). The test writes a draft entry from sample content so Strapi’s own validation runs, then deletes it again. When it passes, click Connect.

  5. 5

    Publish

    Articles publish on your content calendar schedule as published entries. Your front end picks them up through its usual Strapi queries; if it builds statically, trigger a rebuild from a Strapi webhook on entry publish.

Tip

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

What gets published

  • Rich text (Blocks) and Rich text (Markdown). Map the body (HTML) to a Blocks field and SiteLift converts it to Strapi’s Blocks format: headings, paragraphs, bold, italic, underline, strikethrough, inline code, links, lists, quotes, code blocks and images. Blocks has no tables or horizontal rules, so table rows become paragraphs and rules are left out. A Markdown field takes the body as Markdown, with tables kept.
  • Title and featured image. Your front end renders both from their own fields, so the H1 and hero image are removed from the body. Map the featured image to a Media field.
  • Images. Strapi does not accept image links in Media or Blocks fields, so SiteLift downloads each image and uploads it to your Media Library with its alt text, then references the uploaded file. Strapi refuses SVG uploads by default, so an SVG image is left out of the body. Images in a Markdown body stay as links to SiteLift’s CDN.
  • Structured data. The JSON-LD is a separate SiteLift field. Map it to a JSON or Long text field and output it in your page head.
  • Relations, components and dynamic zones. Shown in the mapping but not filled by SiteLift yet. If one of them is required, make it optional or fill it in Strapi.
  • Taking comparisons offline. On Strapi 5, unpublish the entry manually in the Strapi admin; SiteLift keeps comparison publishing available and explains the manual step. On Strapi 4, SiteLift clears publishedAt to unpublish when the collection has Draft & Publish enabled. Without it, take the content offline in your CMS or front end.

Competitor comparison pages

Supported as blog posts in your existing Strapi collection 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

  • 401 from Strapi. The token is wrong, expired or was regenerated. Create a new token under Settings → API Tokens and reconnect.
  • 403 from Strapi. The token lacks a permission. Reading needs find and findOne on the collection, publishing needs create and update, the mapping test needs delete, and images need Upload → upload.
  • 404: no collection at /api/…. The API ID is not the plural one, or the content type is a single type. Copy the API ID (plural) from the Content-Type Builder, for example articles.
  • SiteLift could not detect the fields. The collection is empty and has no required fields, so there was nothing to read. Paste the schema.json in the connection settings, or create one entry in Strapi and try again.
  • 413 when uploading an image. The proxy in front of Strapi (often nginx with its 1 MB default) refuses the file. Raise client_max_body_size or the equivalent on your host.
  • Validation error on a field. The message names the field Strapi refused, for example a UID that is not unique or an enumeration value outside its options. Fix the mapping or the field in Strapi, then republish.

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