The Activity page (in the sidebar under History) is the project’s timeline: everything that happened, in order, on one surface. Where Alerts interrupts you and Issues tracks the work, Activity answers “what happened around then?”

What lands on the timeline

Events are grouped by date and tagged by kind:

Scans and verification. Every scan run and every fix verification.
Changes. Deploys and releases (from the GitHub integration) and dependency update refreshes.
Monitoring. Uptime incidents, traffic anomalies from analytics, and search-performance events from Search Console.

Connected integrations feed their events automatically; without integrations, the timeline still carries your scans, verifications, and update activity.

Why a timeline

Correlation by eyeball is underrated. A score drop next to a deploy, a traffic dip next to an uptime incident, an issue’s first appearance right after a dependency bump - the timeline puts causes and effects on the same axis. On Core and above, SiteCMD also draws those correlations for you (a finding gets tied to the deploy it followed), but the raw sequence is often all you need.

Filters and export

Filter pills narrow the feed to any combination of the three groups. Export gives you the filtered feed as CSV (for spreadsheets) or JSON (for scripts) - useful for sharing an incident window with someone who doesn’t run SiteCMD, or feeding a postmortem.

Like everything else, the timeline is stored in the local database and the exports are written where you choose. Nothing about your activity leaves the machine.