Website Content Checklist for Clients

Accurate legal name, addresses, phone, email, and hours keep the site truthful and prevent launch corrections.

Instructions: Confirm the legal business name, trading name (if different), primary phone, public email, physical address(es), service area, and public hours. Flag anything that must not appear on the website.

Example (illustrative): Oakwood Dental · DBA: Oakwood Smile Studio · (512) 555-0142 · [email protected] · 120 Main St, Austin TX · Mon through Thu, 8 to 5 · Do not publish after-hours mobile.

• Legal and display names are clear
• Phone and email are monitored by the client
• Address and hours match what the client will stand behind
• Any private fields are marked do-not-publish

Owner: Client marketing contact · Reviewer: Agency project manager · Due: Project Start + 3 business days

Remind while the client owns this Ask. Pause on submission, help request, or approved extension.

Original vector and transparent logos let the team place a sharp mark on light and dark backgrounds.

Instructions: Upload the original vector file if available, plus a transparent PNG. Include light and dark versions and any existing brand guide. If you cannot locate the originals, name who created the logo and upload the best version you have.

Example (illustrative): logo.svg + logo-white.svg + Brand_Guidelines.pdf. Designer: River Studio (2019).

• Correct brand/version is identified
• Reviewer can open the files
• Available variants and limitations are recorded
• Upload alone is not treated as design approval

Owner: Client marketing contact · Reviewer: Agency designer · Due: Project Start + 3 business days

Remind only while the client owns the next action. Notify the designer after submission.

Licensed or owned images keep the site sharp and avoid copyright risk.

Instructions: Upload approved photos for hero, services, and about sections. Prefer originals over social crops. Note usage rights, photographer credit, and any images that must not appear publicly.

Example (illustrative): hero-job-site.jpg (owned, 2025) · team-reception.jpg (photographer: Lee Chen, web license) · Do not use patient faces from folder X.

• Rights/source noted for each set
• Restricted images flagged
• Resolution suitable for web hero/cards
• Captions or filenames map to intended pages

Owner: Client marketing contact · Reviewer: Agency designer · Due: Project Start + 10 business days

Remind while open; pause when help is awaiting agency reply.

Real page copy unblocks layout, development, and SEO structure. Placeholder text delays launch.

Instructions: For each page on the agreed sitemap, provide headline, short intro, body sections, and primary call-to-action. Paste text or upload a Doc/PDF labeled by page name. Mark anything still draft.

Example (illustrative): Home. Headline: “Roofing that lasts for Austin homes.” CTA: “Book a free inspection.” About: 2 short paragraphs + values bullets.

• Every agreed page has usable draft or final copy
• CTAs are specific (not “Submit”)
• Draft vs final status is labeled
• No competitor or client-confidential claims without approval

Owner: Client content owner · Reviewer: Agency copywriter or PM · Due: Project Start + 7 business days

Chase until submitted. After submission, agency review becomes the next action.

Named people and clear portraits build trust on About and Team pages.

Instructions: For each person who should appear on the site, provide name, title, a 2 to 4 sentence bio, and a sharp portrait (prefer 1200px+). Map filename to name and title in the notes.

Example (illustrative): jordan-lee.jpg maps to Jordan Lee, Marketing Manager: “Jordan leads client communications and has 8 years in local healthcare marketing.”

• Each portrait maps to a name and title
• Bios are client-approved for public use
• Photos are sharp enough for a team grid
• Anyone who must not appear is omitted

Owner: Client HR or marketing contact · Reviewer: Agency designer · Due: Project Start + 10 business days

Optional unless the sitemap includes a Team section.

One accountable approver prevents endless revision loops and unclear launch authority.

Instructions: Name the person who can approve final copy, design, and go-live. Include email and typical response window. Note any secondary stakeholders who must be consulted but do not hold final say.

Example (illustrative): Final: Priya Shah, Owner, [email protected], usually replies same business day. Consult: office manager for hours/phone only.

• One final decision maker is named
• Contact path for approvals is clear
• Consult-only stakeholders are labeled as such
• Launch approval will route to this person

Owner: Client owner or sponsor · Reviewer: Agency project manager · Due: Project Start + 3 business days

Blocking Ask. Keep chase active until confirmed. Do not invent an approver.