Site speed and uptime: how Sill stays out of the way
Sill is built so that it can never slow your site down or take it offline. Every Sill install works the same way: your pages never wait for Sill, and if any part of Sill fails, is slow or is unreachable, your site behaves exactly as it would without Sill installed. This page answers the questions merchants ask most about speed, outages and running more than one install.
Can Sill slow down my pages?
Section titled “Can Sill slow down my pages?”No. None of the Sill installs makes your visitors wait for Sill.
| Install | What happens on a page view |
|---|---|
| Cloudflare Worker | Checks your block list and protected paths from a copy it already holds in memory, with no call to Sill, then passes the request to your site. Rules are refreshed in the background after a response has gone out. Images, stylesheets, scripts and fonts go straight to your site. |
| WordPress plugin | Reads the rules it saved earlier from your database and makes no call to Sill while the page is built. Rules are refreshed after the page has been sent to the visitor. |
| Script tag | Starts only after your page has finished loading, runs when the browser is idle, and sends one small report. It never delays your page from appearing or from finishing loading. |
| Shopify app | Shopify loads the script after your store page has finished loading. Nothing runs on checkout pages. |
The script adds no layout shift: the only things it adds to your page are a few <link> tags in the <head>, which take up no space.
What happens if Sill is down?
Section titled “What happens if Sill is down?”Your site keeps working. What you lose while Sill is unreachable is Sill itself: visits are not recorded and agents cannot reach your Sill-hosted endpoints.
- Cloudflare Worker: keeps using the rules it already has and serves your site normally. If a Sill file such as
/.well-known/agent-card.jsoncannot be fetched from Sill quickly, the Worker passes the request to your site instead, and stops asking Sill for 30 seconds so later requests do not wait either. - WordPress plugin: keeps using the rules and files it saved earlier. If it has never saved a file, the request goes to WordPress as if the plugin were not installed.
- Script tag: if the script cannot be downloaded, nothing happens: it is requested only after your page has loaded, so your page and anything you run when it loads are not held up.
Can Sill make my site unreachable?
Section titled “Can Sill make my site unreachable?”Sill is designed so that it cannot.
- An error inside the Worker: the Worker tells Cloudflare to send the request straight to your site if it fails, so a visitor sees your page, not an error.
- Cloudflare’s daily Worker limit: on Cloudflare’s free plan, Workers have a daily request limit. When Sill sets up the Worker, it asks Cloudflare to send requests straight to your site once that limit is reached, instead of showing an error page. The Worker also stays out of your static files (images, scripts, styles and fonts), which on most sites is the bulk of the traffic, so the limit is rarely reached in the first place.
- A bad update to your rules: the Worker, the plugin and Sill’s servers all refuse any rule that would block your home page, cart, checkout, account pages, product and collection pages, search, WordPress admin or login,
robots.txt,sitemap.xmlor your icon. A rule like that is dropped, and the rest of your site keeps working. - Two copies of the plugin: if the plugin ends up installed twice, for example after a site migration, only the first copy runs.
Could Sill block my real customers?
Section titled “Could Sill block my real customers?”Only if you turn blocking on, and then only for what you chose.
- Attack paths start in watch-only mode. Sill records the requests it would refuse and refuses nothing until you switch on blocking.
- The paths Sill refuses are files no shopper ever asks for, such as
/wp-config.phpor/.env. Page addresses that only contain a similar word, such as/blog/dockerfileor/wp-configurator, are never refused. - On a site with only the WordPress plugin, someone logged in to WordPress is never refused.
- Blocked addresses are the ones you or your auto-block chose. Sill refuses blocks that cover very wide address ranges, and a temporary block stops applying when it expires even if the Worker has not heard from Sill since.
Does the WordPress plugin slow down WordPress or wp-admin?
Section titled “Does the WordPress plugin slow down WordPress or wp-admin?”No. On a normal page view the plugin reads one saved setting from your database and writes nothing. With a persistent object cache, such as Redis, it reads nothing from the database. It does not change your pages’ cache headers, sets no cookies and does not buffer your page, so page caches such as WP Rocket, LiteSpeed Cache, W3 Total Cache and Cloudflare APO keep working.
The plugin refreshes its rules from Sill about every 10 minutes, after a page has been sent, and saves them only when they have changed. In wp-admin it makes no calls to Sill.
Does Sill affect caching?
Section titled “Does Sill affect caching?”No. The Worker does not change how Cloudflare caches your pages, and the plugin does not change WordPress caching. The script tag does not set cookies, so it cannot make a page cache skip a page.
What happens if I install the Cloudflare Worker, the WordPress plugin and the script tag?
Section titled “What happens if I install the Cloudflare Worker, the WordPress plugin and the script tag?”All three can stay installed. They detect each other, and each visit is counted once. The Worker runs first, at Cloudflare, before the request reaches your server. Anything it answers never reaches WordPress.
A person opening a page
- Worker: checks the request against your blocked addresses and protected paths, from memory, and passes it to WordPress.
- Plugin: runs its own protected-path check and adds the discovery links and a small loader for the script to the page. It does not report visits from ordinary browsers.
- Worker: sees the plugin’s links and loader on the way back and does not add its own.
- Browser: shows the page. After the page has loaded, the Sill script loads and sends one report, however many copies of the snippet are on the page.
An agent or crawler opening a page
The Worker reports the request to Sill in the background, and the plugin reports it again after WordPress has sent the page. Sill recognises the two reports as the same request and records it once. The script tag does not run, because these clients do not run JavaScript.
Sill’s files on your domain
| Address | Who answers |
|---|---|
/.well-known/agent-card.json, /.well-known/ai-catalog.json, /ai-catalog.json, /.well-known/ucp | The Worker, from Sill. If Sill does not answer quickly, the request goes to WordPress, where the plugin serves its saved copy. |
/.well-known/sill-proof.txt, /.well-known/mcp/server-card.json, /.well-known/api-catalog | The Worker, directly. |
/llms.txt, /agent | Your own page, if your site has one. Otherwise the plugin’s saved copy, or the Worker’s copy from Sill. |
/robots.txt, /sitemap.xml and every other address | Your site. |
A blocked address or a protected path, with blocking on
The Worker refuses it (403 for a blocked address, 404 for a protected path) and the request never reaches WordPress. In watch-only mode the request goes through and is recorded once.
A login or form submission
The Worker checks only your blocked addresses and protected paths, then forwards the request without reading it. Sill never reads or stores what was submitted.
Should I remove one?
You don’t need to. If your site is behind Cloudflare, the Worker alone covers everything the plugin does. Keeping the plugin as well means your discovery files are still served if the Worker is ever removed. The pasted script tag adds nothing when the Worker or plugin is installed, so you can remove it, but leaving it in place is harmless. See What each install covers.
Does Sill replace pages I already have?
Section titled “Does Sill replace pages I already have?”No. If your site already has its own /agent page or /llms.txt, visitors and agents get yours. The Worker serves Sill’s version only when your site answers “not found” at that address, and the WordPress plugin steps aside when you have a published page or post with the address /agent.
How do I switch Sill off quickly?
Section titled “How do I switch Sill off quickly?”Each install can be removed on its own, and removing it returns your site to exactly how it was.
- Cloudflare Worker: in the Cloudflare dashboard, open Workers & Pages, select the Worker whose name starts with
sill-, and remove its routes under Settings → Domains & Routes, or delete the Worker. Sill never deletes anything from your Cloudflare account itself. - WordPress plugin: deactivate Sill Agent Readiness under Plugins. Deleting it removes everything it saved.
- Script tag: remove the snippet from your layout.
How do I get these protections?
Section titled “How do I get these protections?”They are in Worker and plugin version 1.18 and newer.
- Worker deployed with a token: when a newer Worker is available, the Cloudflare card under Settings → Install shows UPDATE AVAILABLE. Click Redeploy. Your token and settings stay the same.
- Worker installed by hand, or the plugin: download it again from Settings → Install and replace the old one. See Update the Worker and Update the plugin.