---
title: Deploying websites
---

> 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).

> **Info:** 
>
> #### [Deploying sites](https://docs.kentico.com/13/deploying-websites/deploying-sites-to-a-live-server.md)
>
> After you finish developing your website, deploy it to a live hosting server (production environment).

> **Info:** 
>
> #### [Content staging](https://docs.kentico.com/13/deploying-websites/content-staging.md)
>
> Break up the website's development, content creation, and deployment process. Set up different environments for various stages, for example: Development -> Testing -> Content editing -> Production.

> **Info:** 
>
> #### [Export and Import](https://docs.kentico.com/13/deploying-websites/exporting-and-importing-sites.md)
>
> Export your website with all associated objects and settings, and then import the website to a different instance of Xperience.

> **Info:** 
>
> #### [Microsoft Azure deployment](https://docs.kentico.com/13/deploying-websites/running-xperience-on-microsoft-azure.md)
>
> Deploy your sites to Microsoft Azure to ensure scalability, serve content from a CDN, and get access to other benefits of a cloud deployment.