> 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/advanced-features/custom-html.md).

# Custom HTML

Add #form to an Action Page URL so supporters skip straight to the Form section.

Add `#form` to an Action Page URL so supporters skip straight to the Form section.

## Using HTML Anchors to Link Directly to the Form on Your Action Pages

You can guide donors straight to the Form section of your Action Pages by adding **#form** to the end of your share link URL. This bypasses the content at the top of your Donation or Lead Page and takes supporters directly to the Form details.

**Example:** `https://yourpageurl.com#form`

You can also create a "Skip to form" link within a Text Block on your Donation or Lead Page:

1. In the text editor, type your link text (e.g., *Skip to form*).
2. Highlight the text and use the hyperlink tool.
3. Enter `#form` as the link destination.

When supporters click this link, they'll be taken directly to the Form section of your page.

*Note:* *At this time, additional HTML capabilities are not supported. If you'd like to request more HTML options, please* [*contact Support*](https://www.anedot.com/getsupport)*.*


---

# 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/advanced-features/custom-html.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.