AgentAction
← All agent recipes

Engineering / Read only

Monitor website availability and technical SEO

Powered byAgentAction recurring workflows

Recipe maintained by AgentActionVersion 1.0.0Evidence: synthetic fixtures

The job

Perform bounded availability checks and daily technical SEO comparisons; preserve evidence, report new problems and verify recovery.

Example result

Illustrative output using synthetic data.

Example (synthetic): page unavailable after two consecutive checks; one critical finding opened; notification queued. Recovery resolves the finding after a successful check.

Connections you’ll need

This recipe uses built-in public web checks. Configure page targets and workspace email notifications; no MCP account is required.

Make it work in your environment

Page URL
One public HTTPS page per instance; create additional instances for other pages or sites.

Example: https://example.com/

Expected content
Optional text required in the returned HTML.

Example: Welcome

Runtime requirements

  • Use the recurring-agent runtime with persistent state and an owner-approved schedule.
  • Configure workspace email recipients for notifications.
  • Same-origin redirects are permitted; explicitly approve additional origins before following them.

Operating boundaries

  • Public HTTPS reads of configured origins only; no credentials, writes or automatic remediation.
  • At most three redirects and 512 KiB HTML; no JavaScript rendering or full-site crawl.
  • Two failures from the same location confirm an incident; independent geographic confirmation is not included.
  • SEO checks cover title, description, canonical and noindex; no ranking/indexing claims without Search Console.
  • Email provider acceptance is not proof of inbox receipt; retries may duplicate delivery.

What a completed job requires

  • Configured checks completed
  • Observation evidence preserved
  • Meaningful findings routed under workspace policy

Inspect the test cases

Synthetic tests exercise outage confirmation, deduplication, SEO regression, recovery, scheduling and email routing. Live coverage depends on configured targets and email service.

Successful check discovers an outageExpected: met
{
  "checks_complete": true,
  "evidence_saved": true,
  "routing_applied": true
}

Expected evaluation: met

  • Configured checks completed: expects true
  • Observation evidence preserved: expects true
  • Meaningful findings routed under workspace policy: expects true
Incomplete probe is not successful monitoringExpected: not met
{
  "checks_complete": false,
  "evidence_saved": true,
  "routing_applied": true
}

Expected evaluation: not_met

  • Configured checks completed: expects true
  • Observation evidence preserved: expects true
  • Meaningful findings routed under workspace policy: expects true
No claim of success without evidenceExpected: indeterminate
{
  "checks_complete": true
}

Expected evaluation: indeterminate

  • Configured checks completed: expects true
  • Observation evidence preserved: expects true
  • Meaningful findings routed under workspace policy: expects true

Validate with your agent

Run these procedures in your sandbox. They are a test plan, not completed live-agent tests.

Outage and recovery

Use a controlled target that returns 503 twice, then 200.

Expected: One finding and alert, followed by a recovery event.

SEO regression

After the baseline, introduce noindex and run the next daily SEO check.

Expected: A critical finding references the inspected URL and indexing directive.

The agent’s instructions

  1. Configure the page, expected content, allowed redirect origins and check interval.
  2. Run a baseline and review saved evidence before enabling automatic reads.
  3. Use shared findings to deduplicate problems, acknowledge attention and verify recovery.
  4. Inherit workspace email settings or choose a permitted subset of recipients.
  5. Treat incomplete or stale evidence as unknown; keep execution success distinct from target health.

Follow it into operation

Open Recurring agents to inspect check history, saved snapshots, findings and notification delivery. These deterministic observations are operational evidence; they are not signed gateway Jobs or independent SEO rankings.

Downloading a recipe does not connect accounts, deploy an agent, install controls, or configure Evals.