---
schema_version: "1"
id: 3440b1b273b1f2cc930b0ca195bb6ed18c05f721debb3cb7210f55c094d20543
title: Uploading a Robots.txt File in B2C Commerce
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_uploading_your_robots_txt_file.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_uploading_your_robots_txt_file.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a6bac37cda740e7f81a9e08922e34e4e802452e51664f1fccebf26cdc25ad96d
description: If you choose to create a robots.txt file in an external file, you must upload the file to the correct location on your B2C Commerce server.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Uploading a Robots.txt File in B2C Commerce

If you choose to create a robots.txt file in an external file, you must upload the file to the correct location on your B2C Commerce server.

Upload and manage this file in the cartridge/static/default directory in your custom storefront cartridge using your preferred development tool (for example, the B2C CLI or WebDAV).

You can also manually update the robots.txt file in production after a staging process if the file was accidentally overwritten.

There can only be one robots.txt file per cartridge. Don't put robots.txt files in user directories, because crawlers don't look there.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_note.png)

Note The robots.txt file can only be replicated from instance to instance via code replication. This is because the cartridge/static/default is cartridge-specific not site-specific.