Skip to content
Check a site

Catch what breaks
before your users do.

Audit your website before launch.
Monitor what changes after.

Check a siteSee how it works

No account required for a one-off audit.

  1. All projects
  2. example.com
  3. Scan #14
Example scan

Launch audit of example.com

Run scan
  • Overview
  • Findings4
  • Pages10
  • History14
  • Last scan 2 hrs ago
Scan complete10 pages inspected, two links deep
  1. Fetch
  2. Crawl
  3. Check
  4. Compare
92/ 100

Launch readiness

Looking good. A few things to check.

  • 3 warnings
  • 1 regression
  • 38 passed

Findings Compared with previous scan

New regression

/contact returns 404

Warning

Content-Security-Policy header not detected

Resolved

Google Analytics restored

Pass

HTTPS configured correctly

A sample of what Afterward checks

  • HTTPStechnical.https
  • Redirectstechnical.redirect-chain
  • robots.txtdiscovery.robots-txt
  • Sitemapdiscovery.sitemap
  • Canonicalsseo.canonical-valid
  • Open Graphseo.social-metadata
  • Broken linkslinks.broken-internal
  • Alt textimages.alt-text
  • Formsforms.secure-submission
  • Analyticsanalytics.detected
  • HSTSsecurity.hsts
  • CSPsecurity.csp

50+ deterministic checks Same site responses, same findings, same score

Shipping isn’t the finish line. A content edit breaks a link, a redesign drops analytics, a staging robots.txt reaches production; so Afterward keeps watching.

  • 50+deterministic checks
  • 10–25pages per scan, two links deep
  • $0for a complete one-off audit
  • Dailymonitoring on the Agency plan

QA that remembers your site

Afterward saves a known-good baseline, then compares every scheduled scan against it. You see what changed, with the evidence to act on it.

Coming soon Monitoring arrives with the Pro and Agency plans.

From launch day to every deploy after. The QA pass that runs itself.

Scan before launch, save the result as your baseline, and let scheduled checks compare every future scan against it. When something regresses, you get a focused alert instead of a wall of repeated findings.

Join the waitlist
scaninspecting example.com
  • 10 pages
  • 41 passed
  • 2 warnings
  1. GET /200 · text/html
  2. GET /pricing200 · text/html
  3. GET /robots.txt200 · text/plain
  4. seo.homepage-indexableHomepage can be indexed
  5. discovery.sitemapXML sitemap found
  6. analytics.detectedAnalytics detected
  7. security.cspContent-Security-Policy header not detected
  8. score 96 / 100 · same responses, same findings

Example output

One launch checklist, from first deploy to every deploy after.

Start with a free audit. Add a baseline, scheduled checks, and alerts when you want Afterward to keep watching.

audit

Ship with fewer loose ends

Run a complete one-off audit before launch. Get a launch-readiness score and prioritized findings, each with the evidence Afterward observed.

  • Availability & status codes
  • HTTPS & redirects
  • Titles & descriptions
  • Canonicals
  • Open Graph
  • Sitemap & robots.txt
  • Broken links
  • Image alt text
  • Forms
  • Analytics detection
  • Security headers
Check a site
  1. All projects
  2. example.com
  3. Scan #14
Example scan

Launch audit of example.com

Run scan
  • Overview
  • Findings4
  • Pages10
  • History14
  • Last scan 2 hrs ago
Scan complete10 pages inspected, two links deep
  1. Fetch
  2. Crawl
  3. Check
  4. Compare
92/ 100

Launch readiness

Looking good. A few things to check.

  • 3 warnings
  • 1 regression
  • 38 passed

Findings Compared with previous scan

New regression

/contact returns 404

Warning

Content-Security-Policy header not detected

Resolved

Google Analytics restored

Pass

HTTPS configured correctly

monitorComing soon

Your site passed launch day. Make sure it stays that way.

Afterward remembers your baseline and detects what changes after you ship.

  • New
  • Resolved
  • Persisting
  • Severity changed
  • Baselines
  • Regression detection
  • Scan history
  • Email alerts
  • Weekly checks on Pro
  • Daily checks on Agency
Join the waitlist
  1. All projects
  2. example.com
  3. Changes
Example comparison

Changes since the last scan

Daily monitoring
  • Changes5
  • Findings5
  • History30
  • Checked Tue 09:00
Mon 09:0096
Tue 09:0076
−20 points
New

robots.txt blocks search engines from the entire site

Critical · User-agent: * Disallow: /
New

1 broken internal link

Warning · /pricing now returns 404
Severity changed

HSTS max-age is short

Info → Warning
Persisting

Content-Security-Policy header not detected

Warning · present since the baseline
Resolved

Pages without a canonical tag

A canonical tag is now present on /about
A focused alert. The changes that matter.New critical findings, warnings, and meaningful score drops.
agencyComing soon

One view for every client site

A simple QA layer across your client websites, without manually checking every site after every edit.

  • 50 monitored sites
  • Client & project organization
  • Daily or weekly checks
  • Regression alerts
  • Client-ready reports Planned
Join the waitlist
  1. Workspace
  2. Clients
Example workspace

Your sites, at a glance.

4 sites · 2 projects
  • All sites4
  • Regressions2
  • Projects2
  • Single-owner workspace
Illustrative client site launch-readiness results
Client siteScoreLatest statusChecks
Acme Manufacturing96HealthyDaily
Jones Dental713 regressionsDaily
Beacon Coffee881 regressionWeekly
Smith Law—Site unreachableDaily
mcp

Ask for an audit in conversation

Run Afterward from ChatGPT or another MCP-compatible client. Afterward inspects the site; your assistant helps you understand what to fix.

  • ChatGPT
  • Claude
  • Codex
  • Any MCP client
  • scan_website
  • Account tools Coming soon
Connect your MCP client
  1. MCP client
  2. New conversation
Illustrative response
You

Check example.com before I launch it.

scan_websiteexample.com · 10 pagesComplete
Assistantusing Afterward91 / 100

I found 2 warnings and 1 informational issue.

  1. /pricing contains a broken internal link.
  2. No Content-Security-Policy header was detected.
  3. No common analytics implementation was detected.

Prioritized findings. Specific evidence. A useful next step.

Example findings

GET /pricing
HTTP/2 404
content-type: text/html

Linked from
  /
  /features
  /blog/launch-week
Observed evidence

Example finding links.broken-internal

“1 broken internal link”

/pricing returned HTTP 404 in this scan. It returned 200 in the previous one.

  • 404Current status
  • 200Previous scan
  • 3Pages linking to it

Small changes can break a launch. Our job? Catch them first.

  • Catch broken links
  • Stop staging robots.txt
  • Keep analytics running
  • Verify HTTPS & HSTS
  • Fix missing metadata
  • Spot insecure forms

Afterward for teams that ship websites

Built for the people who ship websites.

Before every launch

For developers

A launch checklist that runs itself, straight from your MCP client.

I’m a developer
  • Complete one-off audits, no account needed
  • Stable check IDs and observed evidence
  • Run it from ChatGPT or another MCP client
Across every client site

For agencies

One view of every client site, with an alert when one regresses.

I run an agency
  • Up to 50 monitored sites
  • Daily or weekly checks
  • Client and project organization
After every edit

For site owners

Know when a routine update breaks something your visitors notice.

I own a website
  • Weekly monitoring on Pro
  • Email alerts for new findings
  • Scan history to see what changed

MCP

Runs inside the tools you already use

Ask for an audit in ChatGPT, Codex, or another MCP-compatible client. Afterward inspects the site; your assistant explains what to fix.

Connect your MCP client
  • ChatGPT
  • Codex
  • Any MCP client
  • Bounded crawler
  • Afterward MCP
  • 50+ checks
  • Your public website
  • Scan history
  • Email alerts

A useful audit is always free. Pay for the watchful eye.

One-off checks are free. Paid plans add persistence, monitoring, and a history of what changed.

Free audits are available now. Pro and Agency are coming soon.

Free

For one-off checks.

$0forever for one-off audits

Check a site
  • One-off audits
  • Complete results
  • No account required

A complete result. No account needed.

Pro

Coming soon

For developers and site owners.

$19/ month

Join the waitlist
  • 10 monitored websites
  • Weekly monitoring
  • Regression detection
  • Scan history
  • Email alerts
  • 100 manual scans / month

A baseline today. Visibility tomorrow.

Agency

Coming soon

For people managing client websites.

$79/ month

Join the waitlist
  • 50 monitored websites
  • Daily or weekly monitoring
  • Client organization
  • Regression alerts
  • Scan history
  • 500 manual scans / month

Every client, in one workspace.

Be first to get monitoring.

Join the waitlist for Pro and Agency. We’ll email you when they open, and only about that.

Email us to join the waitlist

Planned prices shown; they may change before launch. Your email is kept by our email provider, Kit. See our privacy policy.

Clear scope. No surprises.

A few useful answers about what Afterward does, and what it deliberately doesn’t.

Is Afterward a security scanner?

Afterward checks common website configuration and security-hardening issues. It is not a penetration-testing tool and does not guarantee that a site is secure.

Does Afterward replace Lighthouse?

No. Afterward focuses on launch readiness and regressions across technical configuration, metadata, links, forms, analytics, and related checks. It complements performance tools and full accessibility or SEO audits.

Do I need an account?

No. A complete one-off audit through an MCP client needs no account. Saved sites, scan history, and scheduled monitoring are coming with the Pro and Agency plans.

Will Afterward crawl my entire site?

Afterward uses a conservative crawl strategy: 10 pages by default, up to 25 pages, and a maximum depth of two links from the homepage. It is designed for focused launch QA rather than exhaustive crawling.

Can Afterward monitor client sites?

That is what the Agency plan is for. It is coming soon, with up to 50 saved sites, daily or weekly monitoring, and client and project organization. Join the waitlist to hear when it opens.

How many free audits can I run?

Free audits are rate limited, currently to 5 every 10 minutes, so the service stays fast for everyone. If you reach the limit, your assistant will say when you can scan again.

Does Afterward execute JavaScript?

Current scans inspect server-delivered HTML. Content that only appears after JavaScript runs may not be visible to the scanner. A rendered-browser scanning mode is a future possibility.

Check your site before
someone else does.

Run an audit and catch the obvious problems before they reach your users.

Check a siteView pricing

No account required Full one-off audit

Every scan covers
  • HTTPS
  • robots.txt
  • Sitemap
  • Canonicals
  • Open Graph
  • HSTS