Website Launch Checklist for Agencies: Everything to Collect Before Go-Live

Short answer

A website launch checklist for agencies should cover everything needed from both the agency and the client before go-live: final content, access, DNS decisions, redirects, QA, forms, analytics, SEO settings, stakeholder approval, and post-launch monitoring. The best checklist also assigns owners, due dates, and blockers so launch readiness is visible before the final week.

Why agencies need a launch checklist that includes the client

Most website launches do not slip because the agency forgot how to publish a site.

They slip because the last mile depends on people outside the production team.

The client needs to confirm copy. Someone has to approve legal pages. A domain admin needs to update DNS. A marketing manager needs to test lead routing. A founder needs to give final approval. Someone has to confirm whether the old careers page should redirect, archive, or stay live.

When those tasks live across email, Slack, comments, spreadsheets, and meeting notes, the project can look “almost done” while launch risk is quietly climbing.

A strong website launch checklist for agencies does two jobs:

It confirms the technical, content, SEO, QA, and approval work needed before go-live.
It makes client-owned launch tasks visible, assigned, and follow-up friendly.

That second part is where many agency launch checklists fall short.

What should an agency collect before launching a website?

Before go-live, agencies should collect or confirm:

Final approved page content
Final images, logos, downloads, and brand assets
Redirect decisions for changed or removed URLs
Domain, DNS, hosting, CMS, and analytics access plans
Form recipients and CRM or inbox routing
Legal, privacy, cookie, and compliance page approvals
SEO metadata, sitemap, robots, and indexing settings
QA approval across key devices and browsers
Launch-day availability from client stakeholders
Final written launch approval

The checklist should not simply say “client approval.” It should define who approves what, what remains blocked, and what decision allows the agency to proceed.

Website launch checklist for agencies

Use this checklist as a practical go-live framework. Adjust it for the size of the site, the platform, and the risk of the launch.

Area	What to collect or confirm	Typical owner
Content	Final copy, images, PDFs, bios, case studies, product details	Client and agency
Technical SEO	Redirect map, canonical URLs, metadata, sitemap, robots, noindex removal	Agency
Access	Domain, DNS, CMS, analytics, Search Console, hosting, plugin accounts	Client admin and agency
QA	Forms, links, navigation, responsive checks, browser checks, accessibility basics	Agency
Tracking	Analytics, conversions, pixels, events, form destinations	Agency and client marketing
Legal	Privacy policy, terms, cookie notice, regulated claims, disclaimers	Client
Approval	Final approver, decision, timestamp, launch notes	Client lead
Launch day	DNS timing, deployment window, rollback contact, post-launch checks	Agency
Post-launch	Monitoring, crawl checks, Search Console review, client handoff	Agency

1. Collect final content and assets

Content is one of the most common client-side launch blockers.

The agency may have the site built, but the client still owes:

Final homepage copy
Leadership bios
Product or service descriptions
Case study approvals
Final pricing or package language
Downloadable PDFs
Team photos
Logos and partner marks
Testimonials with permission to publish
Legal disclaimers
Final calls to action

A launch checklist should separate “content received” from “content approved.” A draft Google Doc in a thread is not the same as final approved copy on the live page.

For every content item, track:

Page or component
Required asset
Owner
Due date
Current status
Whether it blocks launch
Approval status

Example:

Page	Needed	Owner	Blocks launch?
About	Final CEO bio	Client marketing lead	Yes
Careers	Confirm whether page launches now or later	Client HR lead	No
Case study	Legal approval on customer quote	Client legal contact	Yes
Contact	Correct office address and phone number	Client operations	Yes

This is where agencies can prevent “quick question” chaos in the final week.

Access tasks need special handling. Agencies often need to work with domains, DNS, CMS accounts, analytics, hosting, forms, plugins, or third-party tools. But clients should not paste passwords, API keys, recovery codes, private tokens, SSH keys, payment credentials, or other secrets into a launch checklist or client portal.

Safer access options include:

Invite the agency as a user with the right permission level.
Create a temporary user account for the agency.
Ask the client’s IT or admin contact to complete the DNS or account action directly.
Use a secure password manager when credential sharing is truly necessary.
Share only non-sensitive confirmations in the launch checklist, such as “Agency added as admin” or “DNS admin will make update on launch day.”

For domain and DNS work, collect the decision and owner, not the secret.

Track:

Domain registrar
DNS host
Who can make DNS changes
Whether agency has user access
Launch-day contact
Planned TTL change, if relevant
Required records
Confirmation once records are updated

This keeps the launch moving while reducing avoidable credential risk.

3. Prepare redirects and SEO launch details

If the website is a redesign, migration, domain change, or major URL change, redirects should be decided before launch week.

Google’s guidance on site moves with URL changes highlights common migration problems such as incorrect redirects, noindex rules, robots.txt blocks, and outdated sitemaps. Those are exactly the issues agencies should turn into pre-launch checklist items.

Collect and confirm:

Old URL
New URL
Redirect type
Pages intentionally removed
Pages that should return 404 or 410
Canonical URL decisions
Metadata for priority pages
Open Graph images and social previews
XML sitemap location
Robots.txt rules
Noindex removal plan

Google also recommends submitting sitemaps through Search Console, while noting that sitemap submission is a hint rather than a guarantee. For agencies, the practical takeaway is simple: do not treat “sitemap exists” as the only SEO launch step. Confirm the sitemap contains the right production URLs and that Search Console access is ready.

A small but important launch check:

Visit production URLs directly.
Confirm staging noindex tags are removed where appropriate.
Confirm robots.txt is not blocking pages meant to rank.
Confirm canonical tags point to the live URL.
Confirm the sitemap uses absolute production URLs.

4. Test forms, CTAs, and lead routing

A launch can look perfect while leads quietly disappear.

Before go-live, test every conversion path:

Contact forms
Quote request forms
Newsletter forms
Demo request forms
Booking links
Checkout flows
Donation flows
Job application forms
Download gates
Chat widgets
Phone links
Email links

For each form, confirm:

Required fields work.
Error states are understandable.
Submission confirmation appears.
The right person or system receives the lead.
CRM fields map correctly, if applicable.
Spam protection works.
Thank-you pages or events fire correctly.
Mobile submission works.

Do not just test one happy path. Test the form like a real visitor who mistypes, skips a field, or submits from a phone.

5. Run practical QA before launch day

A useful agency launch checklist should make QA specific enough that nobody can wave it away with “looks good.”

Include checks for:

Broken links
Missing images
Placeholder text
Navigation behavior
Footer links
Header behavior
Mobile layout
Tablet layout
Common browser checks
404 page
Search, filters, or dynamic content
Page speed issues
Image compression
Accessibility basics
Cookie banner behavior, if used
Form labels and keyboard navigation

For accessibility, web.dev’s accessibility guidance recommends using semantic page structure and proper labels for form fields. That is a good reminder that pre-launch QA should include more than visual review. A page can look right and still be hard to use.

At minimum, test:

Can someone tab through key links and forms?
Are form fields clearly labeled?
Does text remain readable on mobile?
Do images have useful alt text where needed?
Is the page structure logical?
Are color contrast issues obvious?

The goal is not to solve every future accessibility concern in the final week. The goal is to avoid launching with basic, preventable issues.

6. Confirm analytics and measurement

Analytics problems are easy to miss because the site still works.

Before launch, confirm:

Analytics property
Tag manager access
Conversion events
Form submission events
Thank-you page tracking
Ad pixels
Cookie consent behavior, where applicable
Search Console property
Sitemap submission plan
Reporting owner after launch

Ask the client which conversions matter most. Agencies often track the form because it exists, but the client may care more about demo bookings, phone calls, PDF downloads, job applications, or partner inquiries.

A good checklist turns “tracking installed” into “the client agrees these are the launch metrics.”

7. Confirm legal and compliance-owned content

Agencies should not guess on legal language.

Before go-live, collect approvals for:

Privacy policy
Terms and conditions
Cookie notice
Accessibility statement, if used
Industry disclaimers
Medical, financial, legal, or regulated claims
Testimonials and case study permissions
Copyright or trademark-sensitive content
Employment and hiring language
Promotional offer terms

For most agencies, the right workflow is simple: show the client exactly where approval is needed, assign it to the right stakeholder, and record the decision.

Do not let legal approval stay buried in a meeting comment like “I think this is fine.”

8. Define launch-day roles and timing

Launch day should not start with the agency asking, “Who has DNS?”

Confirm:

Launch date
Launch window
Time zone
Agency deployment owner
Client launch contact
DNS owner
Backup contact
Final approval deadline
Post-launch QA owner
Communication channel for launch day
Rollback decision owner, if needed

Also confirm when the client team is available. A 5 p.m. launch is risky if the only DNS admin leaves at 3 p.m. or the final approver is traveling.

The checklist should make availability explicit.

9. Record final launch approval

Final approval should be clear enough that the agency can look back and understand who approved launch, when they approved it, and what they approved.

For operational reference, record:

Approver name
Approver role
Approval date and time
Site or project approved
Known exceptions
Decision: approved, approved with exceptions, or not approved
Notes
Agency team member who recorded it

Shipperly is not a legal e-signature tool, and launch approval inside Shipperly should not be treated as a replacement for formal legal documents. But agencies still need a clear operational record so go-live is not based on a vague “looks good” message from a thread.

A simple agency launch workflow

Here is a practical workflow agencies can reuse for client website launches.

Step 1: Create the launch checklist early

Do this before the site is “almost done.”

Add the known client-owned tasks as soon as they appear:

Content decisions
Access needs
DNS owner
Legal approvals
Brand assets
Redirect decisions
Final approver

Early visibility prevents the final week from becoming a scavenger hunt.

Step 2: Assign every client-owned task

Every request should have one owner.

Avoid vague assignments like:

Client team
Marketing
Leadership
IT

Use named owners where possible:

Priya to confirm DNS access
Jordan to approve homepage copy
Sam to review privacy policy
Morgan to confirm CRM lead routing

If the client has several stakeholders, ask for a Client Lead who can delegate requests internally.

Step 3: Mark what blocks launch

Not every open item should delay go-live.

Separate tasks into:

Launch blocking
Important but not blocking
Post-launch follow-up
Waiting on agency
Waiting on client

This helps agency teams avoid false panic while still surfacing real launch risk.

Step 4: Review readiness before the final week

Hold a launch readiness review before the last sprint.

Ask:

What is overdue?
What is unassigned?
What is blocked?
What requires client approval?
What requires access?
What could still delay DNS or deployment?
What can move to post-launch safely?

This is different from checking percent complete. A site can be 90 percent complete and still not ready.

Step 5: Get final approval in writing

Before go-live, send the client a concise approval request that includes:

Launch date and time
Site URL or staging URL
Known open items
What approval means operationally
Who is approving
What happens next

Then record the approval in the same launch workflow.

Practical website launch checklist template

Copy this structure into your agency launch process.

Client-owned tasks

Agency-owned tasks

Launch-day tasks

Post-launch tasks

Crawl for broken links or redirect errors
Monitor Search Console
Check form submissions again
Review analytics events
Confirm client can access CMS, if applicable
Log post-launch fixes
Move non-blocking tasks into a follow-up list
Close the launch with a handoff note

Common mistakes agencies make with launch checklists

Treating the checklist as an internal QA list only

Internal QA matters, but it does not cover client-side launch risk.

If client approvals, access, content, DNS, legal review, and stakeholder decisions live somewhere else, the agency still has launch exposure.

Waiting until the final week to ask for access

Access requests can take days, especially when the client has IT, procurement, security, or a domain admin involved.

Ask early. Track the access path. Use safe sharing methods.

Using “the client” as the owner

“The client” is not an owner.

A launch task needs a person, a due date, and a clear request. Otherwise, everyone assumes someone else has it.

Confusing progress with readiness

A project can be nearly complete and still blocked by one unresolved DNS task, one unapproved legal page, or one missing redirect decision.

Track launch readiness, not just task completion.

Getting informal approval

A meeting comment or emoji reaction is easy to misread later.

Agencies should record final approval clearly, including who approved, when, what was approved, and whether any exceptions remained.

How Shipperly helps agencies manage launch checklists

Shipperly is an AI launch coordinator for website agencies. It helps agencies keep client-side website launch work moving without turning the launch into another generic project management board.

Inside Shipperly, agencies can organize launch requests, assign client-owned tasks, surface blockers, and keep overdue or unassigned work visible. The client sees a focused action portal instead of digging through long email threads.

Shipperly is especially useful when the launch depends on client-side work such as:

Content approvals
DNS ownership
Safe access steps
Legal review
Stakeholder decisions
Final launch approval
Blocked or overdue client requests

A Client Lead can help delegate requests to the right client stakeholders. Magic-link access makes it easier for clients to open their launch tasks without creating another password. Shipperly can also draft follow-ups for agency review, so the agency can send clearer reminders without starting from a blank page.

For launch readiness, Shipperly helps agencies see what is overdue, blocked, unassigned, or risky before launch day. It can also record final launch approval for operational reference, so go-live is tied to a clear decision instead of a scattered message trail.

Shipperly does not replace your agency’s technical QA process, secure password manager, file storage system, or legal approval tools. It gives the launch team a focused place to manage the client-side work that often decides whether go-live is calm or chaotic.

FAQ

What is a website launch checklist for agencies?

A website launch checklist for agencies is a structured list of the content, access, QA, SEO, approval, and launch-day tasks needed before a client website goes live. It should include both agency-owned work and client-owned launch tasks.

When should an agency start the launch checklist?

Start the launch checklist early in the project, not during the final week. Add access needs, content approvals, legal reviews, DNS ownership, and final approval requirements as soon as they become known.

What client tasks usually delay website launches?

Common client-side delays include late content, unclear final approval, missing DNS access, unapproved legal pages, unresolved form routing, delayed stakeholder feedback, and uncertainty about who owns each decision.

No. Clients should not paste passwords, API keys, recovery codes, SSH keys, payment credentials, or other secrets into a launch checklist. Safer options include inviting the agency as a user, creating a temporary account, using a secure password manager, or asking the client admin to complete the action directly.

What is the difference between launch progress and launch readiness?

Launch progress measures how much work appears complete. Launch readiness measures whether anything still blocks go-live. A site can be 90 percent complete and still high risk if final approval, DNS access, redirects, or legal review are unresolved.

Final CTA

Run your next client website launch with a checklist that shows what is ready, what is blocked, and who owns each client-side task.

Start a launch checklist in Shipperly to assign client requests, surface launch blockers, draft reviewable follow-ups, and record final launch approval before go-live.