Skip to main content

How do I connect my Framer blog?

Vitalik May avatar
Written by Vitalik May
Updated over a month ago

Critical: before you begin, clear Framer website cache as described here: Framer Sync Error

1. Open Menu -> Connect my Blog -> Framer

2. Copy the provided API key and click the Connect button. If you need to retrieve your API key later, you can find it in Menu -> Blog Sync Status.

3. Navigate to your Framer dashboard and install the SEObot Framer plugin. You can also find the SEObot plugin in the Framer marketplace.

4. Framer will prompt you to create a collection. Please give your collection a name.

Create a collection for SEObot articles

5. You will then be asked to enter the SEObot API key. Input the key provided by SEObot in step 2 above. Click the Save & Sync button.

Enter SEObot API key

6. Create Index and Details pages using the SEObot collection.

Create SEObot collection pages

7. Design the Details and Index pages.

SEObot page layers

8. On the Details page, select the Content field layer and ensure that all required styles are applied: Paragraph, Headings, Link, Blockquote, Code, Spacing, Code Block, YouTube, Image, and Table.

9. To support table rendering, select Table in the CMS Styles section as shown in the screenshot above.

10. Complete your page design, set up page routes, and publish changes.

Can I use the /blog/ route?

If you already have a blog collection that operates under the /blog/ route, you should choose a different option for SEObot blogs.

This route limitation is imposed by Framer, which does not allow plugins to manage third-party CMS collections—only its own collections. Additionally, you cannot use two CMS collections on the same route. However, you can create a separate route, such as /insights/ or /resources/. This is standard practice and helps organize different types of content more effectively.

Common examples:

  • /blog/ (main blog)

  • /insights/ (thought leadership)

  • /news/ (company updates)

  • /resources/ (guides, tutorials)

  • /case-studies/

  • etc.

Did this answer your question?