final-checklist

Manuelvillarvieites's avatarfrom Manuelvillarvieites

Comprehensive pre-launch verification checklist. Use as the last step before deploying. Triggers on "final check", "pre-launch", "ready to deploy", "launch checklist".

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 14, 2025
[Testing and QA]

When & Why to Use This Skill

This Claude skill provides a comprehensive pre-launch verification checklist designed to ensure websites are technically sound, SEO-optimized, and legally compliant before deployment. It streamlines the final quality assurance process by covering critical areas such as performance benchmarks, mobile responsiveness, and internationalization, helping developers avoid common post-launch errors.

Use Cases

  • Final QA Checklist: Use as a mandatory verification step before moving a web project from staging to production to catch broken links, placeholder text, or missing alt tags.
  • SEO & Technical Audit: Ensure all pages have unique meta descriptions, title tags, and correctly configured sitemap.xml and robots.txt files for better search engine ranking.
  • Legal & Compliance Review: Verify the presence of mandatory legal pages like Privacy Policy (Datenschutz) and Impressum, and ensure cookie consent mechanisms are active.
  • Performance & UX Validation: Confirm the site achieves a Lighthouse score above 90, loads in under 3 seconds, and maintains a flawless user experience across all mobile breakpoints.
  • Deployment Readiness: Follow a structured workflow to verify environment variables, production builds, and SSL certificate status before the final launch.
namefinal-checklist
descriptionComprehensive pre-launch verification checklist. Use as the last step before deploying. Triggers on "final check", "pre-launch", "ready to deploy", "launch checklist".

Final Checklist

Comprehensive verification before website launch.

Content

  • All pages have unique title tags (50-60 chars)
  • All pages have unique meta descriptions (150-160 chars)
  • All H1s contain primary keywords
  • Only ONE H1 per page
  • All images have alt text
  • No placeholder text ("Lorem ipsum")
  • No broken links
  • Contact info is correct

Technical SEO

  • sitemap.xml accessible at /sitemap.xml
  • robots.txt allows crawling
  • Schema.org JSON-LD added
  • Open Graph tags on all pages
  • Twitter cards configured
  • Canonical URLs set
  • Impressum page exists and accessible
  • Datenschutz page exists and accessible
  • Cookie consent (if analytics used)
  • All required legal info present

Design

  • Favicon displays correctly
  • 404 page works
  • Mobile responsive (test all breakpoints)
  • No horizontal scroll
  • Dark mode works (if applicable)

Performance

  • Lighthouse score > 90
  • Page load < 3 seconds
  • Images optimized (WebP)
  • No console errors
  • No console warnings

i18n

  • DE translations complete
  • EN translations complete
  • Language switcher works
  • URLs use correct locale prefix

Forms

  • Contact form submits correctly
  • Form validation works
  • Success/error messages display
  • Email delivery tested

Final Steps

  1. Run pnpm build - verify no build errors
  2. Test production build locally
  3. Verify all environment variables set
  4. Deploy to staging first
  5. Full QA on staging
  6. Deploy to production

Launch Readiness

[ ] All checklist items passed
[ ] Client approval received
[ ] DNS configured correctly
[ ] SSL certificate active
[ ] Analytics tracking verified