The short answer
- Framer generates sitemap.xml and robots.txt automatically, sets canonical tags from your connected domain, and lets you set titles, descriptions and Open Graph images per page.
- CMS pages use variables like {{Title}} in their SEO fields, so each item gets unique metadata.
- Structured data is added as JSON-LD through custom code, with CMS fields inserted using the {{Field | json}} syntax.
- Know the limits: site redirects are on the Pro plan, not Basic; canonical overrides are site-level only; Basic allows 30 pages and 2 CMS collections.
- Changing a page path does not update your redirects automatically. Add the redirect yourself every time.
Framer SEO works well out of the box for the technical basics. Where Framer sites fall short is plan limits that get hit as a content program grows, and slug changes made without redirects.
Everything below is checked against Framer's own help center, SEO page and pricing page in October 2026.
What Framer handles for you
Framer lists these SEO features as built in:
- Sitemap and robots.txt, auto-generated. The sitemap lives at yourdomain.com/sitemap.xml.
- Canonical tags, generated in the page head from your connected domain.
- Dynamic metadata using variables such as {{Title}} and {{Description}}.
- Open Graph images for share previews.
- Redirects to keep rankings when URLs change.
- Structured data through JSON-LD.
- Root-level and /.well-known/ files, which Framer says support standards like robots.txt, security.txt and llms.txt.
- Indexing controls to choose which pages appear in search.
- Semantic HTML tags such as header, nav and article.
- Image optimization, serving WebP through a global CDN.
- Locale redirects that send visitors to their preferred language based on browser settings.
Framer also offers an AI agent that scans a page, prioritizes SEO fixes and applies approved updates to metadata, headings, alt text and internal links. Treat its output like any draft and read it before publishing.
The /.well-known/ and root file support matters for AI search. An llms.txt file gives AI assistants a plain summary of what your site covers, and a robots.txt you control decides which AI crawlers can read it. The AEO grader checks how ready a page is to be quoted in AI answers.
Page SEO settings
Each page has an SEO section in its page settings for the title, description and social image. Practical targets:
- Title around 50 to 60 characters, primary keyword near the front.
- Description around 140 to 160 characters that states what the page answers.
- One H1 per page. In a visual editor it is easy to style several text layers as headings; check the tag, not the font size.
- A short, readable path. Set it once and leave it.
Use the indexing controls to keep thin pages out of search: thank-you pages, password-protected drafts, old campaign landers with no traffic.
Worked example
A pricing page for a design tool. Title: "Pricing - Plans for Solo Designers and Teams". Description: "Three plans from solo to team, billed monthly or yearly, with a feature comparison and answers to common billing questions." Path: /pricing. One H1 that says "Pricing", and FAQ content in the visible page that can later carry FAQPage markup.
CMS collections
Blogs, changelogs, case studies and directories run on Framer's CMS. Each collection has a detail page template, and that template's SEO settings apply to every item.
Unique metadata per item
Use variables in the template's title and description fields: {{Title}} for the title and an SEO description field for the description. Add a dedicated SEO description field to the collection rather than reusing an intro paragraph, which is usually too long or too short.
Plan limits that matter for SEO
| Limit | Basic ($10/mo, billed yearly) | Pro ($30/mo, billed yearly) |
|---|---|---|
| Site pages | 30 | 150, then $20 per 100 (700 max) |
| CMS collections | 2 | 10, then $40 per 10 (40 max) |
| CMS items | 1,000 | 2,500, then $20 per 10,000 (40,000 max) |
| Bandwidth | 50 GB | 100 GB, then $40 per 100 GB (2 TB max) |
| Site redirects | Not included | Included |
| Staging environment | Not included | Included |
Prices and limits from framer.com in October 2026. The Free plan runs on a Framer domain only; a custom domain needs a paid plan. Enterprise has custom limits.
The redirect row is the one to weigh. A site that will ever rename pages, migrate from another platform or restructure its blog needs redirects, which means Pro.
Redirects
Redirects are set under Site Settings, Hosting, Redirects. Framer supports three matching methods:
- * matches any path segment: /blog/* captures /blog/hello-world.
- Capture groups (:1, :2) reuse what each * matched: /blog/*/post/* to /article/:1/entry/:2.
- Named segments such as /blog/:year/:month/:day match specific parts between slashes.
Framer's help center is explicit on one point: if you change a sub-path from the canvas or the CMS, it will not update automatically in your redirect settings. Every slug change needs a manual redirect from the old path.
Worked example: migrating a WordPress blog
A WordPress blog with dated URLs (/2024/05/pricing-guide/) moving to Framer's /blog/pricing-guide can be covered by one rule using named segments: old path /:year/:month/:slug, new path /blog/:slug. That rule matches any three-segment path, so make sure no live Framer page uses that shape, then spot-check ten old URLs from Search Console after publishing.
Framer redirects work only for sub-paths on your current domain. Redirecting a whole old domain to a new one is done at the domain or DNS provider first.
Canonical URLs
Framer generates canonical tags automatically from your connected domain, and for most sites that needs no attention.
The custom canonical setting is under Settings, Domains, in the Canonical URL field, and it is site-level only. Framer's help center describes it for one case: the site is served through a reverse proxy, for example a Framer blog at example.com/blog, and the domain is not directly connected. There, set the canonical to the full public path so tags do not default to the wrong host.
There is no per-page canonical override in that documentation. If you need one page to canonicalize to another, consolidate the content or redirect instead.
Structured data with JSON-LD
Add JSON-LD through Framer's custom code feature, in the head of the page. On CMS detail pages, reference fields with double braces so each item gets its own markup:
- {{Title | json}} for the headline, with the json filter keeping quotes and special characters safe.
- {{Excerpt | json}} for the description.
- {{Cover_Image | json}} for the image.
- {{Author_Name | json}} for the author.
Framer also documents storing full JSON-LD in a plain text CMS field and outputting it with {{field | unsafeRaw}}. Generating it from fields is the safer route, because one typo in a stored block breaks that page's markup silently.
Validate a few item pages with Google's Rich Results Test after publishing.
Performance
Framer serves images as WebP through a global CDN, and paid plans differ in how many CDN locations host the site. What slows a Framer site down is usually design choices:
- Large background videos and heavy scroll animations above the fold on mobile.
- Many custom fonts and weights.
- Embedded third-party widgets and scripts in custom code.
- Very long pages built from dozens of stacked components.
Use the Core Web Vitals report in Search Console for field data, and test the mobile version of your heaviest template first.
Content: the part Framer cannot configure
Framer sites are often launched as polished marketing sites with a handful of pages. That design carries brand searches. Non-brand traffic comes from a blog or resource library published against real keyword demand.
Sprites' AI SEO agent handles that work for Framer sites: keyword research with search volume checked against real search behavior, competitor keyword gaps, page and site audits, and SEO blog posts written or updated. It proposes each post on an editable approval card and publishes it to Framer once you approve. It reads Google Search Console and Google Analytics 4 to pick refresh candidates.
See the SEO optimization use case for the workflow, the Webflow SEO guide if you are choosing between the two builders, and pricing for what each plan includes. Every plan starts with a 7-day trial for $1.
If you are on Basic and plan to rename or migrate anything, move to Pro before you change the first URL.