> For the complete documentation index, see [llms.txt](https://gitbook-v2-go126epqd-gitbook.vercel.app/url/gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook-v2-go126epqd-gitbook.vercel.app/url/gitbook.com/docs/manage-your-site/site-settings.md). # Site settings Customize and edit settings across your published site
A GitBook screenshot showing site settings

Update the settings for your published documentation.

### General
Site title Change the name of your site. If you don't have a custom logo, this is the name that your site visitors will see.
Analytics cookie If you want to use GitBook’s [site analytics](/url/gitbook.com/docs/analytics/insights.md), your site will use cookies to identify returning visitors and gather the data needed to view your analytics. You can choose to disable these cookies, but it will prevent you from using site analytics.\ \ The cookies notice appears when your site has analytics enabled through an integration, especially **Google Analytics**. To remove the notice, open **Site settings → Integrations** :puzzle-piece: in the top-right. Then disable or remove **Google Analytics**. Disabling these cookies also turns off [site analytics](/url/gitbook.com/docs/analytics/insights.md) for that site.
Unpublish site Unpublish your site, but keep its settings and customizations. You can publish your site again at any time.
Delete site Unpublish and remove your site from the **Docs site** section in the GitBook app. **Note:** Deleting a site is a permanent action and cannot be undone. Any settings and customizations will be lost, but your content will remain in its [space](/url/gitbook.com/docs/create-content/content-structure/space.md).
Access Manage who can access and administer your docs site. Open **Access** and click **Manage permissions**. You can also use **Share** from the site’s **Overview** page. Site permissions are available on all plans. By default, new sites derive permissions from their linked [spaces](/url/gitbook.com/docs/create-content/content-structure/space.md), until you update permissions from the site permissions modal. Site permissions can also affect the permissions of linked spaces that use **Inherited** mode. In this case, each inherited space receives the highest permission level granted by the organization, any parent collection, and any site that includes it.
### Agents {% content-ref url="/pages/QEdtUjQ47A0aK7o8HIzN" %} [Overview](/url/gitbook.com/docs/gitbook-agent/overview.md) {% endcontent-ref %} ### Styleguide Create, reuse, or detach the styleguide that defines your team's writing rules and keeps GitBook Agent consistent. {% content-ref url="/pages/ZVg6bZguPovk1woIsVdk" %} [Style guide](/url/gitbook.com/docs/create-content/styleguide.md) {% endcontent-ref %} ### Audience
Audience Choose who sees your published content. See [Publish a docs site](/url/gitbook.com/docs/publish/publish-a-docs-site.md) for more info.
Adaptive content Turn on adaptive content for your site pages, variants, and sections. [Adaptive content](/url/gitbook.com/docs/publish/adaptive-content.md) lets you hide or show content for different visitors, depending on their permissions. Your visitor token signing key will also be displayed here.
### Domain and URL
Custom domain Configure a custom domain to unify your site with your own branding. See [Set a custom domain](/url/gitbook.com/docs/publish/custom-domain.md) for more info.
GitBook Subdirectory Publish your content on a subdirectory (e.g. `yourcompany.com/docs`). Learn more in [Setting a custom subdirectory](/url/gitbook.com/docs/publish/custom-domain/setting-a-custom-subdirectory.md).
### Redirects {% content-ref url="/pages/rcmnyzKOgcYE9OgyZD2Y" %} [Site redirects](/url/gitbook.com/docs/publish/site-redirects.md) {% endcontent-ref %} ### Features
PDF export Let your visitors export your site as a PDF. See [PDF export](/url/gitbook.com/docs/publish/pdf-export.md) for more info.
Page ratings Choose whether or not visitors to your published content can leave a rating on each page to let you know how they feel about it. They’ll be able to choose a sad, neutral, or happy face. You can review the results of these ratings by opening [**Analyze → Traffic**](/url/gitbook.com/docs/analytics/insights/traffic.md) in your site’s sidebar, then selecting **Page feedback**.
### AI & MCP AI settings are available on different plans. The search box placement (AI Assistant Ask) is available on Essential and Ultimate site plans. The sidebar placement (AI Assistant Chat) and MCP connectors are available on Ultimate. AI features use AI credits.
AI Assistant Turn AI Assistant on or off for your site. See [AI Assistant](/url/gitbook.com/docs/ai-for-your-readers/gitbook-ai-assistant.md) for more info.
Appearance Use **Placement** to choose where the Assistant appears: **Sidebar** for the full chat experience (AI Assistant Chat), available on Ultimate site plans, or **Search box** to answer questions in your site’s search bar (AI Assistant Ask), available on Essential and Ultimate site plans. You can also set the Assistant greeting here, which applies to the sidebar placement only. See [AI Assistant](/url/gitbook.com/docs/ai-for-your-readers/gitbook-ai-assistant.md) for more info.
Extend GitBook Assistant with MCP connectors Configure MCP servers that GitBook Assistant can use when answering questions inside your docs. This setting is available on Ultimate site plans. See [MCP servers for published docs](/url/gitbook.com/docs/ai-for-your-readers/mcp-servers-for-published-docs.md) for more info.
### Connections {% content-ref url="/pages/p6K5x8aCszGQ0xYf96Z2" %} [Connections](/url/gitbook.com/docs/ai-for-your-readers/connections.md) {% endcontent-ref %} ### Structure {% content-ref url="/pages/1XRw1GP3RDSWHxEE1tQb" %} [Site structure](/url/gitbook.com/docs/manage-your-site/site-structure.md) {% endcontent-ref %} ### Plan {% content-ref url="/pages/yshuePqcxELaw0iNFK7a" %} [Plans](/url/gitbook.com/docs/account-and-billing/plans.md) {% endcontent-ref %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://gitbook-v2-go126epqd-gitbook.vercel.app/url/gitbook.com/docs/manage-your-site/site-settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.