言語

暫定日本語訳：Framer SEO

暫定日本語訳：How SEO works on Framer — the design-first builder that pre-renders static HTML at publish, so Googlebot gets complete ページ without running JavaScript. Per-ページ metadata, automatic sitemaps and robots.txt, canonical tags, redirects, custom head code, and the real limitations (no スキーマ UI, plan-gated robots.txt, non-editable hreflang).

初回公開：2026年6月27日 · 最終更新：2026年8月4日 · Advanced
言語
AI執筆者：AI v2

暫定日本語訳：Framer pre-renders static HTML at publish, so Googlebot gets complete ページ without executing JavaScript — that's the most important SEO fact about the platform and the thing that separates it from client-rendered builders. Out of the box you get automatic sitemaps, a default robots.txt, self-referencing canonicals, automatic HTTPS, and per-ページ metadata (including on CMS items). The gaps are about depth and scale: no スキーマ markup UI (JSON-LD goes in via custom <head> code), no alt-text binding from CMS fields, custom robots.txt needs a Pro plan or higher, and hreflang is generated automatically but not editable. The redirect manager (also Pro+) now supports wildcard folder redirects and capture groups, not just one-to-one mapping — it just can't redirect across domains. Framer vs Webflow is broadly comparable at the technical level — the difference is CMS maturity and workflow, not crawlability.

暫定日本語案: TL;DR — Framer pre-renders static HTML at publish, so Googlebot gets complete 暫定日本語案: ページ without running JavaScript — the single most important SEO fact about the 暫定日本語案: platform. You get automatic sitemaps, a default robots.txt, self-referencing 暫定日本語案: canonicals, automatic HTTPS, per-ページ metadata (including on CMS items), a 暫定日本語案: built-in redirect manager, and custom <head> injection for the things the UI 暫定日本語案: doesn’t expose. The real limits are depth and scale: no スキーマ markup UI, no 暫定日本語案: alt-text binding from CMS fields, custom robots.txt and the redirect manager both 暫定日本語案: need Pro+, redirects (though now wildcard-capable) can’t cross domains, and 暫定日本語案: hreflang is auto-generated but not editable. Versus Webflow it’s broadly 暫定日本語案: comparable at the technical level.

Evidence for this claim The article's described framer-seo capabilities must be evaluated against the platform's current documentation rather than assumed to be search-engine behavior. Scope: Platform-specific capability documentation. Confidence: high · Verified: Framer: SEO Evidence for this claim Regardless of platform, Google needs crawlable URLs, accessible rendered content, descriptive metadata, and valid search directives. Scope: Google requirements independent of platform. Confidence: high · Verified: Google Search Central: SEO Starter Guide

暫定日本語案: The fact that matters most: it’s pre-rendered

暫定日本語案: I’ll lead with the thing everything else hangs on. Framer generates static HTML 暫定日本語案: at publish time. ページ are pre-rendered, not client-side rendered, so Googlebot 暫定日本語案: receives complete HTML without executing JavaScript to see the コンテンツ.

暫定日本語案: This is the heart of why “is Framer good for SEO?” has a reassuring answer. The 暫定日本語案: classic failure mode for design-tool-turned-publisher platforms is shipping a 暫定日本語案: client-only React bundle where the meaningful コンテンツ only appears after the 暫定日本語案: browser runs JS — which pushes you into Google’s separate, queued rendering step 暫定日本語案: and all the risk that comes with it. Framer sidesteps that entirely. If you’ve read 暫定日本語案: my take on JavaScript SEO, this is the 暫定日本語案: clean-input scenario you want.

暫定日本語案: One honest caveat: Framer is built on React, and animation-heavy ページ can add 暫定日本語案: interaction cost. The HTML being crawlable is settled; the thing to watch on 暫定日本語案: design-heavy ページ is interactivity metrics, which I’ll come back to under 暫定日本語案: パフォーマンス.

暫定日本語案: What Framer gives you out of the box

  • 暫定日本語案: Automatic sitemap.xml. Generated on every publish at 暫定日本語案: yourdomain.com/sitemap.xml, CMS collection ページ included. Submit it in 暫定日本語案: Google 検索 Console and 暫定日本語案: Bing Webmaster Tools.
  • 暫定日本語案: Automatic robots.txt. Framer’s docs: “Framer automatically generates a 暫定日本語案: robots.txt file for every published サイト.”
  • 暫定日本語案: Self-referencing canonical tags on every ページ, set automatically. Per Framer 暫定日本語案: 商品 Specialist Luca Da Corte: “By default, Framer automatically sets a 暫定日本語案: self-referencing canonical tag for each ページ on your ウェブサイト.”
  • 暫定日本語案: Automatic HTTPS on all Framer-hosted sites.
  • 暫定日本語案: CDN + image optimization — automatic conversion to modern formats, served 暫定日本語案: from a global CDN.

暫定日本語案: Per-ページ and CMS metadata

暫定日本語案: Per-ページ SEO settings — title, meta description, OG image, canonical, and an 暫定日本語案: index/noindex toggle — are available on every ページ, including CMS collection 暫定日本語案: items. On CMS ページ the title and description can be driven by collection fields, 暫定日本語案: so a 200-item blog or 商品 collection can populate unique metadata from the 暫定日本語案: データ rather than one ページ at a time.

暫定日本語案: That’s genuinely useful. The honest limitation, flagged by reviewers like Hannah 暫定日本語案: Martin, is that CMS ページ titles lean on a default [item name] [separator] [サイト 暫定日本語案: name] pattern, so granular per-item title templating is thinner than what a 暫定日本語案: WordPress SEO plugin gives you.

暫定日本語案: Custom <head> code injection

暫定日本語案: This is the escape hatch for everything the UI doesn’t expose. Framer supports 暫定日本語案: custom <head> code サイト-wide and per-ページ, which is how you add:

  • 暫定日本語案: JSON-LD structured データ (there’s no スキーマ UI — more below),
  • 暫定日本語案: 検索-engine verification tags,
  • 暫定日本語案: hreflang or other tags you want to control by hand,
  • 暫定日本語案: analytics and anything else that belongs in the head.

暫定日本語案: Redirects

暫定日本語案: Framer has a built-in redirect manager (サイト Settings → Redirects) for 暫定日本語案: 301-style redirects, and it’s no longer a one-to-one tool. Framer added wildcard 暫定日本語案: and pattern matching: use * to match an entire folder (/blog/* catches 暫定日本語案: /blog/hello-world and every nested path under it), reference matched segments in 暫定日本語案: the destination with capture groups (:1, :2), or match specific URL segments 暫定日本語案: with named slugs (/blog/:year/:month/:day → /article/:year-:month-:day). 暫定日本語案: That covers the bulk-migration case that used to require adding redirects one by 暫定日本語案: one. The real limitation now is narrower: redirects only work within your 暫定日本語案: current domain — Framer can’t redirect an entire domain to a different domain 暫定日本語案: (www.old.com → www.new.com); that has to happen at the DNS/hosting level for 暫定日本語案: the old domain before you connect the new one in Framer. Framer’s docs: “You can 暫定日本語案: only redirect sub-paths within your current domain. To redirect an entire domain… 暫定日本語案: use your hosting provider for the old domain to set up domain-level redirects.” 暫定日本語案: One plan note: the redirect manager itself requires a Pro plan or higher — it’s 暫定日本語案: not available on Free or Basic.

暫定日本語案: Canonical tags in detail

暫定日本語案: The default behavior is already SEO-safe: self-referencing canonical on every ページ. 暫定日本語案: When you need a custom canonical (pointing somewhere other than the ページ itself), 暫定日本語案: you add a <link rel="canonical"> via the ページ’s <head> code. Da Corte notes 暫定日本語案: Framer is smart about this: “When Framer detects a custom canonical tag in the 暫定日本語案: <head> tag of the ページ, it will avoid adding the default self-referencing one, so 暫定日本語案: it won’t cause any confusion to 検索 engines.” So you won’t end up with two 暫定日本語案: competing canonicals. The broader topic — 暫定日本語案: canonicalization — is 暫定日本語案: its own thing; the point here is Framer’s default is good and the override is clean.

暫定日本語案: “Dynamic Optimization”: a Framer-specific term

暫定日本語案: You’ll see Framer talk about Dynamic Optimization (also described as 暫定日本語案: traffic-aware pre-rendering). This is not a standard SEO term — it’s a 暫定日本語案: Framer-specific feature, so let me explain it plainly. Framer’s blog: “we optimize 暫定日本語案: each ページ the first time a user visits it. After that, the optimized version is 暫定日本語案: stored in a cache until you publish a new version.” High-traffic ページ get the 暫定日本語案: optimized, cached version served to nearly everyone.

暫定日本語案: Why does this matter for SEO? Because Google’s 暫定日本語案: Core Web Vitals ranking signal 暫定日本語案: uses field データ from real Chrome users (CrUX), not a lab score. Framer’s own 暫定日本語案: framing: “Aggregated パフォーマンス scores like CrUX are not affected, since the 暫定日本語案: overwhelming majority of the visitors will get the optimized ページ.” The practical 暫定日本語案: upshot: don’t panic over a mediocre PageSpeed Insights lab number — Framer’s own 暫定日本語案: help article on the topic 暫定日本語案: calls PageSpeed Insights “an imprecise tool that doesn’t impact SEO.” What Google 暫定日本語案: actually ranks on is the real-user データ, which Framer’s caching protects.

暫定日本語案: Structured データ: no UI, use custom code

暫定日本語案: A genuine gap: Framer has no スキーマ markup UI. Structured データ must be added as 暫定日本語案: JSON-LD via custom <head> code. Arthur Lauwers of 6th Man Digital puts it 暫定日本語案: exactly right: “Structured データ must be added via custom code components by pasting 暫定日本語案: JSON-LD, since there is no native UI for スキーマ.” So Article, FAQ, BreadcrumbList, 暫定日本語案: and Organization markup are all doable — you just paste the JSON-LD yourself rather 暫定日本語案: than filling in fields. Google’s own guidance is “use JSON-LD where possible,” so 暫定日本語案: the format Framer pushes you toward is the recommended one.

暫定日本語案: Framer’s help center now documents this pattern directly for CMS ページ: reference a 暫定日本語案: collection field with {{FieldName}} inside the JSON-LD you paste into a CMS 暫定日本語案: template’s custom code, and use {{FieldName | json}} when the value needs safe 暫定日本語案: JSON escaping (titles, descriptions, dates pulled from the CMS item). That’s how 暫定日本語案: you generate unique BlogPosting or Product markup per CMS item without a native 暫定日本語案: スキーマ field — it’s still custom code, not a UI, but it is an officially documented 暫定日本語案: way to templatize it across a whole collection rather than hand-writing JSON-LD on 暫定日本語案: every item.

暫定日本語案: Localization and hreflang

暫定日本語案: Framer supports localization natively, and when you enable it Framer generates 暫定日本語案: the hreflang tags automatically. The catch, straight from Framer’s docs: “Both 暫定日本語案: the lang and hreflang tags are managed automatically in the backend and are not 暫定日本語案: editable via the UI.” So you can’t hand-tune them, and third-party translation 暫定日本語案: services can’t modify them either. For most localized sites the auto-generated 暫定日本語案: output is fine — but verify it matches your expectations rather than assuming. The 暫定日本語案: underlying spec (hreflang annotations for each localized URL, including 暫定日本語案: x-default) is documented by 暫定日本語案: Google.

暫定日本語案: Known limitations, collected

  • 暫定日本語案: No スキーマ markup UI — JSON-LD via custom <head> code only.
  • 暫定日本語案: No alt-text binding from CMS fields — alt text on CMS images is set manually 暫定日本語案: (or via workarounds), not mapped from a collection field.
  • 暫定日本語案: Custom robots.txt is plan-gated — editing it requires a Pro plan or 暫定日本語案: higher; it’s not available on the free tier. Framer’s docs list custom 暫定日本語案: robots.txt as “available on Pro, Scale, and Enterprise plans.”
  • 暫定日本語案: Redirects only work within your current domain — Framer’s redirect manager 暫定日本語案: now supports wildcards, capture groups, and slug matching for bulk folder 暫定日本語案: redirects, but it can’t redirect an entire domain to a different domain (that 暫定日本語案: needs DNS-level redirects on the old domain). The redirect manager itself needs 暫定日本語案: a Pro plan or higher.
  • 暫定日本語案: hreflang not editable — auto-generated, not hand-tunable.
  • 暫定日本語案: CMS scale limits — per-collection item ceilings make large programmatic SEO 暫定日本語案: builds (500+ ページ) awkward, and there’s no first-class bulk CSV import.
  • 暫定日本語案: No IndexNow — Framer doesn’t natively ping Bing/others on publish; submit 暫定日本語案: your sitemap to Bing Webmaster Tools manually.

暫定日本語案: Framer vs Webflow vs WordPress

暫定日本語案: Framer vs Webflow: both generate static HTML and both offer robots.txt and 暫定日本語案: redirect control. Webflow has a more mature CMS and a wider agency ecosystem; 暫定日本語案: Framer has a stronger design-tool workflow. At the technical SEO level the two are 暫定日本語案: broadly comparable — the differences are in CMS depth and workflow, not in whether 暫定日本語案: the HTML is crawlable. As Matija Golubovic of Omnius frames the scale question: 暫定日本語案: “Both platforms cover the basics, but Webflow clearly is ahead in flexibility, 暫定日本語案: especially for large コンテンツ inventories, migrations, or international SEO.” That 暫定日本語案: mostly still tracks — Framer’s CMS ceilings and non-editable hreflang are real 暫定日本語案: gaps versus Webflow — though Framer’s redirect manager has closed some of the 暫定日本語案: migration gap since that comparison was written: it now supports wildcard folder 暫定日本語案: redirects and capture groups, not just one-to-one mapping.

暫定日本語案: Framer vs WordPress: WordPress wins on the コンテンツ side — the plugin ecosystem 暫定日本語案: (Yoast, Rank Math), multi-author roles, scheduled publishing, and an editorial 暫定日本語案: workflow Framer doesn’t match. Framer wins on the publishing-floor side: SSR, CDN, 暫定日本語案: HTTPS, and image optimization are on by default with no plugins and no hosting to 暫定日本語案: manage. For a small-to-medium marketing サイト Framer’s technical defaults are 暫定日本語案: excellent; for a large コンテンツ operation, WordPress’s tooling pulls ahead.

暫定日本語案: Bottom line

暫定日本語案: Framer is technically sound for SEO because it pre-renders crawlable HTML and ships 暫定日本語案: the right defaults. The limitations are about depth and scale — スキーマ UI, CMS 暫定日本語案: ceilings, editable hreflang, cross-domain redirects — not about whether Google can 暫定日本語案: read your ページ. For most marketing sites that trade-off is easy to live with.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.