The Updates feed on each website's detail page is the log of everything we've done with your site — changes, fixes, deployments, maintenance entries, status events. The left column on Websites → click a website is the live view.

What appears in the feed

Each entry has a short title, a timestamp, and a longer description if there's more context. Common entry types:

• Deployments — when we've pushed a new version of the site, or applied a content update you asked for.
• Maintenance entries — scheduled tasks we've run (updates, backups, security checks). See Maintenance for what's covered by your plan.
• Incident updates — when the site has had an issue, we post the timeline here as we work through it.
• Configuration changes — DNS, SSL renewals, server tweaks.
• Notes from us — anything we want on the record (e.g. "removed cached files for redeploy", "confirmed contact form working after report").

Reading the feed

Entries are newest first. Each is independently dated — you can scroll back as far as the site's history goes. There's no automatic archival; everything stays in the feed indefinitely.

If you're trying to find a specific change, the simplest path is to scroll to roughly when you remember it happening. We don't currently expose a search inside the feed.

What's not in the feed

The Updates feed is the what we did log. A few things that look log-shaped but live elsewhere:

• Visitor analytics (sessions, pages viewed, traffic sources). That data lives in Google Analytics if it's linked to your site (visible in the Information card on the website detail page). We don't duplicate Analytics inside the portal — the Google interface is better suited to it.
• Server access logs (raw HTTP requests). These exist on the hosting side but aren't exposed in the customer portal. If you need them — for a security incident, a forensic question, debugging a specific request — ask us and we'll extract the relevant slice.
• Search-engine performance. That's the SEO reports — separate from the day-to-day updates feed.

Why we keep this kind of log

Two reasons:

• For you — so you can see what's happening to your site without having to ask. If you're trying to remember when we did X, or whether we did Y last month, the feed is the record.
• For us — it's the project history we work from when diagnosing issues. When a problem shows up, the first thing we look at is what changed recently. The feed is the source of truth.

If you ever spot something that's gone live without appearing in the feed, tell us — we may have missed logging it.