Stop 6 of 8 · Weekly
Launch with Claude in Chrome
Claude walks the live site with you the day before launch: links, forms, phone numbers, phone width, speed, and the fix list you work from.
The checklist is the deliverable
Every designer has a launch checklist, and most of them live in their head at eleven at night. Written down, it is the thing Claude runs for Dany. Claude in Chrome is an extension that reads and acts on the page in front of you, so it can open each page of the live site, follow the links, fill in the test form, and come back with a list rather than a feeling.
Dany keeps two lists. Before launch: the site works. After launch: it is being found. This stop is the first one, and it runs on a staging address before the domain switches.
What the pass looks for
| Check | The failure it catches |
|---|---|
| Links, page by page | A menu item that goes nowhere |
| Phone, email, address | A number that differs from the client list |
| Forms, end to end | A form that submits and delivers nothing |
| Phone width, 390 pixels | Text off screen, tap targets too small |
| Titles, descriptions, alt text | A page that shows up as an address in search |
| Weight and the biggest file | A six megabyte hero on mobile data |
Try this
Open the client's site in the tab, then paste this.
The full walk
Walk this site page by page. For each page give me: broken or dead links, images with no alt text, every place a phone number or email appears and whether it matches [paste the client contact details], text that runs off the screen at 390 pixels wide, and the page title and meta description with their character counts. One table, one row per problem, worst first.
The form test
Submit the contact form on this site with the name Test Dany, my email address, and a message saying launch test, then tell me exactly what happened: the confirmation the visitor sees, where the page goes next, and whether anything looked broken on the way. Do not submit any other form on the site.
The fix list I work from
Turn everything you found into a fix list with three columns: what is wrong, where I fix it, and what a visitor loses if I do not. Sort by what a visitor loses. Put anything that needs the client at the bottom in its own group.