Public funnel review
Confirm homepage, features, role pages, pricing, and help content tell the same product story.
Rollout QA
A launch checklist for the public funnel, live workflows, analytics, and SEO
Use this checklist after deployment to validate that the `FBA Interview Generator` and `IEP Goal Generator` are discoverable, trustworthy, measurable, and working end to end.
Start Here
Compare the live homepage and pricing page against current plan limits.
Run one complete FBA interview and one complete IEP goal workflow in production.
Check GA4 for CTA and pricing activity after the first live sessions.
Submit the sitemap and validate structured data on the public pages.
5 review areas
Messaging, workflows, conversion, SEO, and support
2 feature launches
FBA Interview Generator and IEP Goal Generator
1 rollout checklist
Built for launch-day and post-deploy validation
What this checklist covers
This is the post-build validation pass that turns a clean deploy into a professional launch.
Workflow QA
Run the live FBA interview and IEP goal flows, including save, history, export, and upgrade states.
Analytics validation
Verify CTA clicks, pricing interactions, and other conversion events are arriving in GA4.
SEO checks
Confirm sitemap coverage, structured data, titles, descriptions, and indexing behavior after deploy.
Step 1
Review public messaging and trust signals
Start with the surfaces buyers and search engines see first. They should describe the same offer, the same feature set, and the same trial terms.
- Homepage, pricing, features, and role pages should all mention behavior tracking, FBA Interview Generator, and IEP Goal Generator consistently.
- Trial language should read as a 14-day free trial with no credit card required wherever the user is making a purchase decision.
- Tier descriptions should match actual limits for interview modes, goal generation, and save-to-record access.
- Footer, help-center, and navigation links should expose the new feature pages so they are easy to rediscover.
Step 2
Run live workflow QA inside the app
The public pages matter, but the product has to back up the promise. Run both assessment workflows with realistic student context.
FBA Interview Generator
Quick Screening, Focused, and Comprehensive workflow checks.
- Start a Quick Screening interview from a real student record and confirm the student context loads.
- Resume a saved draft from history and confirm the prior answers and mode-specific progress return correctly.
- Run an Essential or Professional test to verify AI-supported analysis, hypotheses, and next-step suggestions render.
- Verify plan gating: Starter should not expose higher-tier AI analysis or deeper interview modes.
IEP Goal Generator
Drafting, save-to-record, export, and limits checks.
- Generate a goal set from a realistic student context and verify all expected domains return.
- Save selected domains into the student record on an eligible tier and verify the saved data is visible afterward.
- Test export and copy workflows so teams can move results into meetings and documentation without formatting issues.
- Verify monthly limits and upgrade prompts behave correctly for Starter and Essential users.
Step 3
Validate conversion paths and analytics
A polished launch is measurable. Make sure high-intent clicks are attributed and the pricing path still feels trustworthy.
- Verify `marketing_cta_click` events fire from homepage, pricing, features, role pages, and this checklist page.
- Check plan-comparison and pricing-card events in GA4 so high-intent traffic is measurable.
- Review registration, contact, and pricing destinations for broken links or stale plan messaging.
- Confirm the most prominent CTA on each page still reflects the current offer and routes to the correct next step.
Step 4
Finish the external SEO pass
Code-level metadata is only part of the job. The live deployment still needs indexing and rich-result validation.
- Confirm `/features/fba-interview-generator`, `/features/iep-goal-generator`, `/pricing`, and `/features` return the expected title and meta description after deployment.
- Run Rich Results tests on the pricing page, feature hub, both new feature pages, and this help-center page.
- Submit the updated sitemap and request indexing if the new URLs are not discovered quickly.
- Review canonical tags, internal links, and noindex behavior so public feature pages index while private dashboard pages stay out of search.
Step 5
Close the loop with proof and follow-through
The final layer of polish happens after launch: production visuals, verified proof, and channel updates that keep the new pages active.
- Capture screenshots or a short walkthrough GIF from production once the UI is stable enough to use as proof on the feature pages.
- Collect one verified testimonial or practitioner outcome statement before adding social proof copy.
- Monitor GA4 and Search Console for a week after launch to see whether new pages are earning impressions and CTR.
- Update onboarding emails, demos, and outbound campaigns so these features become entry points, not only secondary pages.
Supporting rollout resources
Use these checklist downloads alongside the launch-readiness guide when you need something easier to hand to a team.
FBA Quality Assurance Checklist
Use a structured review before sharing interview findings or moving into BIP planning.
Open resourceIEP Meeting Preparation Checklist
Use a meeting-ready checklist when taking generated goals and progress notes into team review.
Open resourceBehavior Toolkit Checklist
Keep one shared operations checklist for launch prep, staff alignment, and follow-through.
Open resourceFrequently asked questions
Short answers for the highest-risk launch checks.
Which pages should be tested first after deploy?
Start with the homepage, pricing page, feature hub, the two public feature pages, and then the logged-in FBA Interview Generator and IEP Goal Generator workflows.
What matters most in the workflow QA?
Confirm student context loads, save and resume flows work, exports render correctly, and plan gating matches the published tier descriptions.
What should I verify in analytics?
Check that CTA and pricing interactions are arriving in GA4 with clear source-page context so you can compare which pages and offers convert.
What should I do outside the codebase?
Submit the sitemap in Search Console, run Rich Results tests on the public conversion pages, and inspect live titles and descriptions after deployment.
Use the checklist, then validate the live pages
The strongest next step is to compare the public feature pages with the real in-app workflows and confirm both match the published tier descriptions.