---
title: Running multiple sites on a single domain
related:
  - https://docs.kentico.com/k12sp/configuring-kentico/managing-sites/setting-up-multiple-websites.md
  - https://docs.kentico.com/k12sp/configuring-kentico/managing-sites/setting-up-multiple-websites/configuring-nested-websites.md
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

This page describes how to run multiple websites in separate sub-folders on a single domain. In this scenario, you do not need to obtain new domains for each site.

## Example - Installing two sites onto a single domain

1. [Install](https://docs.kentico.com/k12sp/installation/installing-kentico.md) a Kentico web project to the following folder: **C:\inetpub\wwwroot\kenticofolder**.

   - In the installer, choose **Custom installation** and disable the **Register to IIS** option in the **Installation type** settings (does not create a virtual directory).
2. Open your **Internet Information Services (IIS) Manager** console (_Start -> Control Panel -> Administrative tools -> Internet Information Services (IIS) Manager_).
3. Create a new virtual directory named **kenticoweb**.
   - The name of the virtual directory must be different than the folder where you installed the web project.
   - Set the **Physical path** to a non-website folder in the root of a local disk. Ideally, create an empty folder for this purpose, for example: _c:\empty_
4. Create two IIS applications under **kenticoweb** named **web1** and **web2**.

   - Set the **Physical path** of both applications to the web site folder of the installed project (**C:\inetpub\wwwroot\kenticofolder\CMS** in this example).
   - Set the application pool according to the type that you specified in the installation of the Kentico web project.
5. Open your browser and type in either **http://localhost/kenticoweb/web1** or **http://localhost/kenticoweb/web2**.
6. Sign in to the Kentico administration interface and open the **Sites** application.
7. [Install](https://docs.kentico.com/k12sp/configuring-kentico/managing-sites/installing-new-sites.md) both sites. Set the **Site domain name** fields:

   - Website 1: **localhost/kenticoweb/web1**
   - Website 2: **localhost/kenticoweb/web2**

Now when you go to **<http://localhost/kenticoweb/web1>**, you will see website 1. If you go to **<http://localhost/kenticoweb/web2>**, you will see website 2.

### Synchronizing global data for the sites

To ensure the synchronization of settings and global objects between the two sites, you need to set up a [Web farm](https://docs.kentico.com/k12sp/configuring-kentico/setting-up-web-farms.md) environment:

1. Sign in to the Kentico administration interface on one of the sites.
2. Open the **Settings** application.
3. Select the **Versioning & Synchronization -> Web farm** category.
4. Select **Automatic** as the **Web farm mode**.
5. Click **Save**.
6. Add the following key to the __ section of the **web.config** file in the installation directory shared by both websites:

   ```html

   <add key="CMSWebFarmSynchronizeFiles" value="false" />


   ```

The system automatically creates web farm servers for the applications and performs synchronization. The _CMSWebFarmSynchronizeFiles_ web.config key disables synchronization of files, which is not needed since the applications already use the same physical folder.

### Avoiding file system conflicts

To prevent problems with file conflicts for [web analytics](https://docs.kentico.com/k12sp/on-line-marketing-features/configuring-and-customizing-your-on-line-marketing-features/configuring-web-analytics.md) log files and [locally stored search indexes](https://docs.kentico.com/k12sp/configuring-kentico/setting-up-search-on-your-website/using-locally-stored-search-indexes.md), you need to configure the application to use a shared file system. Add the following key to the __ section of the **web.config** file in the installation directory shared by both websites:

```html

<add key="CMSSharedFileSystem" value="true" />

```

With a shared file system, the system automatically avoids file name collisions for smart search indexes and web analytics logs.

Your websites should now work without issues.