Framer already did the technical work, including the AI part

Of all the builders in this category, Framer hands you the most finished technical foundation, and it is the only one we have found that addresses AI readability explicitly. So if your Framer site is not being found, the cause is narrow and identifiable.

Run the free check

Framer automatically generates a sitemap at /sitemap.xml for every published site and a robots.txt in which, according to Framer's documentation, all AI and search crawlers are allowed by default. It also automatically converts pages into structured markdown that AI tools can read, and supports llms.txt. Per-page titles and descriptions are set in page settings, and a page can be excluded with the show-in-search-engines toggle.

What Framer handles without being asked

The technical list that takes an evening on most stacks is largely already done here, which changes what your remaining problem is.

Framer's documentation states that it automatically generates a sitemap for every published site, reachable by adding /sitemap.xml to your domain, with no setup required. It generates a robots.txt for every published site as well.

Per-page titles and descriptions are set in site settings, for the whole site or for individual pages, and metadata for CMS-driven pages can pull values from CMS fields, so a field named Title can be referenced to produce a unique title on every generated page.

That covers the sitemap, robots.txt, and the per-route metadata problem that is the most common real defect elsewhere in this category.

The AI part, which nobody else does

This is the genuinely unusual thing about Framer and it is worth knowing about, because it addresses the channel where a new site has the best chance.

Framer's documentation states that it automatically converts your pages into structured markdown that AI tools can read and reference, and that this requires no setup, working through content negotiation headers or by appending a query parameter to the URL.

It also states that Framer supports llms.txt, described there as a proposed standard that helps AI agents quickly understand your site and access important pages.

And the crawler list in the automatically generated robots.txt is permissive by default, covering Googlebot, GoogleOther and Google-Extended, Bingbot, GPTBot, PerplexityBot and others. That default matters enormously, because the most common way a site loses the AI channel is a copied robots.txt that blocks it.

The one setting that turns you off

With this much handled automatically, the failure modes narrow to a small number, and this is the first to check.

Page settings include a show-in-search-engines toggle. Turning it off adds a noindex tag to that page, which tells search engines to exclude it.

This gets switched off during development, for perfectly sensible reasons, and then not switched back on at launch. The page works, the site looks finished, and it will never appear in a search result.

Check every page, not just the homepage. It is set per page, which means it can be correct on the page you check and wrong on the ones you did not.

Editing robots.txt, and why you probably should not

Framer does not allow direct editing of the generated robots.txt. Its documentation describes uploading a custom robots.txt through the static files feature instead, by opening the Files tab for your domain and uploading a file with the path set to the root.

The important thing here is a caution rather than an instruction. The generated default already allows every search and AI crawler, which is what you want. Replacing it with a file you copied from an article is the single most likely way to make a well-configured Framer site worse.

If you do upload one, read it line by line first and confirm it does not carry a blanket disallow, and confirm it names the current crawler agents rather than deprecated ones.

For most Framer sites the correct action here is none at all.

So why is your Framer site not found

Given how much is handled, a Framer site that gets no traffic usually has one of three causes, and only the first is technical.

The noindex toggle is off on pages you want found. Check it everywhere.

You are still on the framer.website address rather than a custom domain, so everything you build accumulates onto an address you do not own and will eventually leave.

Or, most likely, the site has five pages and all five describe your business. That is five things you can be found for, and the people you want are searching for their problem in words that appear nowhere on your site.

The third one is not a Framer problem and no platform solves it. It is the reason this section of the site exists.

What is still yours on any platform

It is worth being explicit, because a platform that handles this much creates a reasonable assumption that it handles everything.

Framer does not submit your sitemap to Google. It generates and serves it, and nothing tells Google it exists until you verify the domain in Search Console and submit it there.

Framer does not decide what your pages are about, does not write the third-party descriptions of your product that get you into category answers, and does not participate in the communities where your customers are.

The technical foundation being finished is genuinely valuable and it means your effort goes entirely into the part that was always the harder half.

Part of a larger guide

This page is one part of Vibe coding SEO. The other parts:

Questions people ask

Does Framer create a sitemap automatically?
Yes. Framer's documentation states it automatically generates a sitemap for every published site with no setup required, accessible by adding /sitemap.xml to your domain. It does not submit that sitemap to Google, which remains your job through Search Console.
Does Framer block AI crawlers?
No, the opposite. Framer's documentation states that all AI and search crawlers are allowed by default in the automatically generated robots.txt, covering Googlebot, Google-Extended, Bingbot, GPTBot and PerplexityBot among others. This default is one of the better things about the platform.
Why is my Framer page not appearing in Google?
Check the show-in-search-engines toggle in that page's settings first. Turning it off adds a noindex tag, and it is commonly switched off during development and never switched back on. It is set per page, so it can be correct on the page you checked and wrong elsewhere.
Can I edit my robots.txt in Framer?
Not directly. Framer's documentation describes uploading a custom file through the static files feature, with the path set to the root. For most sites the correct action is none, since the generated default already allows every crawler you want and replacing it is the likeliest way to make things worse.
Does Framer do anything for AI search?
Yes, and it is unusual in this. Framer's documentation states it automatically converts pages into structured markdown that AI tools can read and reference, requiring no setup, and that it supports llms.txt as a way for AI agents to understand a site and find its important pages.
My Framer site is technically fine but gets no traffic. Why?
Most likely because it has a handful of pages that all describe your business, which is a handful of things you can be found for, while your customers are searching for their problem in words that appear nowhere on the site. No platform solves that one.

Confirm your Framer site is doing what it should

The free Get Found Check reads your published site and confirms the sitemap, robots.txt and per-page tags are all doing what Framer intends.

Run the free check Have Licheo do it for you