---
name: amt-website-qa
description: Inspect a public website for availability, redirects, broken links, metadata, social previews, headers, TLS, email security, content, and change-monitoring gaps with Agent Media Tools. Use for launch checks, recurring site QA, agency audits, SEO hygiene, or diagnosing a public page.
---

# Website QA

Produce an evidence-based website report. Check only public URLs the user is authorized to inspect; never probe private networks or attempt exploitation.

## Establish scope

Ask for the starting URL and whether the goal is a one-page check, launch review, small-site crawl, or recurring monitor. Confirm a crawl limit before expanding beyond the starting page.

## Run the workflow

Check `GET /api/usage` or `GET /api/agent/usage` before running a multi-check audit. A full audit can exceed anonymous capacity; ask the user to authenticate or agree to a smaller scope instead of silently skipping checks.

1. Confirm reachability and redirects with Batch URL Analyzer or `batch-url-check`.
2. Inspect one representative page with:
   - HTTP Headers Inspector (`http-headers`)
   - SSL Certificate Checker (`ssl-check`)
   - Open Graph Preview (`og-preview`)
   - Page Link Analyzer (`link-analyzer`)
3. Use Broken Link Checker for bounded link validation. Do not interpret blocked bot traffic as proof a site is down; record the observed status.
4. Use Sitemap Generator only within the agreed page limit.
5. Use MCP `browse_web` or REST `POST /api/browser/browse` when the report needs checkable page evidence. Set `allowed_domains` to the intended site.
6. Use Structured Scrape only for specific fields such as title, price, canonical URL, or headings.
7. If ongoing checks are wanted, propose Website Watchdog after the one-time audit. Do not create a watch without confirmation of URL and notification destination.

If AgentBrowse reports that its runtime is unavailable, continue with the deterministic site checks that succeeded and list evidence browsing as unavailable. Never replace a missing result with an assumption.

Browser toolbox: https://agentmediatools.com/app
Monitoring workflow: https://agentmediatools.com/workflows/website-monitoring-alerts

## Grade findings

Classify each finding as `critical`, `important`, or `improvement`. Include the checked URL, observed evidence, why it matters, and the smallest practical fix. Separate verified failures from warnings and unavailable checks.

## Return

Report scope and timestamp, checks completed, prioritized findings, passed checks, limitations, and recommended next actions. Never present a security-header score as a penetration test or guarantee of security.
