How to collect website content from clients, one page at a time

To collect website content from clients, turn the agreed sitemap into one request per page, say exactly what each page needs and in what form, and give each page its own due date and its own done state. A client can finish “the Contact page” on a Tuesday evening. A client cannot finish “send us your website content”, so they don’t start. The rest of the work is checking each page the day it arrives and asking for the one missing piece, not the whole set.

Most advice on how to collect website content from clients is about behavior. Educate the client. Put a deadline in the contract. Charge a late fee. Those help, and they are covered below. What they leave out is the shape of the request itself, and the shape is what decides whether a busy owner can make progress in the twenty minutes they have between other jobs.

Why are clients not sending website content?

Because the request is too big to start. “Send us your copy and images for the new site” asks a dentist, a plumber, or the marketing lead at a small firm to write a dozen pages, find the logo files, choose photos, and gather team bios, all at once and with no picture of what “done” looks like. They put it off, the way anyone puts off a task with no clear first step.

Web people have known this for a long time. Pepi Ronalds wrote in A List Apart in 2008 that content “is often the last thing to be considered (and almost always the last thing to be delivered).” Sixteen years later Eric Karkovack, writing on Speckyboy about why web design projects come to a standstill, made the same point: content “is often the last piece of the puzzle”, and the designer can’t go on until it arrives. When Atarim asked people at one of its own coaching sessions how they gather website content, 74% said it was hard and 86% said they used more than one tool to do it. That was a self-selected group of Atarim users, not a market survey, but nobody who has run a web project will be surprised by it.

In a stalled project, the reasons are usually some mix of these:

• The client is writing about their own business for the first time and does not know where to begin.
• The request did not say how long each piece should be, so the client writes a page and a half for a section with room for two sentences, or one line for a page that needs four hundred words.
• Content is spread across people. The owner writes the About page, a partner has the team photos, the office manager has the opening hours and the old logo files.
• The client sent something, but into an email thread, a shared drive, and a text message, and nobody on either side knows which pieces are still missing.
• The client thinks they sent it all. The agency thinks half is missing. Both are partly right.

Only the first of these is about the client’s motivation. The other four are about how the request was built.

When should you ask for website content?

Ask in two waves. The first wave goes out at kickoff and covers facts the design depends on: the list of services, the team members, office locations and hours, the logo in its original format, brand colors, and any photos the client already owns. These are things the client has, not things they must write, and the designer needs them to build a wireframe that fits the real business.

The second wave is the written copy, and it goes out after the client has approved a sitemap and a wireframe. Atarim’s guide makes the same call. It says asking for content at project start is a mistake, and that clients write better copy once they can see the layout and how much text each section holds. A client who can see that the hero has room for eight words and one sentence under it writes eight words and one sentence. A client staring at a blank Google Doc writes an essay.

The two-wave split also gives the agency an early warning. If the first wave, which only asks for things the client already has, takes three weeks, the copy will take longer. That is the moment to talk about scope and dates, not week nine.

How to collect website content from clients page by page

The core change is to stop sending one big request and send one small request per page of the sitemap. Each page becomes its own item with its own owner, due date, and done state. The client sees a list like this:

• Home page: headline, one paragraph under it, three short service summaries. Due Monday.
• About page: two paragraphs on how the business started, one photo of the owner or the team. Due Wednesday.
• Services: one entry per service, each with a name, two to four sentences, and a starting price if you show one. Due Friday.
• Team: name, role, a two-line bio, and a headshot for each person listed. Due next Monday.
• Contact: address, phone, email, opening hours, and whether to show a map. Due next Monday.
• Logo and brand files: original vector logo, color codes, fonts if licensed. Due this Friday.

Each line can be finished on its own. The owner can do the Contact page in five minutes on a phone at lunch, and the progress is real: one item moves to done. Small finishable steps are what a busy person starts. A dozen open items with one done is a better place to be than a single “website content” task at zero percent.

Splitting by page also lets you split by person. The Team page goes to whoever has the photos. The Services page goes to the owner. The Contact page goes to the office manager. Each person sees only their own items, and nobody waits for anyone else to finish before they can start.

Last, page-level requests let the build go on. The developer can lay out the Contact and Team pages with real content while the client is still working on Services. A site built page by page as content lands keeps moving. A site where every template waits for the last paragraph sits idle until that paragraph shows up.

This is the website content collection process in one line: the sitemap is the request list. If a page is on the sitemap, it has a request. If it has no request, nobody will write it.

What does a per-page content request contain?

A good request for one page answers every question a client would otherwise send back by email. It has five parts.

Name the page in the client’s words. “About us” rather than “brand narrative.” “The page that lists your services” rather than “service taxonomy.”

List each section and its length. “Headline, up to 8 words. Paragraph under it, 2 or 3 sentences. Three service summaries, 1 sentence each.” Lengths are the most useful thing you can give a non-writer, because they turn “write the home page” into “write eight words.” If you have a wireframe, attach a screenshot of the page with the sections labelled.

Give an example or a prompt for each section. A prompt like “What does a new customer usually ask you on the first call?” gets better copy than “Write an intro paragraph.” Speckyboy’s piece suggests the same thing: prompts and templates for clients who struggle to write, or an offer to write it for them.

Say what form the answer takes. For copy, a text field per section is best, because each answer lands in the right slot and there is no file to lose. For images, say the file type, the size you need, and how many. “One headshot per person, at least 1,000 pixels wide, JPG or PNG, face centered with some space around it.”

Give a due date and a fallback. “Due Wednesday. If you would rather we draft this page from a 15-minute call, tell us and we will book it.” A fallback written into the request turns a stall into a choice.

The request email itself, the one that delivers the link to these items, can be short. The document request email templates page has wording that works for a first ask and a follow-up, and the structure carries over from client files to website pages unchanged.

Which files should clients send for a website?

Copy is the slow part, but files cause the most back and forth. Ask for each file by what it is and what you need it for, and say what a usable version looks like.

The logo is the classic one. Ask for the original vector file, which is usually an SVG, EPS, AI, or PDF from whoever designed it. Most clients do not know what that means, so say where it is likely to be: “The file your designer sent you when the logo was made, or the one your printer uses for business cards.” If nobody has it, a large PNG with a transparent background is the fallback, and a screenshot from the old website is not.

Photos come next. Ask whether the client owns them. Photos pulled from a search engine or a competitor’s site are a copyright problem the agency will inherit. For photos the client takes, say what you need: landscape for the header, square for team headshots, taken in daylight, not cropped tight. Phone photos are fine if they are sharp at full size. The same problem shows up in every kind of client upload, and the page on clients who send blurry phone photos covers what to ask for and how to reply when one comes in unusable.

Brand colors and fonts are usually a short text answer, but ask for the codes, not the names. “Our blue” is not a color. If the client has a brand guide, ask for the PDF. If they use a paid font, ask for the license or the name of the account it was bought from.

Legal and policy text, such as a privacy policy, terms, or industry disclosures, needs its own item with its own owner, often someone outside the core team. It is short and it is the item most likely to hold up a launch, because nobody thinks of it until the last week.

How to get content from clients on time without a contract fight

The contract is still the backstop. In the SitePoint thread on getting a website’s content from the client, one reply advises being “very specific in the contract” about who delivers what and how many revision rounds there are. That is good advice, and the per-page list makes it easy to follow, because the list can go into the contract as an appendix. “Client provides the items on the attached content list by the dates shown” is a clause both sides can check.

What the contract should also say is what happens on the date if a page is still missing. Pick one of these and write it down:

• The site launches on the agreed date with the finished pages, and the missing pages go live when the content arrives.
• The agency drafts the missing pages from a short call and the client edits, billed at a stated rate.
• The project pauses, and the build slot moves to the next opening in the schedule.

Any of these is fair if the client agreed to it at the start. None of them works if it is a surprise in week ten.

Beyond the contract, three habits get content from clients on time more than any clause.

Send the first request within a day of kickoff, while the client is still excited about the project. Every week of delay in sending the list adds a week of drift on the other side.

Follow up on the single item that is overdue, not the whole list. “The Team page photos are due today, the rest is on track” gets a reply. “Just checking in on the content” does not.

Send reminders where the client reads them. An owner who ignores email for days will often reply to a text within the hour. The comparison of SMS and email for document requests lays out when each one works better, and the same split holds for website content.

What should the website content collection process track?

Track each page, not the project. For each item on the list, you need to know four things: who owes it, when it is due, whether it has arrived, and whether what arrived is usable.

The last two are not the same. A Services page that arrived with three of the six services filled in has arrived but is not usable. A logo that arrived as a 200-pixel JPEG has arrived but is not usable. A tracker that only knows “received” will tell the agency the content is in when the build is about to stall on it. Check every item the day it lands, while the client still remembers writing it, and send back the specific gap: “Thanks for the Services page. Four of the six are done. Could you add the two-sentence description for Emergency repairs and Maintenance plans?”

A shared spreadsheet can do this for a small site if one person keeps it up. The trouble is that the spreadsheet lives with the agency and the content lives in email, so someone has to copy status across by hand, and that is the step that gets skipped. Whatever you use, the client should see the same list the agency sees, with done items marked done, so neither side argues about what was sent.

At the end, get a sign-off. Once every page is usable and laid out on the staging site, ask the client to confirm the content is final. A short written approval saves the “can we just change the About page” email the week after launch from turning into a free rewrite.

What if the client still does not send the content?

Some clients will not send content, however good the request. The owner is busy, the business is in a bad month, or the person who wanted the website has left. When a page is two weeks past due and two follow-ups have gone unanswered, stop sending reminders and change the request.

Make the item smaller. “Write the About page” becomes “Answer these three questions in a text reply: when did you start, why, and who works with you now.” The agency turns the answers into copy.

Offer a call. Fifteen minutes on the phone, recorded with permission, gives a writer enough for most small pages. Many owners who will never write a paragraph will talk for twenty minutes about their business.

Use the fallback in the contract. If the agreed date has passed, launch with what is ready or write the page for the agreed fee. The time an agency spends chasing is real money, and the article on the hidden cost of chasing clients for documents adds it up.

Each of these moves gives a busy person something they can finish today. Content gathering for web design clients works the same way at every step: the smaller and clearer the ask, the sooner it comes back. The same per-client list carries over to brand kits and campaign assets, which the page for marketing agencies covers.

Where zendoc fits in document collection

zendoc lets an agency build the per-page content list once as a workflow template, with a step for each page holding the text fields and file uploads it needs, and spin up a copy for each new client. The client gets one link by SMS or email and opens their own list on a phone with no password and no signup form, and the agency sees each step’s completion as it happens. Every upload is read on arrival by AI that flags a wrong-type or unreadable file as a suggestion for staff to review, and one grouped reminder goes out three days after the first notice for whatever is still open. Pricing for the one plan is on the pricing page.