---
schema_version: "1"
id: d624659a6d3928a2b74806ef9aef347450050ff432559d59705d7b8d2f0b5687
title: SiteDotCom
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_sitedotcom.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_sitedotcom.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 52729fab4146da5358b062cbdca7407e253bc045f13145d1a1856c30bed5e345
description: Represents a site for deployment.
---
# SiteDotCom

Represents a site for deployment.

SiteDotCom extends the [MetadataWithContent](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_metadatawithcontent.htm "MetadataWithContent is the base type for all metadata types that contain content, such as documents or email templates. It extends Metadata. You can’t edit this object.") type and inherits its fullName and content fields.

## Declarative Metadata File Suffix and Directory Location

SiteDotCom components are stored in the siteDotComSites directory of the corresponding package directory.

The file name for the metadata .xml file is \[sitename\]1.site-meta.xml. The file name for the site file is \[sitename\]1.site.

When a Lightning site is created, two sites are made behind the scenes: CustomSite (of type ChatterNetwork) and SiteDotComSite (of type ChatterNetworkPicasso). These sites are named, respectively, _<site\_name>_ and _<site\_name>1_. The corresponding MDAPI file names are _<site\_name>._site-meta.xml and _<site\_name>_1.site-meta.xml. 1 is appended to the SiteDotComSite type to keep the name unique from the corresponding CustomSite site.

![Note](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/images/icon_note.png)

#### Note

There is a file size limitation when using the Metadata API to deploy a site from sandbox to production. The assets in the .site file can't be larger than 40 MB. The site gets created, but the assets show in the new site as broken. To fix the assets, export the assets from the sandbox environment separately and then import them into your new site.

## Version

SiteDotCom components are available in API version 30.0 and later.

## Fields

| Field | Field Type | Description |
| --- | --- | --- |
| label | string | The name of the site that you’re deploying. |
| siteType | ([enumeration](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_objects_intro.htm#enumeration_title) of type string) | Required. Identifies whether the site is a ChatterNetworkPicasso site for Experience Cloud Sites, or a Siteforce site for Site.com sites. |

## Declarative Metadata Sample Definition

Here are two examples of a SiteDotCom XML definition.

<?xml version="1.0" encoding="UTF-8"?>
<SiteDotCom xmlns="http://soap.sforce.com/2006/04/metadata">
    <label\>testsite</label\>
    <siteType\>Siteforce</siteType\>
</SiteDotCom\>

<?xml version="1.0" encoding="UTF-8"?>
<SiteDotCom xmlns="http://soap.sforce.com/2006/04/metadata">
    <label\>testCommunity</label\>
    <siteType\>ChatterNetworkPicasso</siteType\>
</SiteDotCom\>

## Usage

You can only deploy a .site file retrieved in Summer ’19 or later. Older files aren’t supported.

## Wildcard Support in the Manifest File

This metadata type supports the wildcard character \* (asterisk) in the package.xml manifest file. For information about using the manifest file, see [Deploying and Retrieving Metadata with the Zip File](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_meta.meta/api_meta/file_based_zip_file.htm).