Framer

Framer sites get their own dedicated extraction pipeline. The integration handles Framer's structure — the way it renders content, exposes metadata, and serves Open Graph images — better than a generic website crawl would. Auto-detection means you can submit a Framer site via the regular Website flow and Echo will silently switch to the Framer pipeline.

On this page

Why use this

  • Your site is built on Framer (custom domain or .framer.app).
  • You want metadata like the page title, description, and OG image extracted correctly.
  • You'd rather not think about which integration to pick — auto-detection handles it.

How it works

  1. Detection. When you submit a URL, Echo checks the page's <meta name="generator"> tag. If it contains framer, Echo switches to the Framer pipeline automatically — even if you selected "Website" in the form.
  2. Validation. Echo verifies the Framer site is reachable, follows redirects, and locks in the canonical URL.
  3. Extraction. For each page, Echo pulls the page title from <title>, the description from <meta name="description">, and the OG image from <meta property="og:image">. Scripts and styles are stripped, and the main content area (preferring <main>, falling back to <body>) is converted to clean text.
  4. Optional AI processing. When AI extraction is enabled, Echo uses a structured pass to produce cleaner content with richer metadata; otherwise, basic text extraction with the page description prepended is used.

Each page becomes one content item with the title, description, image, and a stable external ID derived from the URL path so updates land on the same item.

How it differs from related options

  • vs Website synced source — the Website pipeline uses Cloudflare's headless browser for any public site. Framer uses a lightweight HTML fetch + extraction tuned for Framer's specific output. Auto-detection means you usually don't have to choose — pick Website and let Echo route.
  • vs URL manual upload — URL handles one page at a time, manually refreshed. Framer integration discovers and keeps pages in sync as a group.

Step-by-step setup

  1. Open Integrations from the dashboard's Synced content sources section.
  2. Click Add source and select Framer — or select Website and let Echo auto-detect.
  3. Enter your Framer site URL (custom domain or your-project.framer.app).
  4. Complete the domain verification step.
  5. Select the target assistant.
  6. Submit.

Echo confirms the site is a valid Framer property, extracts the site name, and registers it. Initial import runs in the background.

Common errors and troubleshooting

  • "Failed to fetch Framer page" — the URL returned an error or timed out. Verify the site is published (not in draft) and publicly accessible.
  • "Page title shows as 'Untitled Page'" — the Framer page has no <title> set. Open the page in Framer and add a title in the page settings.
  • "Domain verification failed" — verification couldn't confirm ownership. Re-check the domain configuration in Framer or contact support if the issue persists.
  • Echo picked the wrong pipeline — auto-detection reads the generator meta tag. If your site doesn't expose one, manually select Framer in the form instead of letting auto-detect run.
  • Some pages are missing — discovery depends on the entry URL you submit. Submitting the homepage typically discovers more than submitting a deep link.
Submit Website, get Framer
If you submit a Framer site as a Website integration, Echo silently switches to the Framer pipeline. The integration card will show "Framer" as the source type once switching is complete.