Change Intelligence

Not just what broke.
What changed
before it broke.

Every detection across uptime, SEO, security, performance, integrity, and content is logged to a shared timeline - automatically, continuously, and in the order it happened. When something goes wrong, you're not starting from scratch. You're looking back at a record.

Your team can add their own events alongside the automated ones - a deployment, a content update, a campaign launch. So the timeline reflects everything that happened to your site, not just what the monitors caught.

What flows into the timeline

Uptime

Downtime incidents, response times, and recovery events.

SEO

Broken links, missing tags, structural regressions, and AI readiness shifts.

Security

Header changes, new scripts, vulnerability detections, and redirect failures.

Performance

PageSpeed score changes, LCP regressions, and Core Web Vital shifts.

Integrity

SSL expiry warnings, domain changes, and broken asset detections.

Content

Body copy changes, keyword drift, H1 shifts, and new external dependencies.

Team Notes Manual

Deployments, updates, campaign launches - anything your team wants on the record.

Where Change Intelligence Earns Its Keep

The conversations it makes possible.

The real value of Change Intelligence is not just in catching problems - it is in having the evidence to understand them.

๐Ÿ‘ฅ For teams

When multiple people edit the same pages

Content teams, developers, and SEOs often work on the same pages without visibility. Change Intelligence creates a shared record - so the conversation starts with evidence rather than assumptions.

Instead of โ€œDid anyone change the homepage?โ€ you get a timestamped log of exactly what changed, when, and how significantly.

๐Ÿข For agencies

When a client edits their own site

A well-intentioned edit by the client - a new paragraph or headline - can undermine months of work. Change Intelligence catches this before it becomes a problem to explain during check-ins.

The next monthly check-in includes a clear record of every change made since the last one - and which ones are worth discussing.

๐Ÿ”’ For security

When something is injected without authorisation

Content injection appears as a new external dependency or an unexpected change. Dependency fingerprinting catches both immediately, rather than waiting for a monthly security scan.

New third-party resource detected on checkout page. Unauthorised tag manager entry identified and removed before any data was exposed.

๐Ÿ“Š For SEO

When you need to explain a traffic change

The hardest part of SEO reporting is explaining why. We give you a complete record of everything that changed on your monitored pages in the period immediately before a traffic shift.

Traffic dropped 18%. Change log shows an H1 change on Oct 3rd and a rewrite on Oct 11th. Investigation starts there with concrete data.

Change Intelligence Timeline โ€” How it works

Something changed.
Now you can prove it.

SiteVitals keeps a continuous, dated record of everything it detects regressions, recoveries, content shifts, security changes, so you always have a trail to follow. Your team can add to it too. Deployed something? Log it. Client made changes? Note it.

sitevitals.co.uk/report/demo

Click to explore the live timeline

Scroll inside to see more events

API Access

Give your AI agent
the full picture.

The SiteVitals health endpoint returns everything an AI agent needs to diagnose a site issue in a single request - current scores across all six monitors, a score history timeline, recent drift events, uptime incidents, security failures, content change index, and a monthly summary.

Point an AI assistant at GET /api/v1/sites/{page}/health and it has the context to answer questions that would otherwise take minutes of manual investigation.

โ†’ "Why did our SEO score drop last week?"
โ†’ "Are there any unresolved security issues right now?"
โ†’ "What changed on the site before the traffic dropped?"
โ†’ "How has performance trended over the last 30 days?"
โ†’ "Is the SSL certificate about to expire?"
GET /api/v1/sites/4/health
{
  "status": "warning",
  "score": 87,
  "summary": "Site is online. CRITICAL: 2 high-priority issues...",
  "vitals": {
    "is_up": true,
    "ssl": "valid_35days",
    "perf_score": 61,
    "seo_score": 80,
    "security_score": 93
  },
  "recent_drifts": [
    {
      "type": "uptime",
      "severity": "critical",
      "resolved": false
    }
  ],
  "score_history": [ ... 30 days ],
  "monthly_summary": {
    "uptime_avg": 99.93,
    "downtime_incidents": 5,
    "seo_avg": 69.57
  },
  "improvements": [ ... action items ]
}
Current scores - all 6 monitors
Score history
Recent drift events
Uptime incident log
Security failure detail
Content change index
Monthly summary
Improvement suggestions
Data freshness indicators
Questions

Things people often ask us.

If something isn't covered here, we're genuinely happy to answer it. We're a real team and we actually respond.

What kinds of events appear on the timeline?

+

Everything SiteVitals detects is logged automatically - uptime incidents, SEO regressions and improvements, security changes, performance shifts, integrity alerts, and content changes. Your team can also add manual events like deployments, content updates, or campaign launches alongside the automated ones.

Can my whole team see the timeline?

+

Yes. The timeline is shared across everyone with access to a site. Team members can view all automated detections and add their own annotations, so the record reflects both what the monitors caught and what the team knows happened.

Can I share the timeline with people outside my account?

+

Yes. Each site has a shareable public report link that gives read-only access to the timeline and health data - no login required. Useful for sharing a site's current status and change history with a developer, a client, or a stakeholder who needs visibility without needing a SiteVitals account.

How far back does the timeline go?

+

History retention depends on your plan - 90 days on Starter, 180 days on Marketer, and 365 days on Agency. The longer it runs, the more useful it becomes for correlating site changes with performance shifts.

Can I use the timeline data in my own tools?

+

Yes. The health API endpoint returns recent drift events, score history, and the full site health context in a single request. This makes it straightforward to feed timeline data into AI assistants, dashboards, or reporting workflows.

Does the timeline cover all my monitored sites?

+

Each site has its own timeline. You can view events per site through the dashboard, or use the global timeline view to see activity across all your monitored pages in one place.