Framer + Sightkick: SEO pages published to your Framer CMS

Updated November 7, 2026

Framer handles the technical side of SEO by itself: sitemap, robots.txt, and a title and description per page. Sightkick adds the pages: written for Google and AI answers by Sightkick, your AI agent or you, and published into a Framer CMS collection on their day. Connecting takes about 2 minutes.

Sightkick makes this page and the integration it describes. Framer facts are from Framer's own help and pages, read in November 2026.

Key takeaways

Framer generates the sitemap and robots.txt and lets you set titles, descriptions and social images per page and per CMS item.
Sightkick connects with one Framer project API key and writes into one CMS collection, then publishes the site on each page's day.
One step stays yours in the Framer editor: bind Meta title, Meta description and Thumbnail in the collection page's settings.
Sightkick never publishes over your work in progress: with unpublished changes, its pages wait for your next publish.
Your own AI agent can run the whole setup from one guide.

How do you connect a Framer site to Sightkick?

You give your agent the guide at sightkick.so/connect/framer.md, plus your Framer project's address and an API key, and it runs five steps. Two of them happen in the Framer editor, because Framer makes API keys only there. Prefer to click? In Sightkick, Settings → Publishing, "Set it up yourself". Every platform Sightkick publishes to is on Integrations → Publishing.

Not on Sightkick yet? Paste your agent "Set up Sightkick for my site by https://sightkick.so/llms.txt", or see how AI answers treat you today with the free AI visibility report. No card for the report.

Connect to Sightkick. No MCP connection yet? Your agent adds Sightkick's MCP server, https://app.sightkick.so/mcp (streamable HTTP, OAuth), by sightkick.so/connect/agent.md (or see connecting your agent). Its sign-in picks your workspace. It then reads the sites (get_settings, view: sites). A Framer connection for this project with status connected means it's done already. A site has one publishing destination, so a second connection is refused. If another one is there, your agent asks you whether to move, and removes it only on your yes (update_connections, action: remove).
Get the project and an API key. Give your agent two things:
- the project's address, from the Framer editor's address bar (https://framer.com/projects/…)
- an API key: in the project, Site Settings → General → API Keys, create a key named Sightkick.
The key is a secret: keep it out of code, commits and anything you share.
Connect. The agent calls update_connections with action connect_framer, projectUrl and apiKey.
```
update_connections {"action": "connect_framer", "projectUrl": "https://framer.com/projects/<id>", "apiKey": "<your Framer API key>", "check": true}
```
Sightkick writes to a collection named like a blog, else the first one it can write to, else it makes a new Blog collection. collectionId "new" always makes one. With check: true, the call lists the collections and stores nothing, so you can choose. blogUrl is where the collection's pages live. It defaults to the site's address + /blog: pass it when the blog lives elsewhere. Sightkick adds the fields it needs to the collection.
Your step in the Framer editor. connect_framer's note says what is left. For a new Blog collection, add a CMS page for it at the blog's address and publish. In every case, bind Meta title, Meta description and Thumbnail in the collection page's settings, so Google reads them. If the project has unpublished changes, pages wait for your next publish.
Test. update_connections with action test and the connectionId. ok: true means Sightkick can publish.

Sightkick then publishes each page to your Framer site on its day. The connection sits in Sightkick under Settings → Publishing, where you change or remove it. If a step fails, its error says what to fix.

Where do you bind the fields in Framer?

In the CMS page's Page Settings. Per Framer's help on CMS meta titles, enter the Meta title field as a CMS variable in Title and the Meta description field in Page description. Under Page images → Social preview, choose CMS Variables and pick Thumbnail. Framer's social previews use 1200 × 630.

What does Framer do for SEO, and what does Sightkick add?

Framer covers how Google reads a page: sitemap, robots.txt, titles, descriptions and social images. It doesn't decide what to publish or track whether AI answers name you. That is the part Sightkick adds.

From Framer's guide to its SEO features and its SEO page, a Framer site gets:

sitemap.xml and robots.txt, generated automatically.
Custom titles and descriptions for the whole site or each page. CMS pages take theirs from CMS fields.
A social preview image per page.
Redirects, canonical URLs, and custom code for JSON-LD structured data.
Agents in the editor that scan a page, prioritize SEO fixes and apply approved updates to metadata, headings, alt text and internal links, plus an AEO scanner for what AI search can find and cite.

What Sightkick adds:

Your buyers' questions, asked daily in AI search: any 3 of ChatGPT, Gemini, Google AI Overviews and Google AI Mode, the 4th as an add-on. 50 prompts on either package.
Keyword research: 100 searches a month, plus new keywords and topics found every week.
Pages written by Sightkick (30 a month on Pro) or by your agent (Standard), each scored on four pillars: answers the search, says something new, can be trusted, easy to quote.
Publishing into your CMS collection, and the site published, on each page's day.
Search Console, synced daily, and improvements to live pages: titles, missing answers, links and stale figures, each change measured.
The pages AI answers cite where competitors are named and you aren't, with a pitch written for each.

What are the ways to publish SEO pages to a Framer CMS?

Four: by hand, with Framer's own agents, with a script on Framer's Server API, or through Sightkick. They differ in who writes the page and who publishes the site.

Ways to publish SEO pages to a Framer CMS, as of November 2026
Way to publish	How the page gets written	Title, description, image	How it goes live	What it uses
By hand	You add a CMS item	CMS variables in the CMS page's Page Settings	You publish the site	Your Framer plan and your time
Framer's agents	You prompt the agent in the editor. It can create collections and write CMS content	The agent can set titles, descriptions and Open Graph images, and audit them	You publish the site	AI credits. Framer's paid plans include monthly credits
Framer Server API	A script of yours writes CMS items, without opening Framer	Whatever your script sets	Your script publishes and deploys	Free during its open beta, per Framer
Sightkick	Your agent, Sightkick (30 a month on Pro) or you, scored before it goes out	Meta title, Meta description and Thumbnail fields, bound once	Sightkick publishes the site on the page's day	A Sightkick plan from $39 a month ($31 billed yearly)

Sources: Framer agents, Framer Server API, Server API launch (free during open beta), Framer pricing, Sightkick pricing.

What does Sightkick write into your Framer CMS?

Each page becomes one item in the connected collection, at the blog's address, with Meta title, Meta description and Thumbnail filled. Sightkick adds the fields it needs to the collection. Pages Sightkick writes are researched, every claim cited or cut, with images. Drafts your agent writes go through the same scoring and fix-it checklist.

Comparison, alternatives, integration and use-case pages work too: Framer gets a collection named after each of those folders, and you add its CMS page once, the same way as the blog's.

What can you ask your agent once Framer is connected?

The numbers below are Sightkick's own, from sightkick.so, which publishes through a webhook rather than Framer. Search Console and AI answers read the same either way. Method: Sightkick's Search Console sync for 11 October to 7 November 2026 (the last 3 days provisional), and its AI answer tracking, 85 unbranded and 15 branded prompts asked daily in 4 AI models, 25 October to 7 November 2026.

Size up a keyword before writing for it.

Research "framer seo" in the US: volume, difficulty, and whether it's worth a page.

research_keywords (US, 4 November 2026): "framer seo", 90 searches a month, difficulty 2. Low competition. This page is the one written for it.

See which AI models name you, and the trend.

Which AI models mentioned us in the last 14 days, against the 14 days before?

On sightkick.so, in answers to unbranded prompts: ChatGPT 15 mentions (3 the 14 days before), Google AI Mode 4 (8), Gemini 1 (0), Google AI Overviews 0 (1). About 1,445 answers per model in each window.

Find the page Google likes, and where the brand name ranks.

What's our top page by impressions in the last 28 days, and where do we rank for our own brand name?

On sightkick.so: /blog/am-i-on-ai, 1,751 impressions, 10 clicks, position 9.4. The brand query "sightkick": 156 impressions, 1 click, position 18.3. The whole site: 18 clicks and 5,953 impressions, against 4 and 4,507 the 28 days before.

Check whether AI answers name you when nobody asks for you.

How often were we named in answers to unbranded prompts, and to branded ones?

On sightkick.so: named in 20 of 5,780 answers to unbranded prompts (0.3%), and in 165 of 220 answers to branded ones (75%). AI answers know the brand when asked about it, and rarely bring it up by themselves. Pages that answer the unbranded questions are the gap.

How do you fix a Framer setup that doesn't publish?

Most failures are one missing step in the Framer editor. The error from the failed step names it.

The blog's address shows nothing. A new Blog collection needs a CMS page at the blog's address, added in the Framer editor and published.
Google shows the site's title, not the page's. Meta title, Meta description and Thumbnail aren't bound yet. Bind them in the collection page's settings.
A page's day came and it isn't live. The project has unpublished changes, so pages wait for your next publish. Publish in Framer.
Pages landed in the wrong collection. With no collection named like a blog, Sightkick writes to the first one it can write to. Connect again with check: true and pick one, or pass collectionId "new" for a fresh Blog collection.
The blog isn't at /blog. Pass blogUrl with its real address when you connect.
No room for another collection. Framer's pricing lists 2 CMS collections on Basic and 10 on Pro. A new Blog collection counts.
The connection is refused. The site has another publishing destination. Remove it under Settings → Publishing first.
Every tool says there's no workspace. Finish setup at app.sightkick.so/start, then run the sign-in again.
Your agent runs headless. Use an API key from Settings → Agents, New key, sent as Authorization: Bearer <key>. See the API and the CLI.

Is it safe to give Sightkick a Framer API key?

Yes, within one project. Per Framer's Server API quick start, a project API key authenticates as the person who created it and is bound to one project, so Sightkick gets that project and nothing else in your Framer account. Keep the key secret like a password.

Sightkick writes to the collection it connected, adds its own fields there, and publishes the site when a page's day comes. It doesn't publish over work in progress: with unpublished changes in the project, its pages wait for you.

In Sightkick, every change your agent makes is logged under its name in the activity feed. Taking a page down is marked destructive, so the agent's app asks you first, and agent edits to live pages can be undone. Signing in, the first card, ending a trial early and who gets access remain yours.

For a review step, set Sightkick's jobs to Manual and keep your agent to drafts. A page without a day stays in Unscheduled. A written page with a day goes live on it, exactly as written.

FAQ

Is Framer good for SEO?

For the technical side, yes: Framer generates the sitemap and robots.txt and lets you set titles, descriptions and social images per page and per CMS item. The pages themselves, and whether AI answers name you, are where Sightkick comes in.

What does Sightkick cost for a Framer site?

$39 a month on Standard ($31 billed yearly), with your agent writing. $99 on Pro ($79 billed yearly), with 30 articles a month by Sightkick. Both have a 7-day free trial with a card, nothing charged for 7 days.

Does it need an API key?

A Framer one, made in Site Settings → General → API Keys. Your agent reaches Sightkick through a sign-in, with no Sightkick key.

Will Sightkick publish my unfinished design changes?

No. If the project has unpublished changes, Sightkick's pages wait for your next publish.

Does Sightkick publish without asking?

Pages with a day go live on it, as written. Pages without one wait in Unscheduled.

Does it run on a schedule?

Yes. You set the pages per month and the hour they go out, and each page has its day on the publishing calendar.

Which AI models does Sightkick track?

Any 3 of ChatGPT, Gemini, Google AI Overviews and Google AI Mode, with the 4th as an add-on. Claude and Perplexity are not tracked.

How your agent connects to Sightkick
Every platform Sightkick publishes to
Pricing and the trial
Free AI visibility report
Other platforms: WordPress + Sightkick and Shopify + Sightkick. Agents: Claude Code and Codex. Proof in Google: Google Search Console