Rankealo connects for each publish, writes the item using your collection's field IDs, then publishes a new version and deploys it (this is what makes the article go live). Each article is created once and updated in place afterwards. Connections saved with the old "Site ID" setup no longer work — reconnect with the project URL and a new API key.

What you'll need#

A Framer project with a CMS collection for blog content, including a Rich Text field for the article body.
A Framer API key for that project. The Server API is per-project and its availability depends on your Framer plan and Framer's release status — check Framer's documentation. Treat this integration as experimental until Test Connection succeeds.
Your published site domain (e.g. myblog.framer.website).

Step 1 — Get your credentials#

1
Open your Framer project and copy its URL from the browser (e.g. https://framer.com/projects/MySite--aBc123).
2
In the project, open Site Settings → General and generate an API key. Keys are per project; store it securely.
3
Create or identify your blog CMS collection and note its name.
4
Enter your published site domain (e.g. myblog.framer.website).
5
If your fields are not called title / content / description / image, enter their names (or IDs) in the field mapping below.

Reference: Framer Server API.

Step 2 — Connect in Rankealo#

In Rankealo, open Integrations, choose Framer, and fill in these fields:

Field	Required	Where to find it
Framer project URL	Required	e.g. https://framer.com/projects/MySite--aBc123.
API Key	Required	Site Settings → General in your Framer project.
Collection name or ID	Required	The CMS collection that holds blog posts.
Site Domain	Required	Your live Framer domain, e.g. myblog.framer.website (used to record the published URL).
Content field	Optional	Rich Text field for the article body (default: a field named content/body).
Description field	Optional	Field for the meta description (default: description/excerpt/summary).
Title field	Optional	Text field for the title (default: title/name).
Featured image field	Optional	Image field (default: image/featured image/cover).
Collection URL path	Optional	Path of your collection pages, e.g. blog. Blank uses the collection name; "/" means the site root.

Click Test Connection. Rankealo verifies your credentials — you must see a successful test before Save Integration becomes available.

Updating credentials later

Secrets are write-only. When you reopen a saved integration, secret fields show “leave blank to keep existing” — only re-enter them if you are rotating keys.

What gets synced#

When Rankealo publishes, each article carries:

TitleThe article title.
ContentFull article body as HTML (or markdown where the platform supports it).
Meta descriptionSEO meta description / excerpt, where the platform has a field for it.
SlugGenerated from the title when the item is created and kept on update.
Featured imageSet only if the collection has an Image field.

Slug, featured image, tags and SEO title depend on the platform and your field mapping. Each platform guide lists exactly what it sends.

Updates & re-publishing#

Rankealo tracks the post it created for each article. When an article is edited — or automatically re-optimized by Improvements — Rankealo updates the same post in place rather than creating a duplicate.

Troubleshooting#

Connection test fails+

Verify the project URL and the API key (Site Settings → General), and that the collection name matches. Confirm your Framer plan includes the Server API.

Rankealo asks you to reconnect Framer+

The integration was saved with the old Site ID setup. Enter the project URL and a new API key.

Articles are saved but not live+

The item was written but the publish/deploy step failed (plan limits, Framer outage). Publish the site from Framer, or update the article in Rankealo to retry.

No usable content field+

Add a Rich Text field to the collection, or enter its name under "Content field".

Framer