> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/action-pages/page-builder/page-settings-seo-sharing-and-tracking.md).

# Page Settings: SEO, Sharing, and Tracking

Set an Action Page's SEO title and description, social share text and images, share buttons, default source code, tracking codes, and custom CSS.

The **Settings** panel holds how your page appears in search and on social media, and the codes that track it. You'll find it in the Page Builder under **Setup > Settings**. This article covers each section of the panel.

## Open Settings

To open Settings:

1. Go to **Action Pages > Pages**.
2. Hover over the page you want to edit.
3. Click **⋮ > Edit**.
4. Select **Setup > Settings**.

## Settings Preset

Named presets reuse tracking codes, pixels and custom CSS across pages. Applying a preset replaces the tracking codes on this page. See Presets in the [Page Builder Overview](/action-pages/page-builder.md).

## Page URL

Shows the **Public page URL** with a **Copy** button. If your account uses a custom domain, the **Anedot hosted URL** also shows. To change the URL slug, use **Details**.

## SEO

* **Title tag:** The page title in search results.
* **Meta description:** The description in search results.

## Social Sharing

* **Share title** and **Share description:** The text shown when the page is shared. They also fill the Twitter fields when you save.
* **Default share image** and **Twitter share image:** The images shown when the page is shared.
* **Share Buttons:** Shows buttons for sharing the page on social networks.

## Favicon

Choose the icon that shows in the browser tab.

## Source Code

Enter a **Default Source Code** to track where submissions come from. It's added to the page link when you copy it from Share. See [URL Parameters](/action-pages/advanced-features/url-parameter.md).

## Tracking Codes

Add your Google Analytics, Google Tag Manager and Facebook Pixel codes. See [Tracking Codes for Action Pages](/action-pages/advanced-features/tracking-codes-for-action-pages.md).

## Custom CSS

Add page-specific CSS that applies to the hosted page. Custom CSS shows only when it's turned on for your account.

When you're done, click **Save**.

## Related Articles

* [Tracking Codes for Action Pages](/action-pages/advanced-features/tracking-codes-for-action-pages.md)
* [Share An Action Page](/action-pages/action-page-basics/share-an-action-page.md)
* [Page Builder Overview](/action-pages/page-builder.md)


---

# 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://docs.anedot.com/action-pages/page-builder/page-settings-seo-sharing-and-tracking.md?ask=<question>&goal=<user_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.