Website With Claude Code
SOP — Website Build & Launch Process
Purpose
This SOP covers the full process for building a new client website, from the time the client signs up through gathering information, building the website in Claude Code, uploading it to Hostinger, collecting revisions, connecting the client's domain, and launching the final site.
The goal is to keep every website build consistent, organized, and easy for another team member to pick up if needed.
1. Client Signs Up
Once a client signs up for the website service:
Confirm the client has completed payment/signup.
Confirm their business name.
Confirm the primary contact name.
Confirm phone number and email.
Add or confirm the client in the website tracking Google Sheet.
Determine which Website Information Track below applies.
2. Determine Which Website Track Applies
Every website should follow one of these three tracks.
TRACK 1 — Client Already Has a Website
Use this track when the business already has a website that contains useful information we can use for the new site.
Gather:
Current website URL
Any additional information supplied by the client
New photos they want used
Logo/branding files if available
Google Review Widget information
Any important changes they want from the old website
Builder's name
The existing website should be provided directly to Claude so it can read the current site and use it as a source of information.
Important: The goal is not necessarily to copy the old website. Use it to understand the company, services, service areas, contact information, positioning, and other relevant business information.
TRACK 2 — Client Has a Reference / Focus Website
Use this track when the client does not have a useful existing website but has provided a website they want their new site to take inspiration from.
Gather:
Reference/focus website URL
Business name
Business contact information
Services
Service areas
Any other information provided by the client
Photos
Logo/branding
Google Review Widget information
Builder's name
Tell Claude that the reference website is being supplied for design, layout, content-direction, or feature inspiration and that it should still create a website specifically for the client's business.
Do not blindly copy another company's branding or content.
TRACK 3 — Client Has No Existing Website or Useful Online Information
If the client does not have an existing website or enough information online to build from, a team member needs to speak with the client.
Schedule the Call
The rep should contact the client and ask:
When is a good time today or tomorrow for us to give you a quick call and gather everything we need for your new website?
The builder or assigned team member then calls the client.
Website Discovery Call
Ask the client all of the questions contained on the approved Website Information Form / Question Sheet.
Gather enough information to understand:
What the business does
Main services
Most important services
Service areas
Ideal customers
What makes the company different
Years in business
Company story
Phone number
Email
Business address if applicable
Hours
Licensing/certifications if relevant
Calls to action
Any warranties or guarantees
Financing information if applicable
Frequently asked questions
Anything the client definitely wants included
Anything the client does NOT want included
Record the call when appropriate and permitted.
After the call:
Obtain the transcript.
Add the transcript to Claude.
Include any available photos.
Include logo/branding.
Include the Google Review Widget.
Review the client's Google reviews if available.
Use Reviews as a Source of Information
Google reviews can be extremely helpful when the client has limited website content.
Reviews may reveal:
Services customers commonly hire them for
Geographic areas they serve
Team member names
Common customer problems
What customers like about the company
Recurring selling points
Quality-of-service themes
Use this information to help Claude understand the business.
Do not invent claims based on reviews.
3. Photos and Video
Before beginning the build, determine whether enough quality photos are available.
If Good Photos Exist
Collect and organize them for the build.
Examples:
Team photos
Owner photos
Completed projects
Before-and-after photos
Building/location photos
Vehicles
Equipment
Service photos
Product photos
Logo
If More Photos Are Needed
Request additional photos from the client.
If applicable, offer professional photography/video services.
If an on-site shoot needs to be scheduled, use the approved filming days:
Monday / Wednesday / Friday
unless otherwise approved.
Do not unnecessarily delay the website if usable temporary imagery can be used while waiting for final photography.
4. Open Claude Code
Once enough information has been collected, begin the actual website build.
Step 1 — Open Claude Code
Open Claude Code on the computer.
Step 2 — Confirm You Are in the Correct Mode
Make sure you are in the Code section located in the top-right area.
Do not begin the website build in the wrong Claude interface.
Step 3 — Start a New Chat
Create a new Claude chat for the client.
Each new website should generally have its own dedicated chat so the project's context remains clean.
Step 4 — Set the Working Directory
Set the working directory to the:
MLB Website Files
directory.
Confirm that Claude has access to the appropriate website template/files before giving it the build instructions.
5. Prepare the Claude Prompt
Your Claude prompt should contain all of the information gathered for the appropriate track.
At minimum, include:
Business name
Business information
Website/reference links
Client instructions
Services
Service areas
Contact information
Photos/assets
Google Review Widget
Transcript if applicable
Any design requests
Any specific features requested
Your name as the person building the site
Always Add Your Name
Include the website builder's name in the prompt.
Example:
Website Builder: John
This allows the team to know who originally built the project if questions or revisions come up later.
6. Claude Prompt — Track 1
If the client already has a website, the prompt should tell Claude to:
Review the existing website.
Extract relevant business information.
Use the information to create a substantially improved new website.
Incorporate the client's new photos and information.
Add the approved Google Review Widget.
Follow the established MLB website project structure.
Make the new website responsive and mobile-friendly.
Include clear calls to action.
Preserve accurate important business information.
Avoid copying outdated design elements or unnecessary content from the old site.
Include:
Existing Website:
[PASTE URL]
Additional Client Information:
[PASTE INFORMATION]
Photos / Assets:
[ADD FILES]
Google Review Widget:
[ADD WIDGET INFORMATION]
Website Builder:
[YOUR NAME]
7. Claude Prompt — Track 2
If the client has a reference/focus website, tell Claude:
Review the reference website.
Use it for inspiration where appropriate.
Build an original website for the client's business.
Use the client's own branding and information.
Add the client's photos.
Add the Google Review Widget.
Follow the MLB website structure and development standards.
Make the website fully responsive.
Add strong calls to action.
Include:
Reference / Focus Website:
[PASTE URL]
Client Business Information:
[PASTE INFORMATION]
Photos / Assets:
[ADD FILES]
Google Review Widget:
[ADD WIDGET INFORMATION]
Website Builder:
[YOUR NAME]
8. Claude Prompt — Track 3
If the client has no existing website, provide Claude with the discovery-call transcript.
Tell Claude to:
Read the full transcript.
Extract the relevant factual information about the business.
Organize the information into an effective local-business website.
Use Google reviews as additional context when supplied.
Incorporate the supplied photos.
Add the Google Review Widget.
Follow the MLB website project structure.
Make the site responsive and mobile-friendly.
Create strong calls to action.
Do not invent facts that were not supplied.
Include:
Client Discovery Call Transcript:
[PASTE TRANSCRIPT]
Additional Information:
[PASTE INFORMATION]
Google Reviews / Review Information:
[ADD IF AVAILABLE]
Photos / Assets:
[ADD FILES]
Google Review Widget:
[ADD WIDGET]
Website Builder:
[YOUR NAME]
9. Let Claude Build the Website
After the prompt and all relevant information have been supplied, allow Claude to begin the build.
Use the approved coding model.
Depending on the current setup, this may include:
Sonnet
Opus
A normal first build may take approximately:
30 minutes
Do not assume the website is finished simply because Claude has stopped generating.
When Claude finishes, review the website.
10. Internal Quality Check
Before sending anything to the client, check the website yourself.
Review both desktop and mobile.
Business Information
Business name is correct
Phone number is correct
Email is correct
Address is correct
Hours are correct
Services are correct
Service areas are correct
No invented information
Website
Homepage loads properly
Navigation works
All important pages work
Buttons work
Forms work
Phone links work
Email links work
Mobile layout looks correct
Photos display correctly
Logo displays correctly
Review Widget works
There is a clear call to action
There are no obvious spelling errors
There are no placeholder sections
There is no leftover information from another website/template
Do not send a website to a client without completing this check.
11. Create the Website in Hostinger
Once the website passes the internal review:
Log into Hostinger.
Create the new website.
Create/get the temporary Hostinger domain.
Set up the website environment.
12. Add Temporary Domain to the Google Sheet
Copy the temporary domain.
Add it to the client's row in the website tracking Google Sheet.
Also add the required access information, including:
Temporary website URL
Leads portal password
Any other required internal access information
The Google Sheet needs to remain updated so anyone on the team can locate the current website.
13. Upload the Website Files
Inside Hostinger:
Open the website dashboard.
Go to the File Manager.
Locate the appropriate public website directory.
Upload the website files generated by Claude.
Confirm the files are in the correct location.
Load the temporary URL.
Verify the site works on the live temporary domain.
Do another quick desktop and mobile check after uploading.
14. Send First Preview to Client
Once the temporary website is working, send the temporary domain to the client.
Explain that this is their first website preview and that they can request changes.
The goal of this stage is to gather the first round of edits.
After sending the link, follow up with a phone call when appropriate.
It is often easier for the client to explain their changes verbally than trying to write everything in an email.
15. First Revision Call
Ask the client to review:
Homepage
Services
Photos
Wording
Contact information
Colors/design
Calls to action
Anything missing
Anything incorrect
Record/transcribe the revision call when appropriate.
Ask the client to identify all changes they can think of during this round, rather than sending one change at a time.
16. Put Revision Transcript Into Claude
Return to the same Claude Code chat used to build the website.
Provide the revision transcript.
Tell Claude clearly:
These are client-requested revisions to the website you just built. Review the transcript, identify every requested change, make those changes, and do not change unrelated areas of the website unless necessary.
Allow Claude to complete the changes.
17. Review Claude's Changes
Before uploading the revised files:
Confirm every requested edit was completed.
Confirm nothing important was accidentally removed.
Confirm mobile still works.
Confirm forms/buttons still work.
Confirm contact information remains correct.
Upload the revised files to Hostinger.
18. Send Second Preview / Final Round of Edits
Send the updated temporary domain to the client.
Ask them to review it again.
If another revision call is needed:
Speak with client.
Record/transcribe requested changes.
Add transcript to the same Claude project.
Have Claude make the revisions.
Review the changes.
Upload the new version.
Send it to the client.
Continue through the approved revision process until the site is approved.
19. Obtain Final Approval
Do not connect the client's main domain until the client has approved the website.
Confirm:
Website design approved
Website copy approved
Photos approved
Contact information approved
Services approved
Forms working
Review Widget working
Client is ready for launch
20. Connect the Client's Domain
After final approval:
Obtain access to the existing domain/DNS as needed.
Connect the client's domain to the Hostinger website.
Configure the required DNS records.
Confirm SSL is active.
Confirm both the root domain and preferred
www/non-wwwversion work correctly.Confirm redirects if necessary.
21. Launch the Website
After the domain is connected, perform the final launch check.
Final Launch Checklist
Correct domain loads
SSL/HTTPS works
Desktop site works
Mobile site works
Navigation works
Phone button works
Email works
Forms work
Review Widget works
All important photos load
No temporary URLs are visible
No placeholder text remains
Correct business information
Page titles / basic SEO information are present
Favicon/logo works if applicable
Client has been informed the website is live
22. Update Internal Tracking
After launch, update the Google Sheet.
Record:
Final domain
Launch date
Temporary domain if it needs to remain recorded
Leads portal password
Website builder
Status = LIVE
Any relevant notes
Golden Rules
Never begin building until you have enough information about the business.
Always put the builder's name in the Claude prompt.
Always use the client's existing website, reviews, transcripts, photos, and other available information before asking Claude to create content from scratch.
Claude should never invent important facts about a business.
Always review Claude's work yourself before the client sees it.
Always check the mobile version.
Always use a temporary domain for client review before connecting the final domain.
Put revision-call transcripts back into the same Claude conversation whenever possible so Claude retains the context of the website.
Do not launch until the client has approved the site.
Do not consider the project complete until the final domain works, SSL works, forms work, and the Google Sheet has been updated.