---
title: "Framer: design, SEO & AI discoverability"
description: "How I work on Framer, where I run production client work: schema injection validated against the rendered page, staged review before whole-site publishes, and the full machine-readable layer."
source: https://sukisong.com/platforms/framer/
updated: 2026-09-10
---
# Framer: design, SEO & AI discoverability

Framer ships beautiful sites fast, and I run production client work on it. Its trade-offs are specific, and knowing them is most of the job: schema goes in through code injection, publishing is site-wide, and what a validator accepts is not always what a browser renders. My Framer process exists because of those three facts.

## How I work on Framer

- **Build in Framer.** Design and build in your workspace, with the machine layer wired in through Framer’s custom-code surfaces from the start.
- **Layer onto your existing Framer site.** Structured data, crawler policy, and metadata added without touching your design.
- **Steward what a designer built.** A designer made you something beautiful in Framer; I make it findable and keep publishes safe.

## The machine layer on Framer

- **Injected JSON-LD is verified against the rendered page.** Schema added via script injection can pass a paste-in validator while never actually rendering for crawlers, so I validate the live output rather than the input. This is the single most common Framer schema mistake.
- **Publishes are site-wide**, so every change goes through staged review before it ships. Nobody’s half-finished draft ever rides along with a fix.
- **Sitemaps are automatic.** Metadata and social cards are set per page, deliberately.
- **llms.txt needs a workaround.** Like most hosted builders, Framer doesn’t serve arbitrary root text files, so a lightweight proxy in front carries it.

Platform capabilities move. Before any engagement starts, I re-verify every constraint on this page against the platform’s current documentation and your actual plan tier. You get what is true at kickoff, not what was true when this page was written.

**Q: My designer built our site in Framer. Can you work with it?**

Yes, and that’s a shape I work in today: the designer owns the look, I own the machine layer and publish discipline. Your designer’s work stays exactly as they made it.

**Q: Is Framer bad for SEO?**

No. It renders real HTML and handles the basics well. The gap is the structured layer (schema, crawler permissions, a machine-readable index) and the operational care around site-wide publishing. Both are addable.