Published Tools on Your Pages

A Published Tool block puts one of your account's own tools on a page of your website. A visitor types a website address, presses the button, and sees the result right on the page. The tool is one of the read actions your account publishes in Settings, Connections, Publish (Publishing).

Add One to a Page

1. Open the page in the builder and choose Published Tool under Connect in the library, or in Add Section.
2. In the Published Tool Block pop up, choose the Tool. The list holds the published actions that are turned on. One that is not read only, or that needs more than one input, is shown with the reason and cannot be chosen (action sites.tools.list).
3. Change the Heading, Input Label, and Button Label if you like. They start as the tool's own words.
4. Result Addresses is on at first: each checked website gets its own shareable address on this page, like /tools/ssl-checker/example.com/, with the result already shown. Allow Search Engines on Results is off at first.
5. Choose Save Block, then publish the page. Block Settings in the settings panel opens the pop up again.

In the builder and the preview the block is a card with the tool's name that never runs the tool. The tool runs on the published website only.

What a Visitor Sees

A box for a website address and your button. A bar fills while the tool works and reaches the end only when the answer is back, and the result appears as plain rows of a label and a value, taken from what the tool answers. With result addresses on, the page's address changes to the result's own address, with a Copy button. Opening a result address runs the check at once, or shows a result from the last 10 minutes.

Checks That Protect It

• The address must be a public website name, like example.com. A web address with a path is cut to its host name; anything else is refused with "Enter a public domain name, like example.com."
• A result from the last 10 minutes is shown as it is, with no new run. Otherwise the visitor passes Cloudflare Turnstile with your own keys from Forms Settings. Until your keys are set, the block says it is not taking checks right now.
• Eight runs a minute for each visitor and six a minute for each website address. A visitor over the limit is told to wait.
• A run is sent only from a page of the same website. A post from any other website is refused.
• A tool turned off, removed, or no longer read only stops answering. Nothing is run for a block that is not on the published website.

What Is Kept

For 10 minutes, the last result for each website address on each block, in your account. For counting the limits, a hash of the visitor that changes every day and the address checked, forgotten after two days. Never the visitor's address, and nothing is tracked.

Result addresses are not stored pages: they are left out of the sitemap, and ask search engines to stay out unless you allow them on the block.

Who Can Do It

People who can edit Websites add and change blocks. Publishing the page is a person's step, as for every page. An AI agent can list the tools (sites.tools.list) and save a block as a draft like any other page change.

For AI Agents

sites.tools.list reads which published tools a page can show. Everything else is the page save.