> For the complete documentation index, see [llms.txt](https://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.com/docs/manage-your-site/customization/sharing-and-social.md).
# Sharing and social
Customize the social account metadata and sharing options for your site
### Social accounts
You can add social accounts to your site’s metadata and footer from the **Sharing** tab in the customization menu.
Click **+ Add account** and choose an account type from the list of included options — such as X, GitHub, LinkedIn, Discord and Bluesky. Adding a social account in this menu also adds it to your site’s metadata.
For each social account, you can toggle its visibility in your docs site’s footer on or off, without affecting the metadata.
### Social preview
Here, you can upload a custom social preview image for your site. This will set the site’s `og:image` to your uploaded image, and it’ll show when the site’s link is shared to any platform or product that supports OpenGraph images, such as Slack or X.
If you don’t add a social preview, GitBook will automatically generate one using your theme color, page title and description.
If your site has multiple [site sections](/docs/manage-your-site/site-structure/site-sections.md), you can use the drop-down menu at the top of the Customization screen to switch between each section and add a custom social preview image for each one.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://gitbook.com/docs/manage-your-site/customization/sharing-and-social.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 `automate deployments from our CI pipeline` 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.
