SEO / AEO
Unique metadata, FAQ schema, and answer-led copy.
Launch checklist
Everything to verify before launch
Use this as the final preflight for copy, SEO/AEO, performance, analytics, and support.
This page is intentionally noindex while it serves as an internal working checklist.
Performance
Fast first paint, lighter image delivery, reduced motion.
Trust
Visible support, legal pages, and social previews.
Monitoring
Search Console, analytics, and error checks in place.
Content and positioning
Make it obvious in one read what the product is, who it is for, and why it matters.
- Hero headline says what CometLens does without internal jargon.
- Primary CTA copy is consistent across hero, footer, and contact pages.
- Placeholder copy, filler language, and duplicate claims are removed.
- Feature pages answer the question a buyer would ask before scrolling.
SEO and AEO
Search engines and answer engines should see clean metadata and direct answers.
- Each public page has a unique title, description, and canonical URL.
- Homepage answers what it is, who it is for, and what it replaces.
- FAQ and article structured data validate without warnings.
- Robots and sitemap include only public launch pages.
Performance and accessibility
Keep the page fast, stable, and usable with or without motion.
- Hero and blog images load without layout shift.
- Heavy sections use lazy rendering and avoid blocking first paint.
- Motion respects `prefers-reduced-motion`.
- Keyboard focus is visible on links, buttons, and form fields.
Forms and analytics
The launch should be measurable from the first visitor.
- Demo form submits end to end in the production environment.
- CTA clicks and form successes are tracked in analytics.
- Error and success states have clear copy.
- Thank-you path or confirmation message works on mobile and desktop.
Trust and legal
Make support and policy details easy to find before visitors ask.
- Privacy and terms links are visible in the footer.
- Support email and contact route are working.
- Open Graph images and favicons render correctly in social shares.
- Internal pages that are not public remain noindex.
Post-launch monitoring
The first week should focus on real traffic, not guesswork.
- Search Console is connected and receiving the sitemap.
- Top landing pages are reviewed for click-through and bounce issues.
- 404s, form errors, and slow pages are checked daily for the first week.
- Any broken link or missing image is fixed immediately.
Launch rule of thumb
Do not go public until the content, search, and demo flow are green.
If one of those areas is not ready, keep the page internal, fix the gap, and recheck before you announce.