Monitoring (after deploy)

What monitoring does

• Runs scheduled scans of your production base URL.
• Creates incidents when something changes (new issues, spikes, drift).
• Builds a drift timeline so you can see when a template changed and what it affected.

Add your first site

You can set this up in the dashboard, or via API.

Option A: Dashboard

• Go to /app.
• Use Create project and enter your production base URL.
• Choose a schedule (nightly recommended) and save.

Option B: API

curl -sS -X POST "https://api.seodiff.io/api/v1/sites" \
  -H "Authorization: Bearer $SEODIFF_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "base_url": "https://example.com",
    "enabled": true,
    "schedule": "nightly",
    "config": {}
  }'

Incidents

Incidents are diff-driven. They’re designed to answer: what changed, where, and how bad.

curl -sS "https://api.seodiff.io/api/v1/incidents" \
  -H "Authorization: Bearer $SEODIFF_API_KEY"

Template drift timeline

The timeline shows how a template evolves over time (issue rate, score changes, drift events).

• Dashboard: open your project in /app, then click Template Drift (or open /app/timeline directly).
• API: list templates for a base URL, then query the timeline for one template key.

curl -sS "https://api.seodiff.io/api/v1/templates?base_url=https%3A%2F%2Fexample.com" \
      -H "Authorization: Bearer $SEODIFF_API_KEY"

curl -sS "https://api.seodiff.io/api/v1/timeline?base_url=https%3A%2F%2Fexample.com&template=%2Fproduct%2F*" \
      -H "Authorization: Bearer $SEODIFF_API_KEY"

Common monitoring issues

• No incidents yet: run at least two scans before expecting diff-driven incidents.
• Unexpected spikes: verify target pages are publicly reachable and not serving temporary error pages.
• Missing timeline points: ensure you query the same base_url. For the template identifier, use the dashboard autocomplete on /app/timeline or call GET /api/v1/templates?base_url=... to get the exact keys.

Planned improvements (not available yet)

• Alerts: email / Slack / webhooks.
• Long-lived share links: share reports and incidents with a single link, without requiring recipients to sign in.

Related

• API reference
• CI/CD guide
• Concepts