How to Edit robots.txt in Framer (and Check It Works)

You publish a Framer site, Google starts crawling, and then you realise you have no idea what your site is actually telling search engines at /robots.txt. If you’ve been searching for “edit robots.txt in Framer,” most of what you’ll find assumes you can open a file and tweak a few lines. Framer doesn’t work that way.

Framer automatically generates a robots.txt file for every published site, and the live file you see by visiting yourdomain.com/robots.txt is the one search engines use when crawling your pages (Framer: Access your robots.txt file). That means the only thing that matters is what your domain serves right now — not what you think you configured.

In practice, “editing” framer robots.txt usually means one of two moves: confirm the default file is fine and leave it alone, or upload a custom robots.txt via Static Files to replace Framer’s generated version (available on Pro and Enterprise plans). This guide shows you how to check the live file, replace it the way Framer documents, and verify the exact output crawlers will read. If you want extra confidence before you upload anything, you can also run your draft through a checker or generator like Robots.txt Checker, Robots.txt Generator, and AI Crawler Checker.

How to View Your Live Framer robots.txt

The safest way to confirm your framer robots.txt setup is to look at the exact file your published site serves. Framer documents a simple method: open the robots.txt file directly in your browser, on the live domain. That is the version crawlers read when they decide what to crawl and index.

Framer’s help docs define robots.txt as the file that tells search engines which pages they can crawl and index on your site. Framer also automatically generates a robots.txt file for every published site. (Source: Access your robots.txt file.)

Copy the exact domain you want to check (your production domain, not a draft URL).
In your browser, go to your-domain.com/robots.txt.
Read the text that loads. This page is your live robots.txt file.

Framer states that you can access a Framer site’s robots.txt by entering your site’s domain followed by /robots.txt, and that the file you see there is the live robots.txt file that search engines use when crawling your site. (Source: Framer help documentation.)

Common Checks When You Edit robots.txt in Framer

People often say “edit robots.txt Framer,” but the first step is always verification. Open /robots.txt on the domain that matters, and confirm you are looking at the right site.

Check the domain: if you have multiple domains connected, repeat the check on each domain you care about.
Check that it’s published: Framer’s robots.txt is generated for published sites, so validate on the public URL.
Check what crawlers will see: treat the browser view of /robots.txt as the source of truth, because Framer explicitly says search engines use that live file when crawling.

When Should You Replace Framer’s Default robots.txt?

If the framer robots.txt you just verified looks sensible, leave it alone. Framer automatically generates a robots.txt for every published site, and search engines use the live file at /robots.txt when they crawl your pages (Framer: Access your robots.txt file). Replacing it changes how crawlers access your site, so do it only when you have a specific reason.

Use this checklist to decide whether “edit robots.txt Framer” really means “upload a replacement,” or whether the default is enough.

You have a specific reason to change crawler access. Framer’s docs support two modes: use the auto-generated robots.txt, or upload a custom robots.txt via Static Files when you need different directives.
You are on a plan that supports replacement. Framer states that uploading a custom robots.txt via Static Files is available on Pro and Enterprise plans (Framer: Access your robots.txt file).
You can commit to owning the file going forward. Once you replace the generated file, you are responsible for maintaining your robots.txt content. Framer confirms that an uploaded robots.txt replaces the automatically generated one (Framer: Access your robots.txt file).
You can verify the change on the exact live domain. If you cannot reliably check yourdomain.com/robots.txt after the change, don’t ship it.

When You Should Keep Framer’s Default robots.txt

Keep the default if your goal is simply to “have a robots.txt.” Framer already provides one for every published site, and you can view the exact live version at /robots.txt (Framer: Access your robots.txt file). In that situation, uploading a custom file adds ongoing work and creates a new failure mode: you can accidentally ship a restrictive rule and reduce crawl access.

If you do decide to replace it, treat the file like production configuration. Draft it carefully, then upload and re-check the live URL until you see the exact content you intended.

How to Upload a Custom robots.txt in Framer (Static Files)

Once you have a finished file you trust, “edit robots.txt Framer” means uploading a replacement file through Framer’s Static Files feature. Framer documents that you can upload a custom robots.txt this way, and that it replaces the automatically generated file for your published site. (Source: Access your robots.txt file.)

Framer also states that uploading a custom robots.txt is available on Pro and Enterprise plans. (Source: Framer help documentation.)

Open your project dashboard in Framer.
Select your domain.
Open the Files tab.
Upload your robots.txt file.
Set the file path to /.

That path setting matters because it tells Framer to serve your uploaded file at the root of the domain, which is where crawlers request it (your-domain.com/robots.txt). Framer explicitly calls out the “Files” tab upload flow and the requirement to set the path to “/”. (Source: Access your robots.txt file.)

Keep The Filename And Location Literal

Use the exact filename robots.txt and upload it through Static Files with the path set to /. If you upload a differently named file or place it on a different path, it will not be the framer robots.txt file search engines fetch at /robots.txt.

What Happens After You Upload a Custom robots.txt?

If you upload robots.txt through Static Files with the path set to /, Framer will treat that file as the one served at /robots.txt on your live domain. Your upload becomes the framer robots.txt file search engines read, and it replaces Framer’s automatically generated robots.txt. Framer describes both the default behavior (auto-generated for every published site) and the replacement behavior for custom uploads in Access your robots.txt file.

This replacement model is why “edit robots.txt Framer” means “publish a full custom file you own.” After the upload, Framer will not merge your directives into the generated file. Crawlers see whatever text your custom robots.txt contains when they request yourdomain.com/robots.txt.

How to Confirm Your Custom robots.txt Is the Live One

Verification is simple and Framer documents it: open the live URL in a browser. The content you see at /robots.txt is the live file that search engines use when crawling your site (Framer: Access your robots.txt file).

Open a browser window (an incognito or private window helps avoid cached content).
Go to your-domain.com/robots.txt.
Confirm the text matches the custom robots.txt you uploaded.

If you still see the old, auto-generated file, something about the upload target is off. The most common causes are checking the wrong domain (for example, a different connected domain than your production one) or not actually serving the file at the root path /. Framer’s docs keep the check grounded: the live truth is whatever loads at /robots.txt on the domain you care about.

Once the live URL shows your intended contents, you can assume crawlers will fetch the same file, because Framer states that the file at /robots.txt is what search engines use when crawling your site (Framer: Access your robots.txt file).

The “It’s Live, But Not Live” Gotcha: Verify the Exact File Crawlers See

The only “source of truth” for framer robots.txt is what loads on your live domain at /robots.txt. Framer explicitly says that when you open /robots.txt, you are viewing the live robots.txt file that search engines use when crawling your site (Framer: Access your robots.txt file). If you uploaded a custom file, this quick check catches the common mistake where you think you shipped an update, but crawlers still see something else.

Open the exact production domain in a browser. Type your-domain.com/robots.txt directly. Do this on the domain you care about, because crawlers fetch robots.txt per host.
Read the contents line by line. Confirm the text matches what you intended to publish. If you are trying to “edit robots.txt Framer,” this is how you confirm the edit actually took effect.
Repeat for each connected domain. If your site responds on more than one domain, check /robots.txt on each one.

What This Check Actually Proves

This browser check answers one question: “What file does this domain serve at /robots.txt right now?” That is the same question search engines ask when they crawl, because Framer states the file at /robots.txt is the live robots.txt that crawlers use (Framer: Access your robots.txt file).

If the content is wrong, treat it as a deployment issue, not a robots.txt theory issue. Either you are looking at the wrong domain, or the live file is still the default auto-generated robots.txt, or your custom upload did not replace it the way you expected.

Framer’s documented workflow stays simple: access the file by visiting your domain plus /robots.txt, and use that live output as your verification step (Framer: Access your robots.txt file).

Free Tools to Check and Generate robots.txt Before You Upload

The live file at /robots.txt is the source of truth for framer robots.txt verification, but you still need to feel confident in what you plan to upload. A small typo or an overly restrictive directive can change how search engines crawl and index your site (Framer: Access your robots.txt file). Before you “edit robots.txt Framer” by uploading a replacement, run the text through a checker and draft it in a generator you can review line by line.

Balzac Robots.txt Checker, paste in your robots.txt content to sanity-check what you wrote before it becomes the live file at yourdomain.com/robots.txt.
Balzac Robots.txt Generator, draft a robots.txt from scratch when you know you need a custom file, but you do not want to hand-write every line.
Balzac AI Crawler Checker, check how AI crawlers relate to your crawl setup before you publish changes.

How to Use These Tools With Framer’s Replacement Workflow

Framer’s docs are clear about the mechanics: Framer auto-generates robots.txt for published sites, you can replace it by uploading a custom robots.txt via Static Files, and the live file at /robots.txt is what search engines use when crawling your site (Framer: Access your robots.txt file). These tools fit around that workflow.

Copy your current live output by opening yourdomain.com/robots.txt in a browser.
Edit or draft your replacement in a plain text editor, or start with the Balzac Robots.txt Generator if you prefer a guided draft.
Validate the exact text you plan to ship by pasting it into the Balzac Robots.txt Checker.
Upload the finished file to Framer using Static Files (Framer documents the upload flow and that it replaces the generated file).
Re-check the live file by reloading /robots.txt on the production domain, since that is the version crawlers read.

If you treat robots.txt like production configuration, you avoid the most common failure mode: uploading a file you never validated, then assuming it matches what crawlers will fetch from your Framer domain.

FAQ: Framer robots.txt Questions People Ask Most

Most robots.txt mistakes come from assuming you changed something without confirming what the domain actually serves. With framer robots.txt, the answers are straightforward because Framer documents how the file works and how you verify it.

Framer robots.txt FAQs

Does Framer create a robots.txt automatically?
Yes. Framer automatically generates a robots.txt file for every published site. Framer also defines robots.txt as the file that tells search engines which pages they can crawl and index. (Source: Access your robots.txt file.)

Where do I see the live robots.txt for my Framer site?
Open your domain in a browser and add /robots.txt. Framer states you can access it by entering your site’s domain followed by /robots.txt, and what you see there is the live file search engines use when crawling your site. (Source: Access your robots.txt file.)

Can I edit robots.txt directly inside Framer?
Framer’s documented approach is replacement, not line-by-line editing of the generated file. If you need a custom robots.txt, Framer says you can upload one using Static Files. (Source: Access your robots.txt file.)

How do I upload a custom robots.txt (the supported way to “edit robots.txt Framer”)?
Framer documents this flow: go to your project dashboard, select your domain, open the Files tab, upload robots.txt, then set the file path to /. (Source: Access your robots.txt file.)

What plans support uploading a custom robots.txt?
Framer states that uploading a custom robots.txt via Static Files is available on Pro and Enterprise plans. (Source: Access your robots.txt file.)

What happens after I upload my own robots.txt?
Your uploaded file replaces Framer’s automatically generated robots.txt. Framer explicitly describes this replacement behavior. (Source: Access your robots.txt file.)

How do I confirm my custom robots.txt is the one crawlers see?
Reload your-domain.com/robots.txt and read the contents. Framer says that when you open /robots.txt, you are viewing the live robots.txt file that search engines use when crawling your site. (Source: Access your robots.txt file.)

Quick Wrap-Up and Next Step

Your framer robots.txt setup comes down to one loop: check what is live, replace it only when you have a clear reason, then verify the live output again. Framer documents the core mechanics in Access your robots.txt file: every published Framer site has an auto-generated robots.txt, you can view it by visiting /robots.txt, and search engines use that live file when crawling.

If you remember one thing about “edit robots.txt Framer,” remember this: you are not editing the generated file. You are either leaving Framer’s default alone, or you are uploading a full replacement via Static Files.

View the live robots.txt first. Open your-domain.com/robots.txt in a browser. Framer states this is the live file search engines use when crawling.
Decide whether you actually need a custom file. If you do, prepare a complete robots.txt you are comfortable maintaining.
Upload your custom robots.txt via Static Files. Framer’s documented flow is: project dashboard, select your domain, open the Files tab, upload robots.txt, set the path to /. Framer also states this option is available on Pro and Enterprise plans.
Re-check the live URL. Reload /robots.txt on the exact domain you care about and confirm you see the content you intended. Framer states the file you open at /robots.txt is the one crawlers use.

If you want a fast sanity check before you publish a replacement, use the free Balzac Robots.txt Checker to validate the text you plan to serve at /robots.txt, or draft a clean starting point with the Balzac Robots.txt Generator.

Next step: open your production domain’s /robots.txt in a new tab right now, read what it actually serves, then decide if you should leave it alone or replace it with a file you can confidently verify.

New Balzac signups get 3 free articles with no card.

Sources

Access your robots.txt file