Start with a specific inventory
Clients struggle with “send us the website content” because it is too vague. Give them a list that matches the site you are building.
Ask for homepage copy, service pages, team bios, testimonials, case studies, images, logo files, social links, and access details as separate items. The clearer the slots, the less interpretation the client has to do.
Separate copy assets and access
Treat content, files, and credentials as different workflows.
- Copy can be drafted, reviewed, and revised.
- Assets need quality checks.
- Access details need careful handling and clear ownership.
Putting all three into one email thread creates confusion quickly.
Review before you build
Do not wait until design or development to discover that a logo is too small, a testimonial is missing attribution, or CMS access points to the wrong environment.
Review submissions as they arrive. Mark incomplete or unusable items clearly, then ask for a replacement while the client still has context.
Use a portal
A client portal gives the client one place to see what is done and what is still missing. For the agency, it creates a cleaner handoff than email attachments, Drive folders, and reminder messages spread across the team.
Practical version
The short version clients and internal teams can act on immediately.
Website content collection works best when copy, images, source files, access details, and approvals are requested as separate items with clear owners.
Request structure
A more specific structure gives the page more utility and gives clients fewer decisions to interpret.
Page copy
Required text
Collect homepage, service pages, about page, bios, testimonials, case studies, and legal copy separately.
Image assets
Required file
Ask for original images, usage rights, captions, alt text notes, and replacement needs.
Brand files
Required file
Request editable logos, colors, fonts, guidelines, and old assets that should not be used.
CMS access
Optional access
Collect the access needed to review existing content and prepare launch work.
Content approval
Required approval
Name who approves final copy, imagery, testimonials, and legal or compliance text.
Workflow checklist
Use this to turn the advice into a repeatable client request.
Inventory
List every page that needs copy, imagery, or review.
A page-level inventory prevents vague requests and missed content.
Ownership
Assign each missing item to a client-side owner.
Clients move faster when responsibility is visible.
Quality
Define accepted file formats, resolution, and copy status.
This reduces unusable uploads.
Review
Check submissions before design or development depends on them.
Early rejection avoids late rework.
Approval
Confirm who can approve final content and launch changes.
Approval ambiguity is a common launch delay.
Make the request easier to complete
Small wording choices change whether a client sends useful material or another incomplete reply.
Do
- Ask for content by page, not as one general upload.
- Separate final copy from draft copy.
- Review image quality and usage rights early.
- Keep access requests outside ordinary content comments.
Avoid
- Let clients dump a folder without a checklist.
- Assume old website content is approved for reuse.
- Wait until build week to discover missing bios or testimonials.
- Treat content, access, and approvals as one task.
When the checklist becomes a portal
The same request becomes more reliable when every field has an owner, a status, and a place to submit it.
Each page can have its own copy, image, and approval request.
Clients can see which content blocks are still missing.
Your team can reject unclear copy or unusable images with context.
Practical questions
What website content should I collect first?
Start with the page list, homepage copy, service copy, brand assets, images, testimonials, team details, legal copy, and access details.
How do I stop clients sending content in pieces?
Give them a structured checklist with page-level requests, accepted formats, and visible completion status.
Should I collect content before design?
Collect enough content before design to understand structure and messaging. Final polish can happen later, but missing core content should not be a surprise.