> 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/troubleshoot-iframes.md).

# Troubleshoot IFrames

If an iFrame on your site is not displaying correctly, use the HTML template below to help identify and resolve issues.

If an iFrame on your site is not displaying correctly, use the HTML template below to help identify and resolve issues. This will allow you to test your **Action Page embed code** in a clean environment.

## Instructions

1. Copy the HTML template below.
2. Insert your **Action Page embed code** between the comment markers:

```html
<!DOCTYPE html>
<html lang="en-US">
<head>
  <title>Anedot iFrame demo</title>
</head>
<body>
  <main>
    <div>
      <!-- iFrame Embed code -->
      <!-- Paste embed code between these comments -->
    </div>
    <footer>&copy; Anedot</footer>
  </main>
</body>
</html>
```

3. Save the file and open it in your web browser to preview.

## Adjusting IFrame Size and Scrolling

To remove unwanted scrolling, set **specific height and width values** for your iFrame.

Example:

```html
<iframe src="YOUR_URL_HERE" width="100%" height="800" style="border:none;"></iframe>
```

**Tips:**

* Test your adjustments on **both desktop and mobile devices** to ensure the content fits without unnecessary scrolling.
* Increase the height if content is being cut off.
* Use `width="100%"` for responsive designs.


---

# 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/troubleshoot-iframes.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.