Website QA / Before launch. After every change.

Catch what breaks
before your users do.

Audit your website before launch. Get clear findings, the evidence behind them, and a useful next step.

Free one-off audits. No account required.
Works with ChatGPT, Codex, and other MCP clients.

Example audit · illustrative data

01 / Pageexample.com

<nav>
  <a href="/pricing">
    View pricing
  </a>
</nav>

Internal link found on the homepage

02 / Response/pricing

GET https://example.com/pricing

HTTP/2 404
content-type: text/html

Destination returned “not found”

Warninglinks.broken-internal

One broken link. A clear next step.

Update the link on / or restore /pricing, then run another audit.

50+ deterministic checks10–25 pages per scan$0 for a complete one-off auditExplore the scan scope

01 / The workflow

From a public URL to a useful next step.

Afterward inspects your site. Your assistant helps you understand the result. You decide what to fix.

01 / 03
Share your URL
Ask your MCP client to check a public website. No account or script installed on your site.
scan_website → example.com
Start with the site your visitors actually see.
02 / 03
Inspect what shipped
Afterward fetches pages, checks configuration, and verifies links within a bounded crawl.
Fetch → crawl → check
A link on the homepage points to /pricing. The destination returns HTTP 404.
03 / 03
Follow the evidence
Get prioritized findings with affected URLs, observed responses, and a recommendation.
Finding → evidence → next step
Update the link or restore the page, then run another audit to check the response.

Example audit · illustrative data

Page → response → evidence.
Every finding has a reason.

Same site responses, same findings, same score. Scans inspect server-delivered HTML; they do not execute JavaScript.

02 / The product

A closer look at what shipped. And what changes next.

Start with a free audit in your MCP client. Add baselines, monitoring, and client sites in Afterward Cloud.

Illustrative product previews

All projects
example.com
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

Fetch
Crawl
Check
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

Workspace
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 site	Score	Latest status	Checks
Acme Manufacturing	96	Healthy	Daily
Jones Dental	71	3 regressions	Daily
Beacon Coffee	88	1 regression	Weekly
Smith Law	—	Site unreachable	Daily

MCP client
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.

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

Prioritized findings. Specific evidence. A useful next step.

01audit

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

Available now

A complete one-off result. No account, no installation on your site.

URL → findings → evidence

02monitor

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

Start monitoring

Afterward Cloud

A baseline today. A clear view of what changed tomorrow.

Baseline → compare → alert

03agency

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

Explore Agency

Afterward Cloud

Every client site, with the context to know what needs attention.

Clients → projects → sites

04mcp

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

Audit your website with ChatGPT

Available now

You ask. Afterward checks. Your assistant explains.

scan_website({ url: "https://example.com" })

From finding to fix

Don’t just see the issue. See what’s behind it.

Choose an example finding to inspect the response, affected URLs, and recommended next step.

example.com / FindingsInteractive example · no live scan

Warninglinks.broken-internal

1 broken internal link

A link on the homepage points to a page that returned HTTP 404. Visitors following that link reach a missing page.

Observed evidence Example response

GET https://example.com/pricing

HTTP/2 404
content-type: text/html

Linked from: https://example.com/

Affected URLs

https://example.com/
https://example.com/pricing

Recommended next step

Check the /pricing link on the homepage. Update it to the intended destination or restore the missing page. Deploy the change, then run another audit to check the response.

The response was observed during this example scan. It does not establish why the page was missing.

Criticaldiscovery.robots-txt

robots.txt blocks search engines from the entire site

The public robots.txt tells all compliant crawlers not to crawl the site. A staging rule may have reached production.

Observed evidence Example response

GET https://example.com/robots.txt

HTTP/2 200
content-type: text/plain

User-agent: *
Disallow: /

Affected URLs

https://example.com/robots.txt

Recommended next step

Confirm whether this public site should be crawled. If it should, remove the blanket Disallow: / rule for User-agent: *, keeping any intentional path restrictions. Deploy and inspect robots.txt again.

A crawl restriction is not access control. Changing it does not guarantee search indexing or ranking.

Warningseo.meta-description-present

Pages with a missing or empty meta description

The delivered HTML for the about page has no non-empty meta description. Search engines may choose other text for its snippet.

Observed evidence Example response

GET https://example.com/about

HTTP/2 200
content-type: text/html

<title>About — Example</title>
<meta name="description">  (not detected)

Affected URLs

https://example.com/about

Recommended next step

Add a concise, page-specific meta description to the server-delivered HTML for /about. Describe the actual page content, deploy, and run another audit to check that the tag is present.

Afterward checks delivered markup. A description is not a promise of a particular search snippet or ranking.

Warningsecurity.hsts

Strict-Transport-Security header not detected

The site responded over HTTPS, but the response did not include a policy telling browsers to require HTTPS on later visits.

Observed evidence Example response

GET https://example.com/

HTTP/2 200
content-type: text/html
x-content-type-options: nosniff

strict-transport-security  (absent)

Affected URLs

https://example.com/

Recommended next step

Review HTTPS support across the site before adding Strict-Transport-Security at the server or hosting layer. Choose a policy appropriate to the deployment; only include subdomains after checking them. Verify the response header after deployment.

This is an observed configuration gap, not a finding that the site has been compromised or is insecure.

Inside your workflow

You ask.
Afterward checks.
Your assistant explains.

Go from a public URL to a useful answer in the tools you already use.

Illustrative conversation · example data.
No audit is running on this page.

Connect your MCP client

You Request
Check example.com before I launch it.
02
Assistant → Afterward Tool call
```
scan_website({
  "url": "https://example.com",
  "maxPages": 10
})
```
Afterward inspects the public website.
Afterward → Assistant Result excerpt
Warninglinks.broken-internal
1 broken internal link
Linked from
/
Destination
/pricing
Observed response
HTTP 404
Assistant Explanation
Start with the pricing link.
Your homepage links to /pricing, which returned 404 in this scan. Visitors following that link reach a missing page.
Update the link or restore the page. After deploying the change, ask me to run another audit and check the response.
Explore the finding and evidence

03 / After launch

Shipping isn’t the finish line. Keep a record of what changes.

Save a baseline, compare later scans, and get a focused alert. Explore the example below.

scaninspecting example.com

10 pages
41 passed
2 warnings

GET /200 · text/html
GET /pricing200 · text/html
GET /robots.txt200 · text/plain
seo.homepage-indexableHomepage can be indexed
discovery.sitemapXML sitemap found
analytics.detectedAnalytics detected
security.cspContent-Security-Policy header not detected
score 96 / 100 · same responses, same findings

Example output

baselinesaving a known-good state

96 score
43 findings stored

siteexample.com
savedMon 09:00
score96 / 100
findings41 passed · 2 warnings · 0 critical
scheduledaily · next check Tue 09:00
baseline stored with stable finding IDs for comparison

Example output

comparediffing Tue 09:00 against the baseline

3 new
1 resolved
1 persisting

discovery.robots-txtrobots.txt blocks search engines from the entire site
links.broken-internal1 broken internal link (/pricing → 404)
analytics.detectedNo common analytics implementation detected
seo.canonical-presentPages without a canonical tag — resolved
security.cspContent-Security-Policy header not detected — persisting
score 96 → 76 (−20)

Example output

alertnotifying the site owner

1 email
3 new findings

subjectexample.com: 3 new findings since your last scan
robots.txt blocks search engines from the entire site
1 broken internal link
No common analytics implementation detected
Score 96 → 76. Open the comparison for evidence.
alerts cover new findings and meaningful score drops

Example output

New. Resolved. Persisting. Severity changed.Start monitoring

04 / Coverage

The details that are easy to miss.

A focused launch-readiness check across your public website, with stable check IDs and observed evidence.

Fig. 01 — Example inspection. Illustrative findings, not a scan of a real site.

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

Launch readiness is an indicator, not a security, compliance, SEO-ranking, or accessibility score.

05 / Plans

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.

Monthly billing. No annual commitment.

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

For the long run

For developers and site owners.

$19/ month

Start Pro

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

A baseline today. Visibility tomorrow.

Agency

For people managing client websites.

$79/ month

Start Agency

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

Every client, in one workspace.

Pricing may evolve as Afterward grows.

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 account is required for a complete one-off audit through an MCP client. An account and a paid plan are required for saved sites, scan history, and scheduled monitoring.

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?

The Agency plan supports up to 50 saved sites, daily or weekly monitoring, and client/project organization. The current workspace has one account owner; team invitations and expanded client-ready reports are planned.

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 site View pricing

No account required Full one-off audit

Every scan covers

HTTPS
robots.txt
Sitemap
Canonicals
Open Graph
HSTS

Catch what breaks before your users do.

One broken link. A clear next step.

From a public URL to a useful next step.

Share your URL

Inspect what shipped

Follow the evidence

A closer look at what shipped. And what changes next.

Ship with fewer loose ends

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

One view for every client site

Ask for an audit in conversation

Don’t just see the issue. See what’s behind it.

1 broken internal link

Affected URLs

Recommended next step

robots.txt blocks search engines from the entire site

Affected URLs

Recommended next step

Pages with a missing or empty meta description

Affected URLs

Recommended next step

Strict-Transport-Security header not detected

Affected URLs

Recommended next step

You ask.Afterward checks.Your assistant explains.

1 broken internal link

Start with the pricing link.

Shipping isn’t the finish line. Keep a record of what changes.

The details that are easy to miss.

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

Free

Pro

Agency

Clear scope. No surprises.

Check your site before someone else does.

Catch what breaks
before your users do.

You ask.
Afterward checks.
Your assistant explains.

Check your site before
someone else does.