TechnicalCollectible prompt
Website launch checklist from domain to first week
Act as a web project manager who has launched hundreds of sites. Build a launch checklist for {{website_url}}, going live on {{launch_date}}, built with {{tech_stack}}.
Group it into two weeks before, launch day, and the first week after. Cover:
- Content: proofreading, real photos, working links, correct prices and hours, legal pages and contact details
- Search: no leftover noindex tags or blocked robots file from staging, unique titles and descriptions, a sitemap submitted to Google Search Console, and redirects from every old URL
- Forms: each one tested end to end, with the email landing in the inbox, not spam
- Domain and email: DNS, HTTPS, one version of the domain redirecting to the other, and SPF, DKIM and DMARC records so site emails get delivered
- Speed, mobile and accessibility spot checks on a real phone
- Security: no secrets in the code, access rules on every table, admin accounts protected with two-factor sign-in
- Analytics and cookie consent working, favicon and share image set, a helpful 404 page
- Backups, uptime monitoring and a rollback plan
Mark each item with who usually owns it and whether it blocks launch.
Ask me first whether an existing site is being replaced, since that changes the redirect work.
Technicalnvoka.com/library/nvoka-website-launch-checklistScan to open
Technical
Website launch checklist from domain to first week
Go live without surprises, from DNS and forms to redirects, security and the first week.
Curated by Nvoka
ChatGPTClaudeGemini
Make it yours
Fill in the blanks and change any word. Only your copy changes, never the card.
Fill in the blanks
0 of 3 filledYour prompt
Act as a web project manager who has launched hundreds of sites. Build a launch checklist for {{website_url}}, going live on {{launch_date}}, built with {{tech_stack}}.
Group it into two weeks before, launch day, and the first week after. Cover:
- Content: proofreading, real photos, working links, correct prices and hours, legal pages and contact details
- Search: no leftover noindex tags or blocked robots file from staging, unique titles and descriptions, a sitemap submitted to Google Search Console, and redirects from every old URL
- Forms: each one tested end to end, with the email landing in the inbox, not spam
- Domain and email: DNS, HTTPS, one version of the domain redirecting to the other, and SPF, DKIM and DMARC records so site emails get delivered
- Speed, mobile and accessibility spot checks on a real phone
- Security: no secrets in the code, access rules on every table, admin accounts protected with two-factor sign-in
- Analytics and cookie consent working, favicon and share image set, a helpful 404 page
- Backups, uptime monitoring and a rollback plan
Mark each item with who usually owns it and whether it blocks launch.
Ask me first whether an existing site is being replaced, since that changes the redirect work.