The SEO tool Framer did not have.
RankFrame is a full SEO product built inside the Framer editor. I scoped it into eight tools, specified it for a developer, and priced and released it as a subscription business.
Role
Product lead. Scope, spec and release
Timeline
Launched May 2026
Team
One developer, briefed and run by me
Live
rankframe.com ↗
01
The problem
Framer is where a lot of small teams now build their sites, and it shipped without the SEO layer every other platform has. There was no way to manage meta tags at scale, no structured data, no way to push a sitemap to Google, no alt text tooling, and nothing that told you whether a page was any good. People were leaving Framer, doing the work in a dashboard somewhere else, and coming back.
The gap was obvious. The hard part was that an SEO tool isn't one feature. It's eight, and each one is a product on its own, so shipping four of them badly would have been worse than shipping none.
02
What I did
I built it inside the editor rather than as one more dashboard
The obvious shape was a web app you log into. I put the whole thing in a side panel in Framer, so the audit, the fix and the publish all happen without leaving the file. A dashboard still exists, but it only holds billing, sites and credits. Nothing you do while designing needs it.
I priced per site, then broke my own rule for agencies
Personal is 15 dollars a month for one website. Agency is 40 for unlimited customer sites. The second tier exists because the people who install a Framer plugin most often are studios running twenty customer sites at once, and charging them per site would have priced out the exact customer who would use it every day.
I treated the crawl cost as a design problem
Site crawling is the expensive part of this product, and on a large site it ran often enough to cost real money against a fifteen dollar subscription. That isn't an engineering surprise, it's a scoping decision that was made too loosely, so it went back into a written brief and came out as a costed fix rather than a bigger bill.
I redrew the whole interface for Framer 3.0
When Framer changed underneath us the choice was to patch or to start again. I started again, with a new interface, much faster crawling, and every page getting its own analyser, so you audit and fix page by page instead of being handed one site wide score you can't act on.
An SEO tool is not one feature. It is eight, and four of them done badly is worse than none.
03
How I ran it
There were two of us, so the process had to be light and still survive a gap of weeks. Every round of fixes went to the developer as a dated brief rather than a message, rendered to PDF so it could be reread later.
The Framer review rounds, the backend security pass, the crawl cost fix and the team feature review each have one. That's why a two person product could take review notes from a platform team and turn them round without losing track of what was actually said.
The releases were scheduled rather than opportunistic. Eight tools didn't arrive at once, they arrived in an order I decided, so each one could be supported before the next one shipped.
04
The journey
The whole product is one decision about where it lives. Every other SEO tool asks a designer to leave the canvas, so RankFrame docks beside it. Design on the left, optimise on the right, and the eyes never travel.
Getting in takes five steps, and after that the product does the work for you. It detects the published Framer site rather than asking anyone to paste a URL, finds the sitemap and the languages, asks what the brand is, what the site is being optimised for, who the audience is and who the competitors are, then shows the whole setup back before it commits. Then it crawls, so every screen after that arrives filled in rather than blank.
From there each system is a job rather than a menu. The analyser returns one score out of a hundred with the sixteen checks that produced it, sorted into passed, warned and failed. Image SEO finds what's missing alt text and writes the replacement back into the CMS field. Schema, indexing submission, the 404 monitor, keyword tracking and page speed each sit one level down, grouped by the job they do rather than by the API they call.
The biggest thing I added after launch came out of one conversation. An agency told us what they valued was having everything in one place, then named the thing that was missing, which was user management so a team could work inside the same account. I wrote that one up and specified it, because the feature came from a sentence somebody said rather than from a roadmap I drew on my own.
05
What shipped
It shipped as a live plugin on the Framer Marketplace and a dashboard at rankframe.com, carrying meta tags with AI suggestions, keyword research with volume and difficulty, JSON-LD structured data, Google Search Console with instant indexing and position tracking, an audit scored zero to one hundred with Core Web Vitals and a downloadable report, bulk AI alt text across canvas, CMS and components, a 404 monitor, and locale support across all of it.
06
Impact
Designers who have installed and run it
250+
In sales across two paid tiers
$1,500+
Active users on the plugin today
20+
Tools in one panel, each a product on its own
8
07
The work
The product as it is sold, then the product as it is used: sign in, connect, onboard, crawl, and then the eight tools, from the analyser and image SEO to keywords, schema, the 404 monitor and indexing.
08
Go deeper
Design system and Figma
I built the design system in Figma, with eleven component variant sets and fourteen standalone components across eighteen plugin screens, and everything is bound to variables rather than typed in, so a colour or a spacing change lands everywhere at once. It runs light and dark throughout, and nothing is called done until it has been looked at in both, after a badge once shipped with purple text on a purple fill.
Build and handover
It's a Framer plugin and a web dashboard that stay in sync on one Google sign in, with billing through Polar and a knowledge base of eighty three articles across fifteen modules, so support is usually a link rather than a conversation.
More
All work
→
