Framer
Publish SiteLift articles into a Framer CMS collection through the Framer Server API, with the title, slug, body, image and your own fields mapped.
How it works
SiteLift writes each article as an item in one of your Framer CMS collections, using the Framer Server API and a project API key. The Server API is Framer’s official way to edit a project from outside the editor; it is in open beta and free while the beta lasts. You paste the project URL and the key, pick the collection, and match SiteLift’s fields to the collection’s fields. Republishing an edited article updates the same item. Framer only changes your live site when the site is published, so by default articles wait in the CMS until you click Publish in Framer.
Setup Guide
- 1
Create a project API key
Open the project in the Framer editor and open Site Settings (the gear icon, or Cmd+K and type “open settings”). In General, scroll to API Keys, click Generate and copy the key. Framer shows it once.
Copy the project URL from the browser address bar too. It looks like
https://framer.com/projects/Website--aBcD1234…. The address of your published site (….framer.websiteor your own domain) does not work here.A key belongs to one project and acts as the Framer user who created it, so create it with an account that can edit the CMS (and publish the site, if you want SiteLift to publish). Framer has not said which plans the Server API will be limited to; if you do not see the API Keys section, your plan does not offer it yet.
- 2
Prepare the collection
Use a collection you created in Framer. Collections synced by a plugin (Notion, Airtable or another tool) are read-only to everyone else, so SiteLift does not list them. SiteLift matches fields by name, so these are mapped automatically: Title (plain text), Content or Body (formatted text), Excerpt (plain text), Featured image or Image (image), Meta title and Meta description (plain text), Tags (plain text), Category (option) and Published date or Date (date).
The slug is not a field in Framer: every item has one. SiteLift sets it from the article slug and uses it to find the item again when you republish. Give the collection a detail page (for example
/blog/:slug) so SiteLift can record each article’s public URL. - 3
Connect and map the fields
In SiteLift open Settings → Integrations, choose Framer and paste the project URL and the API key. Pick the collection.
SiteLift proposes a mapping: Slug gets the article slug, the field your slugs are based on (usually Title) gets the title, the formatted text field gets the article body and the image field gets the featured image. Option fields take a fixed value or a SiteLift value that matches one of the options by name; reference fields take an item you pick from the linked collection. Test publish writes a draft item from sample content and deletes it straight away, so Framer’s own checks run before you save.
- 4
Choose who publishes the site
Framer publishes a whole site at once: everything that has changed since the last publish goes live together, including unfinished design work on your pages. That is why the setting Publish the Framer site after each article is off by default. With it off, each article is saved to the collection as a published (not draft) item and goes live the next time you click Publish in Framer.
Turn it on only when SiteLift is the only one editing the site. SiteLift then publishes the site after every article and pushes it to your custom domain, so new articles go live on schedule without you opening Framer.
- 5
Publish
Articles publish on your content calendar schedule. The URL SiteLift records is your site’s address plus the collection’s detail page path; it works once the site has been published.
Tip
What gets published
- Title and featured image. Your detail page shows the title and image fields, so the H1 and hero image leave the body. The image field gets the hero’s alt text.
- Body. Sent as HTML into the formatted text field: headings, paragraphs with bold, italic, code and links, lists, quotes, code blocks, tables, dividers and images. Classes, inline styles and layout wrappers are removed, because Framer styles formatted text from your own text styles.
- Images. Framer downloads the featured image and inline images from SiteLift and hosts them itself, so they count towards your project’s storage like any image you add.
- Structured data. A Framer CMS item has no place for JSON-LD, so the article’s schema markup is left out.
- Republishing. The mapped fields of the item are overwritten; fields you did not map keep what you entered in Framer.
- Taking comparisons offline. Automatic site publishing is opt-in. With Publish the Framer site after each article enabled, SiteLift can unpublish a comparison item and publish the site to apply it. Otherwise take the item offline in Framer and publish the site yourself; SiteLift shows a manual removal note.
- Plan limits. Framer plans cap the number of CMS items per project. When the collection is full, Framer refuses new articles until you upgrade or remove items.
Competitor comparison pages
Supported as blog posts in your existing Framer collection, 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
- Framer refused the API key. The key was deleted or regenerated, or it belongs to another project. Generate a new key in Site Settings → General → API Keys for this project and reconnect.
- SiteLift asks for the editor URL. You pasted the published site address. Open the project in the Framer editor and copy the framer.com/projects/… URL from the address bar.
- My collection is not in the list. Collections synced by a plugin are read-only and are not offered. Create a collection in Framer’s CMS and pick the collection again.
- The article is in the CMS but not on the site. Publishing the site is off, so the article goes live the next time you publish in Framer. Turn on “Publish the Framer site after each article” only if nobody else edits the site.
- Framer is busy or did not answer. The Server API is in beta and limits how many sessions a key can run at once. Publish the article again in a minute; if it keeps happening, check that no other tool uses the same key.
- A field is out of date or rejected. A field was renamed to a different type, removed, or an option no longer exists. Open Integrations → Framer → Edit field mapping and pick again.
Still stuck? Use Test Connection on the Integrations page; the message comes straight from Framer. Or write to support.