Framer SEO audit
Verify what search engines actually receive from a Framer site: rendered content, CMS collection canonicals, a real 404 status, image sizes and per-page metadata.
Framer publishes a site as a React application with pre-rendered HTML, which makes it fast to build and easy to get subtly wrong for search: components that hydrate before they show content, CMS collection pages that share a canonical, a custom 404 that needs to return a real 404 status, and images placed at full resolution. CrawlX crawls the published site with 150+ technical checks and compares the raw response with the rendered page so you know exactly what a crawler receives.
Framer issues CrawlX detects
The problems that show up again and again on Framer sites — grouped by root cause and ranked by how much of the site they touch.
01Content that appears only after the app hydrates
Framer pre-renders pages, but components driven by effects, code overrides or CMS fetches can render client-side. CrawlX crawls the raw HTML and the rendered DOM (Professional and above) and reports text, headings and links present only after JavaScript runs.
02CMS collection pages with missing or shared canonicals
Collection detail pages generated from one template can end up with no canonical or with the template's canonical applied to every item. CrawlX validates canonicals on every page for presence, self-reference and cross-page conflicts, grouped by collection.
03A custom 404 page that returns 200
Designing a 404 page is easy; making sure unknown URLs return a 404 status rather than a styled 200 is what matters for indexing. CrawlX requests a deliberately missing URL and reports soft 404s wherever a not-found page is served with a success status.
04Images served at upload resolution
Images placed on the canvas without a size constraint are delivered at full resolution, and background images skip responsive variants. CrawlX reports oversized images, missing dimensions and missing lazy loading, and on Professional and above measures the Largest Contentful Paint they cause.
05Duplicate titles and descriptions across CMS templates
When a page's settings are left empty the site-wide title and description are reused, so CMS items all share one title. CrawlX reports duplicate, missing and over-length titles and descriptions and groups them by template.
06Links to the framer.app or framer.website subdomain
Embeds and copied links can point at the default Framer subdomain instead of your custom domain. CrawlX reports internal links, canonicals and hreflang that resolve to a different host than the one being crawled.
07Heading structure driven by text styles
A text component styled as a heading is not necessarily an h1, and a page can end up with none or several. CrawlX checks each page for a single h1 and a sensible heading hierarchy.
08Redirect chains and host inconsistencies
Redirects added in Site settings stack with the www and HTTPS hops. CrawlX follows every chain, reports hop counts and final status, and lists internal links still pointing at the first hop.
Crawl in the cloud, fix where the code lives
Most Framer sites have no code repository, so fixes are delivered as ready-to-apply changes with the affected pages listed. Connect a GitHub repo for any code you do keep and those fixes arrive as pull requests.
The Framer workflow
- CrawlX crawls the published Framer site from the cloud. Nothing is added to the project and no code component is required.
- JavaScript rendering (Professional and above) captures what the React application shows after hydration, so the raw pre-rendered HTML and the final page are both audited.
- Framer sites are built on the canvas, not in a code repository, so there is normally no GitHub repo for CrawlX to open a pull request against. Each finding comes with the exact change to make — the page setting, canonical value, image constraint or redirect — and the pages it applies to.
- If part of your site is code you keep in GitHub — code components, overrides or a separate app — connect that repository and CrawlX drafts pull requests for the issues that live there.
Framer SEO questions
Does CrawlX see the content on my Framer site?
Yes. CrawlX crawls the pre-rendered HTML Framer publishes, and on Professional and above also renders the page in headless Chromium. Content that only appears after hydration is reported so you know what a crawler that does not run JavaScript would miss.
Can CrawlX fix Framer SEO issues for me?
CrawlX opens pull requests only against a connected GitHub repository, and a Framer site is edited on the canvas rather than in a repo. So for Framer you get the exact ready-to-apply change and the affected pages; if you keep code components in GitHub, connect that repo and those fixes arrive as PRs.
How do I know whether my Framer 404 page returns the right status?
CrawlX requests a URL that cannot exist on your site and records the status code. If the custom 404 page is served with a 200 status, it is reported as a soft 404 so you can correct it before search engines index the page.
Do I need to add anything to my Framer project?
No. CrawlX runs from the cloud and only needs the public URL. Search Console and GA4 can be connected on Starter and above to weigh findings by the traffic each page earns.
SEO audits for other stacks
Audit your Framer site now
Your first cloud crawl runs free — 500 URLs, no credit card, nothing to install.