What Rollouts checks every day while you work

It's 2 a.m. and someone on your team pushes a homepage edit that quietly drops the meta description. Nobody notices for a week. That's the kind of breakage a website platform should catch, and it's a fair question to ask of any tool that says it works while you're busy: what, exactly, runs when nobody is logged in?

For Rollouts, the answer is one job. Once a day it reads your live homepage, your sitemap and your llms.txt file, compares them with the last check, and writes what changed to your site's feed. Everything else, from building pages to applying fixes to publishing, waits for you to click. This post walks through what that daily check sees, what it reports, and which parts of Rollouts are still rolling out.

The one job that runs without you

Every day at 06:00 UTC, Rollouts revisits every site that has had at least one scan, on every plan, Free included. It doesn't wait for you to log in, and it doesn't need a browser tab open. It fetches the homepage the same way the scanner does, reads the sitemap, and looks for llms.txt, the plain-text file that tells AI crawlers what your site is about.

That's the whole list of what runs unattended: one read-only pass, once a day. A site that happens to be in the middle of a scan is skipped, so the check never trips over fresher results. It doesn't rewrite copy, change your title tags, or publish anything.

What the daily check reads

On the homepage, the check records four things: the title tag, the meta description, a fingerprint of the visible text, and how long the page took to respond. The title and description are what search engines and AI assistants show when they mention you. The visible text is everything a visitor reads, reduced to a fingerprint so even a one-word change registers.

From the sitemap it takes one number: how many URLs it lists. A sitemap that suddenly shrinks usually means pages were removed or something in the build broke, and one that grows tells you new pages are discoverable. From llms.txt it checks only whether a real file is there, not an HTML error page dressed up as one.

What lands in your feed

When something moved, the feed gets a plain entry: the homepage title changed, with the old and new versions side by side; the meta description changed; the visible text differs from the last check; the sitemap grew or shrank, with both counts; llms.txt appeared or disappeared.

Two entries are flagged as serious. If the homepage answers with an error code, the feed says your site may be down. If the check can't reach the domain at all, because the request timed out or was refused, it says so. On a quiet day you get a single line saying no changes were detected, along with how fast the homepage responded.

The feed is where these live. Rollouts doesn't email or text you about them today, so the habit that makes the check useful is opening the feed when you sit down to work, the same way you'd glance at an inbox.

Why fixes wait for your click

The check finds; it doesn't fix. That's deliberate. A tool that rewrote your title tag every time it disagreed with you would undo changes you made on purpose, and a site that edits itself is a site nobody can vouch for. So in Rollouts, building, fixing and publishing all start with a click, and nothing goes live until you press publish.

When a feed entry needs action, you run a scan. It takes about a minute and lists every technical SEO and AEO fix the site needs, sorted worst first, so critical issues come before high ones and high before medium. Each fix says why it costs you and exactly what to do, and where one applies, it gives you a snippet to paste.

A rebuild takes under three minutes. You can look over the result before anything changes on the live site, then publish when it's right.

A week with the daily check

Say you run a SaaS landing page and a teammate ships a pricing update on Monday. Tuesday's feed shows the homepage content changed, which you expected, and the meta description changed, which you didn't. You open it, see the old description was replaced by a placeholder, run a scan, fix it in the builder, and publish before lunch.

On Thursday the sitemap shrinks from 64 URLs to 41. That's a bigger deal: whole sections stopped being discoverable. You'd want to know that within a day, not at the end of the quarter when organic traffic has already slid. Friday's entry is a single line saying nothing changed and the homepage answered quickly, which is the entry you want most days.

What's still rolling out

Some of what Rollouts is built to do isn't live yet, and it's worth knowing which parts. Visitor identification, the part that names the companies landing on your pages, belongs to the Grow engine, which is rolling out. So does matching visitors to your ideal customer profile and drafting account-based outreach. The Ads engine, for ad creative, campaigns, attribution and budget, is rolling out too.

A few playbooks wait on those pieces. The Search Console keyword playbook needs a connection that isn't wired up yet, and the two playbooks built on visitor data stay off until visitor identification is switched on. The rest of the playbooks work today, and each one hands you a checklist, a brief, or a page in the builder rather than acting by itself.

Rollouts also doesn't run A/B tests, and there's no public API. If you need either today, pair it with a dedicated tool. What does connect today: signed webhooks when a site is published, a build completes, a scan finishes or a lead comes in, plus Zapier, Make, n8n, Slack and GA4.

Where the daily check fits in your week

The daily check is a smoke alarm, not a contractor. It won't repaint the kitchen, but it will tell you within a day that the homepage changed, the sitemap lost pages, or the site stopped answering. That's the part of website upkeep most teams drop first, because nobody remembers to look until a customer mentions it.

Pair it with a scan whenever you ship something meaningful, and with the fix list when you have an hour to spare. The site stays yours: Rollouts reads it every day, tells you what moved, and leaves every change to you.

Frequently asked questions

Will Rollouts change my live site without asking?

No. The daily check only reads your homepage, sitemap and llms.txt and reports what changed. Building, fixing and publishing start with your click, and nothing goes live until you press publish.

What does the daily check look at?

Your homepage's title, meta description, visible text and response time, the number of URLs in your sitemap, and whether a real llms.txt file exists. It compares each with the last check and writes what changed to your site's feed.

Will Rollouts email me when something changes?

Not today. The daily check writes its findings to your site's feed rather than sending an email or a text, so open the feed when you sit down to work. Serious entries, like the homepage returning an error, carry a higher severity so they stand out.

Can Rollouts tell me which companies visit my site?

Not yet. Naming the companies that land on your pages is part of the Grow engine, which is rolling out. Until it ships, Rollouts' built-in analytics show visits, top pages, referrers and the goals you set.

Does the daily check run on the free plan?

Yes. It runs for every site that has had at least one scan, on every plan, including Free at $0 a month.