> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/screen-recorder/settings/website-management.md). # Website management Control which websites Instant Replay runs on. Choose the websites where Instant Replay can run. Instant Replay is **off by default for each website**. Enable only the websites where you want recent page activity available for replay. ## Enable the current website Open Screendesk on the website and choose **Enable on this site**. You can also open **Settings → Manage Websites** and choose **Always Enable** for the current domain, or add a domain to **Always Enabled Sites**. ## Block a website Open **Settings → Manage Websites** and choose **Block Site**, or add the domain to **Blocked Sites**. A blocked domain takes precedence over Always Enabled Sites. Remove it from Blocked Sites before enabling it again. ## Remove an enabled website Remove the domain from **Always Enabled Sites** to return it to the default disabled state. Website rules are saved in your current browser profile. They apply to the listed domain; add other subdomains separately when needed. ## When a replay is unavailable Check that Instant Replay is enabled in Settings, the website is allowed and not blocked, and you have used the page since enabling it. Chrome's protected pages and unsupported page content can limit capture. Instant Replay cannot recover activity from before the website was enabled. --- # 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://docs.screendesk.io/screen-recorder/settings/website-management.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.