How I Audit a Framer Site Handed Over by a Designer

TL;DR: Framer's SEO posture changed materially in 2024-2025. Server-rendered HTML by default, CMS collections with real routing, per-page metadata controls, structured-data fields, CDN-native images, and an in-product redirect manager all shipped in that window. Most of the older Framer SEO advice you'll read is now obsolete, and the 2026 audit at designer handoff is shorter than the public web makes it sound. The seven checks I actually run, ordered by what breaks rankings fastest, are rendering verification, per-page metadata, the collection-route map, the internal-link graph, image alt text, structured-data fields, and the redirect map if this is a migration. Five of those are mostly Framer's default behavior now; two still need real operator work.

The handoff sits on my desk every other month

A designer finishes a Framer build, the visuals are good, the founder is happy, and the site is about to launch (or has been live a few weeks with nothing happening in Search Console). The question they bring me is the same every time: "is this ready to rank?" I used to walk a 2022-era checklist with twelve items on it. After three Framer audits in the last quarter, half that list is now Framer handling things for me by default, and I've trimmed the audit to seven checks I actually run.

The piece below is that audit. I'll start with the render-path map, because the historical concern about Framer (the JavaScript-rendering one) is the part operators still ask me about and it's the part most cleanly closed in 2024. Then the seven checks in priority order, then the migration-source matrix for the rebuild scenario, and a short honest section on what Framer's CMS still doesn't do well in 2026. This is platform-specific. The Wix and Webflow versions of this article cover their own ground, and I'll cross-link to the Webflow one in the spot where it's the better next read.

What Framer actually does between publish and crawl

The render path is five stages. A browser (or crawler) requests a URL. Framer's edge resolves the URL to a page or a collection record. Framer's server renders the HTML, full body text, headings, structured data, the lot, and ships it in the initial response. The CDN caches and serves it. The crawler reads it and indexes the same HTML a human would see. Each stage has one thing the operator should verify, and only one of them (the last) is non-obvious.

The historical concern about Framer (and every other design-tool-turned-website-builder) was that it shipped client-rendered JavaScript and Google saw an empty shell. Google's public position has been consistent for years: server-rendered or pre-rendered HTML and client-rendered output are different delivery shapes, not different ranking classes, and the indexing pipeline doesn't reward one over the other — it just needs the content present when the page is fetched. Framer's 2024 default puts the content in the initial response, which closes the historical concern.

The verification on every handoff is a one-line check: curl -A "Googlebot" <url> against three sample pages (home, a collection detail page, a deep page), and grep the response body for a phrase only visible client-side. If it's there, the page is shipping rendered HTML in the initial response and you're done. If not, you found the one page where the SSR default got overridden, usually by a heavy client-side animation widget. The SPA SEO context piece covers what to do in that edge case.

What changed in 2024-2025 that you can stop auditing for

Five things Framer now handles by default that you used to need to fix by hand. If your audit checklist still has these items on it, you can shorten the checklist.

First, server-side rendering. Pages ship full HTML in the initial response (the section above covers the verification). Second, CDN-native image delivery: WebP and responsive srcset are automatic on assets uploaded after the 2023 CDN rollout. The old "compress your images" SEO advice still matters for image alt text and filename hygiene but not for format negotiation. Third, per-page <head> controls: title, meta description, canonical URL, OG image, robots tag, all settable per page in the publish UI without theme-level edits. Fourth, native structured-data fields: Article, Product, FAQPage, BreadcrumbList schema fields ship in the per-page panel without code injection. Fifth, a native redirect manager that handles 301s on the same domain.

The implication: most older Framer SEO content describes a 2022 product that doesn't exist anymore. The operator-side audit in 2026 is about verifying defaults held and finishing the per-page work Framer doesn't do for you. That's a shorter audit than most platform-comparison roundups suggest. The honest caveat is that defaults are good, not perfect, and three things still need real operator work in the next section.

The seven-check handoff audit

Take-away artifact. Seven checks ordered by what breaks rankings fastest if mis-set. I run them in this order because earlier failures cost more rank than later ones, and finding a stage-one failure changes how I treat the rest of the audit.

#	Check	Failure mode at handoff	Status in 2026
1	Rendering verification	One page configured to render client-side (animation widgets)	Mostly default; verify 3 sample pages
2	Per-page metadata	Every page sharing the site-level title prefix	Operator work
3	Collection-route map	Flat URL prefix, near-duplicate pagination pages	Operator work
4	Internal-link graph	Visual nav rich, body links thin	Operator work
5	Image alt text	Alt reads "image-1.jpg" on hero images	Operator work (CDN handled)
6	Structured-data fields	Schema panel populated for one page, empty for the rest	Operator work (field shipped)
7	Redirect map (migration only)	Old URLs return 404, equity gone	Operator work; tool shipped

The next sections walk the three checks I see fail most on real Framer handoffs (checks 2, 3, and 4). Checks 5, 6, and 7 are covered together in a single section because they share a pattern: the platform ships the surface, the operator populates the field.

Check one, per-page metadata wiring

This is the check that breaks rankings fastest in Framer because the platform inherits title and description from site-level settings. Designer-built sites often launch with every page sharing the same title-template prefix, and the per-page overrides are left empty. Looking at five sample page titles tells you within thirty seconds whether this happened.

Four fields to verify per page. Title: unique, under 60 characters, leads with the page-specific phrase rather than the site name. Meta description: unique, 140-155 characters, written for click-through not for the keyword. Canonical URL: not pointing at the staging domain (the most common failure I see, since the designer was working in a preview environment and the canonical never got updated for production). OG image: page-specific, not the site-wide default that shows up on every share.

The fix is a single editorial pass and takes about an hour for a 20-page site. The OG image piece is the follow-on if share imagery matters for the site's audience. Make a list of the top ten pages by intended traffic, write the four fields for each, paste into the Framer publish panel, ship.

Check two, the collection-route map

Framer's CMS uses collections with dynamic routing. Blog posts, case studies, products, team members are records in a collection, each rendering at <collection-prefix>/<slug>/. The handoff audit checks three things on every collection.

The collection prefix should be hierarchical, not flat. A blog post should live at /blog/post-name/, not at /post-name/. Flat prefixes break crawl-budget signals because the crawler can't tell which URLs are leaves and which are listings, and the URL itself loses the topical category hint that helps Search Console attribution. The crawl-budget piece covers the underlying mechanic.

Pagination on collection listings shouldn't generate near-duplicate pages. Framer's default is page-2, page-3 URLs that share the listing's title and meta, which Google will pick one of and ignore the rest. If pagination matters for the site (a content-heavy blog past 50 posts), set up canonical from page-2 onwards to the page-1 listing, or use an infinite-scroll pattern that doesn't generate paginated URLs at all.

Collection-level canonical is the third check. On a collection detail page, the canonical should be the detail page's own URL, not the listing's. I've seen this misconfigured exactly twice in the last year, and both times the symptom was "all my blog posts have zero impressions", because Google was canonicalizing every detail page back to the listing. The fix is one toggle in the collection settings. The content-silos piece covers the broader hierarchy decision.

Check three, the internal-link graph

Designer-built sites tend to have visually-rich nav but thin body-link structure. The header has six items, the footer has a sitemap-style block, but the body prose rarely links to other pages on the same site. That's a problem because internal links inside body content carry more weight than nav links, both for rank-signal distribution and for crawl-priority hints.

The check is mechanical. List the top ten commercial-intent pages on the site (the service pages, the product pages, the case studies that should rank). For each, count in-links from non-nav locations: body prose on other pages, related-articles modules, contextual cards. The minimum I'd ship at handoff is three body-prose in-links per top-ten page. Two is workable for a small site under twenty pages; one or zero is the failure case I most often see on Framer handoffs.

The fix is an editorial pass through the existing content: reading the article-style pages, case studies, and landing pages, then inserting two or three contextual links into the top-ten list. It takes about half a day for a 30-page site. The internal-link statistics piece covers why this matters more than nav-link distribution.

If you came out of this section clean, the cross-platform hygiene-audit reference is the next read; it covers the items that aren't Framer-specific.

The other four checks that still need operator work

Image alt text, structured-data fields, redirect map, and the rendering sample verification I described earlier. These share a pattern: the platform ships the surface, the operator populates the field. Bundling them here because the work shape is similar.

Image alt: Framer's CDN handles format and responsive sizing, but the alt attribute is set per asset in the asset library. The audit check is to spot-inspect ten images used above the fold on key pages and confirm the alt text is descriptive (not "image-1.jpg" or "Untitled-design.png"). Hero images and OG-shared images are the ones I check first because they're the most visible.

Structured-data fields: Framer's schema panel ships Article, Product, FAQPage, and BreadcrumbList. The check is per-page: every blog post should have Article schema populated, every product page should have Product, every page with a FAQ block should have FAQPage. The failure mode I see most is the schema getting populated for the first three pages a designer set up, then left empty for the rest of the collection.

Sample-page rendering verification was covered in the render-path section. Three sample pages, curl -A "Googlebot", grep for a phrase that's only visible after JavaScript runs. If the phrase appears in the curl response, the page is SSR-rendered; you're done.

Redirect map only matters if this is a migration into Framer. If it is, the next section is for you.

Migrating into Framer — the source matrix

Four realistic source scenarios with different risk profiles. The most common one I see is Webflow → Framer (a founder who started with Webflow, switched designers, and got a Framer rebuild). The riskiest one is WordPress → Framer because the redirect surface is larger and plugin-managed metadata gets lost in the move.

Source platform	Key risk	Recommended approach
Figma (no live site)	None — nothing to preserve	Fresh launch. Plan URL structure cleanly from the start; submit sitemap to GSC on day 1
Webflow	Equity loss without 301s; temporary rank dip during recrawl	Build redirect map at parity (one old URL per new URL), launch, monitor rank for 60 days
WordPress	Plugin-managed metadata loss; larger redirect surface; potential image-URL changes	Inventory all metadata via SEO plugin export, build redirect map, expect 30-90 day reranking window
Fresh launch (no prior site)	Slow indexing only	Submit sitemap to GSC + Bing on day 1, expect 14-30 day initial rank ramp

Walking the Webflow case in depth because it's the most common. Build the redirect map at parity, meaning every old URL maps to exactly one new URL (no many-to-one collapses, no one-to-many splits). Launch on a Tuesday or Wednesday so the first crawl wave hits inside a business week. Expect a 10-20% temporary impressions dip in weeks 2-4 while Google re-crawls the redirect map and re-attributes signals — that dip is normal and recovers if the redirect map is clean. The headless CMS migration piece covers the adjacent cost framing.

WordPress migrations are harder because plugin-managed metadata (Yoast, RankMath, AIOSEO) needs to be exported before the rebuild starts. The redirect surface is typically two to three times larger than a Webflow migration because WordPress sites accumulate URLs over years. The WordPress migration piece covers the inventory step.

What Framer's CMS still doesn't do well

Honest 2026 posture. Framer's CMS is a real CMS, but two things still trail Webflow's, and if either is core to the project the platform choice might be worth revisiting.

One: faceted-search-style filter combinations on large product or content collections. If your site has a catalog page with multiple filter dimensions (category, price, color, brand) generating combinatorial URLs, Framer's filter handling generates URLs that aren't always cleanly canonicalized. The workaround is to noindex the filter combinations and keep the canonical base URL for the unfiltered listing. This works for sites under a few hundred SKUs; past that, the canonicalization story matters and Webflow handles it better.

Two: nested-collection patterns. If you have a content hierarchy three levels deep (category → subcategory → article), Framer's URL routing can flatten unexpectedly under certain configurations, and the URL field per record needs to be set manually to enforce the hierarchy. Webflow's collection nesting is more predictable. For a two-level hierarchy (blog → post, products → product) Framer is fine.

If either is a blocker, the sibling Webflow audit piece covers the same territory on a platform that handles it better. For the other 80% of sites, Framer's CMS in 2026 is competitive.

What the audit produces

The artifact is a one-page handoff report. Render-path verified on three sample pages. Per-page metadata complete across the top-ten pages. Collection routes mapped, pagination handled, canonicals correct. Internal-link graph audited with the top-ten landing pages receiving three body-prose in-links each. Images alt-tagged where they matter. Structured-data fields populated. Redirect map built if this is a migration. The designer keeps the project; the operator now has a baseline.

Two next reads. The cross-platform hygiene audit is the right reference for the items that aren't Framer-specific. The founder-tools piece is the next read for the smaller-portfolio audience auditing their own Framer site without an operator alongside them.

FAQ

Is Framer's SEO actually competitive with Webflow in 2026? Close, not identical. Framer caught up materially in 2024-2025 with SSR by default, CMS collections, per-page <head> controls, and structured-data fields. Webflow still has the edge on nested collections and complex filter-URL handling. For 80% of sites I see, the gap is closed.

Do I still need to worry about JavaScript rendering on Framer pages? Not for default-built Framer pages. Framer ships server-rendered HTML by default since 2024. The exception is highly animated detail pages with heavy client-side state. Verify with curl -A "Googlebot" against three sample pages to be sure.

How long after launching a Framer site does it take to start ranking? Same range as any new site: 14-30 days for first Search Console pickup, 60-90 days for query-level ranking signal. Migrating from a ranked site, expect a 10-20% temporary impressions dip in weeks 2-4 while Google re-crawls the redirect map.

Can I host a Framer site on my own domain and CDN? Custom domain yes, custom CDN no. Framer's CDN is part of the platform. This is the same posture as Webflow and Wix.

What's the one Framer-specific SEO mistake I see most often at handoff? Every page sharing the same title-template prefix. Designers set the site-level title pattern and leave the per-page overrides empty, so every page reads "Site Name | Page Title". Easy to fix in an hour; visible in any sample of five page titles.

<script type="application/ld+json"> {"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Is Framer's SEO actually competitive with Webflow in 2026?","acceptedAnswer":{"@type":"Answer","text":"Close, not identical. Framer caught up materially in 2024-2025 with SSR by default, CMS collections, per-page head controls, and structured-data fields. Webflow still has the edge on nested collections and complex filter-URL handling. For 80% of sites, the gap is closed."}},{"@type":"Question","name":"Do I still need to worry about JavaScript rendering on Framer pages?","acceptedAnswer":{"@type":"Answer","text":"Not for default-built Framer pages. Framer ships server-rendered HTML by default since 2024. The exception is highly animated detail pages with heavy client-side state. Verify with curl against three sample pages to be sure."}},{"@type":"Question","name":"How long after launching a Framer site does it take to start ranking?","acceptedAnswer":{"@type":"Answer","text":"Same range as any new site: 14-30 days for first Search Console pickup, 60-90 days for query-level ranking signal. Migrating from a ranked site, expect a 10-20% temporary impressions dip in weeks 2-4 while Google re-crawls the redirect map."}},{"@type":"Question","name":"Can I host a Framer site on my own domain and CDN?","acceptedAnswer":{"@type":"Answer","text":"Custom domain yes, custom CDN no. Framer's CDN is part of the platform. This is the same posture as Webflow and Wix."}},{"@type":"Question","name":"What's the one Framer-specific SEO mistake you see most often at handoff?","acceptedAnswer":{"@type":"Answer","text":"Every page sharing the same title-template prefix. Designers set the site-level title pattern and leave the per-page overrides empty, so every page reads 'Site Name | Page Title' with the same prefix. Easy to fix in an hour."}}]} </script>