What Is a Front-End Checklist and What Should It Cover Before Launch?

A front-end checklist is a structured set of quality rules you run through before shipping a website, covering markup, styling, performance, accessibility, SEO, security, and more. Use one when you're about to deploy a new site, push a major redesign, or cut a high-risk release — it turns "I think it's ready" into a repeatable pass with a defined scope. The Front-End Checklist (frontendchecklist.io) organizes this as 350+ rules across 11 categories, plus curated workflows for common situations.

What a front-end checklist actually is

It's not a single document but a corpus of rules grouped by concern. Each rule is a discrete check you either pass or don't, which is what makes the format useful: you can track progress (the site shows counts like "0 / 95" per category), hand it to a reviewer, or run it as a pre-launch gate.

The scope is deliberately broad because front-end quality is broad. A site can have clean HTML and still fail on Core Web Vitals, or pass performance and fail WCAG.

The 11 categories and what each covers

Two things stand out from the counts. First, accessibility and SEO together account for over half the rules — they're where most real-world defects hide. Second, the small categories (I18n, Privacy) aren't less important; they're narrower in scope, which is why they have fewer discrete checks.

Curated workflows vs. browsing all rules

You have two entry points, and the right one depends on whether you know what you're looking for.

Browse by category when you already know the area that needs work — say, you're auditing images or tightening security. You go straight to those rules.

Start a curated checklist when you want a guided path. Three examples from the site:

• Launch Checklist — essential checks before deploying to production, spanning HTML, SEO, security, and performance. 16 rules, ~45 minutes, rated beginner. Intended for a new site, major redesign, or high-risk release.
• SEO Audit — comprehensive search optimization pass. 12 rules, ~30 minutes, intermediate. Use when traffic, indexing, metadata quality, or editorial discoverability are active concerns.
• Performance Quick Wins — high-impact optimizations that are relatively easy to implement. 8 rules. Use when you want the biggest gains without a deep performance investigation.

The time and skill ratings matter for planning: a 45-minute beginner pass and a 30-minute intermediate pass are different commitments, and you can assign them to different people.

How to run a checklist as a review pass

1. Pick the workflow that matches your situation. Pre-launch → Launch Checklist. Traffic or indexing problems → SEO Audit. Slow site, limited time → Performance Quick Wins.
2. Work through the rules and mark pass/fail. The site tracks progress per category, so you can see what's outstanding rather than relying on memory.
3. Treat failures as a fix list, not a verdict. A failed rule is a specific, actionable item — that's the point of the format.
4. Re-run after fixes. Because rules are discrete, you can verify only what changed.

The common failure mode is treating the checklist as a one-time read rather than a pass you actually execute. Reading 95 accessibility rules teaches you something; running them against your site finds the defects.

Humans and AI agents, same standards

The site positions the same rule corpus for both human reviewers and AI-assisted audits, with an MCP server to connect the standards to AI tools. Practically, this means a junior developer, a senior reviewer, and an AI-assisted audit can work from identical criteria — useful when you want consistency across a team or a second pass that doesn't depend on reviewer memory.

If your goal is simply to know whether a site is ready to ship, start with the Launch Checklist and expand into category-level rules only where it flags problems.