How to Get Website Content from Clients (Without Chasing Them for Weeks)

The fastest way to get website content from a client is to stop asking for "the content" and instead give them a structured, page-by-page template with a hard deadline, a contract clause that ties the launch date to delivery, and one single place to submit everything. Clients are not lazy. They just have no idea what you need, in what format, or by when, so they put it off until it becomes a problem that is suddenly yours.

The problem: the site is done, the content is not

You know this one. The design was approved two weeks ago. The build is finished. The staging site looks great with its lorem ipsum and its stock photos. And the client still has not sent a single real word.

Here is how it usually plays out. You send an email in week one: "Please send me your texts and images." Silence. You follow up in week three. The client replies with a 14 MB Word document called "Website text FINAL v2", plus a WhatsApp message saying the "about us" text is "somewhere in my Dropbox". Two days later, a different person on their team sends photos as WhatsApp screenshots, compressed to the size of a postage stamp. The owner's nephew "who is good with computers" suggests that the homepage headline should be changed. Then the real text arrives, but it was written for a brochure from 2016 and it is 1,800 words long for a page that has room for 120.

Meanwhile, your launch date is slipping. Not because of anything you did, but you are the one who has to explain to the client why it is slipping. And the project you quoted at 40 hours is now at 55, because you are chasing, reformatting, rewriting, and resizing.

This is one of the most common reasons freelance projects run late, and it almost never shows up in the contract. Designers write clauses about revisions and payment, but rarely about content delivery. The result: the client treats content as a "when I get to it" task, and you carry the schedule risk.

The fix is not working harder at chasing. It is changing what you ask for, how you ask, and what happens if the answer does not come.

How to get website content from clients: 7 steps

1. Collect content before you design, not after. Ask for the real headline, the real services list, and the real team bios during the discovery phase. Designing around lorem ipsum guarantees that the layout will break when the real text arrives.
2. Send a page-by-page content template, not a vague request. For each page, list exactly what you need: headline, subheadline, body text with a word range, images with minimum dimensions, and one call to action. Clients fill in a form far more reliably than they write an essay from scratch.
3. Give every item an owner and a date. "Content" is not a task. "Marta sends the three service descriptions (max 80 words each) by Friday 14 March" is a task. Put names and dates on every line.
4. Tie the launch date to content delivery in your contract. Add a clause stating that the launch date assumes all content arrives by a specific date, and that every week of delay moves the launch by at least a week and may trigger a rescheduling fee.
5. Use one submission channel and refuse the rest. Pick a shared folder or a single form. Politely redirect anything that arrives via WhatsApp, a second email thread, or a USB stick.
6. Offer to write it, but price it separately. If the client cannot or will not write, copywriting is a paid add-on with its own scope. Do not absorb it silently.
7. Review content in context, on the real site. Once the text is in, share the staging link and let the client approve copy where it lives, with pinned comments instead of a 9-message email thread.

Each of these steps closes a specific gap. The sections below go deeper on the three that matter most: the template, the contract clause, and the review.

Why clients fail to deliver content (and it is not laziness)

If you understand why content stalls, you can design the process around it.

They do not know what "content" means. To you, content is a set of headlines, body text, and optimized images. To a client who runs a plumbing business, "content" is a vague homework assignment that sounds like writing a book. The word itself is intimidating. Ask for specific things instead: "a two-sentence description of each service" is easy. "Website copy" is not.

They are doing it on top of their real job. Your project is a priority for you. For them, it is the fourth item on a list that starts with customers, invoices, and staff. Content tasks are the first to slide because they feel open-ended and nobody is waiting on them yet.

They are afraid of getting it wrong. Writing about your own business in public is uncomfortable. Many clients delay because they want the text to be perfect, and they have no one to tell them it is good enough. This is where a rough first draft, or a short interview you turn into copy, can unblock a stuck project.

They have no deadline with consequences. If nothing bad happens when content is late, nothing gets done. A launch date that "moves automatically" when delivery slips gives the client a reason to care. It is not a punishment. It is just honesty about how the schedule works.

Decisions are spread across several people. The owner approves, the office manager sends files, and the marketing intern has opinions. Nobody knows who owns what. Naming a single point of contact on the client side removes a surprising amount of delay.

Building a content template that clients actually fill in

A good template is boring on purpose. It should feel like a form, not a creative brief. Here is what to include for each page.

• Page goal: one sentence. What should a visitor do after reading this page?
• Headline and subheadline: with a character limit, such as 60 and 120 characters.
• Body text: with a word range, for example 100 to 150 words per section.
• Images: how many, minimum width (say 1600 px), and acceptable formats. State clearly that screenshots and photos taken from a social media feed will not work.
• Call to action: the exact button text and where it links.
• Notes: a free field for anything the client wants to mention.

Add a column for status: "Not started", "Draft", "Final". It gives the client a sense of progress and gives you a quick overview without writing a single follow-up email.

Two details make a big difference. First, show an example. Fill in one page of the template with fake but realistic content so the client can see the level of detail you expect. Second, keep the first deadline small. Ask for the homepage first, within a week. A quick win builds momentum for the rest.

If the client's content is thin, offer a 30-minute call where you ask them questions and take notes. People who cannot write three sentences about their business can usually talk about it for half an hour. You then turn the recording or notes into a draft and send it back for approval. Bill that call as the content workshop it is.

The contract clause that protects your schedule

Most delayed launches are not a content problem. They are a contract problem. If your agreement says nothing about content delivery, the client is allowed to assume that "the site is ready when the designer says so".

A simple clause covers it:

The launch date of [date] is based on receiving all required content (texts, images, logos, and access credentials) by [date]. If content is delivered later, the launch date will move by an equal period, and the project may be rescheduled depending on availability. Content that is incomplete or does not meet the agreed specifications counts as not delivered.

Add two optional lines. One: if content is more than 30 days late, the final payment milestone becomes due regardless of the launch status. Two: copywriting, image retouching, and content migration beyond the agreed scope are billed at your hourly rate.

You do not need to sound aggressive. Present it as a scheduling note: "This is what makes sure I can hold the date I promised you." Clients rarely object, because the logic is fair. And if you are still working on your contract language, our guide on what to include in a web design contract covers the other clauses worth having.

Reviewing content on the real site

Once content arrives, you hit the next trap: approval. Content that looks fine in a Word document often looks different on a page. A 12-word headline wraps onto three lines. A team photo gets cropped at the worst possible spot. The client sees it for the first time and wants to change things, and you get feedback in five different places.

The cleanest approach is to review copy where it lives. Put the text into the staging site, send the link, and ask the client to comment directly on the page. With a tool like dotts, they click on the exact headline that bothers them and write what they want changed. No login, no account, no screenshots with red arrows. You see the comment pinned to the element, with the browser and device details attached, so "the text is cut off" arrives with enough context to actually reproduce it.

That matters for content specifically, because content feedback is usually tiny and specific: a typo in a service name, a phone number with a wrong digit, a sentence the owner wants to soften. Those are the worst kind of changes to handle over email, since each one needs a location and a quote. Pinned comments carry both automatically. If you want a deeper look at keeping this part of the project under control, see our guide on the web design revision process.

One more habit worth adopting: set a rule that content changes after sign-off count as a new revision round. Say so up front, and say it again when you send the review link.

A real-world example: Anna and the dental practice

Anna is a freelance web designer in Hamburg. She was building a six-page website for a dental practice, quoted at 35 hours and a fixed price. Her first two projects of the year had both slipped by about a month because of late content, so she changed her process for this one.

Before (her old way): After the design was approved, Anna sent one email asking for "all texts and photos". Three weeks later she had a Word document with the practice history, a folder of 40 phone photos, and a message from the receptionist asking whether the dentist's holiday card could be the homepage image. Anna spent about 12 hours reformatting text, resizing images, and writing the missing service descriptions for free. Launch slipped by five weeks.

After (the new way): At kickoff, Anna sent a content template with seven rows per page, a word range for each text, and a deadline of two weeks after design approval. She named the practice manager as the single contact. Her contract included the launch-date clause. She also offered a 45-minute interview for the dentists, priced at 150 euros, which they accepted for the treatment pages.

The practice manager delivered the homepage text in four days, because it was a small, clear task. The rest followed over two weeks. Anna dropped the final text into staging, shared the link with dotts, and the practice manager and the two dentists left comments directly on the page. Eleven comments in total, all in one place, no login required. The dentists approved the site in two rounds.

Total time on content-related work: about 4 hours, down from 12. The site launched on the planned date, and Anna got a Google review that mentioned how "organized" the process was. The template did not make the client smarter. It made the job smaller.

Bottom line

Late content is a process problem, not a client problem. Collect it early, ask for small specific pieces, give each piece an owner and a date, and write the consequences into your contract. Then review the text on the real site so feedback stays in one place. Do those four things and you will launch on time far more often than not.

FAQ

How do I get website content from a client who keeps missing deadlines?

Break the request into small, specific tasks with named owners and short deadlines, and send a reminder two days before each one. If deadlines still slip, point to the contract clause that moves the launch date and offer a paid content workshop as an alternative. A client who sees a clear consequence usually responds within days.

Should I collect website content before or after the design?

Before, or at least in parallel. You do not need every word, but you need the real headlines, the real number of services, and the real image formats. Designing with placeholder text often leads to layouts that break once actual content arrives, which costs you rework hours.

What should I do if my client cannot write their own website copy?

Offer a structured interview and turn the answers into a first draft, or recommend a freelance copywriter. Either way, treat it as a separate paid item. Writing copy for free quietly turns a 35-hour project into a 50-hour project.

How long should I give a client to deliver website content?

Two to three weeks is a realistic window for a small business site, split into smaller deadlines (for example the homepage in week one). Longer windows tend to get used in full. Tie the final date to your launch date so the dependency is visible.

What file formats should I ask clients to send?

Ask for text in a shared document or form, not inside emails or images. For photos, request original files (JPG, PNG, or HEIC) at a minimum width of 1600 px, never screenshots or social media downloads. For logos, ask for SVG or a high-resolution PNG with transparency.

What if the client sends content after sign-off?

Treat it as a new revision round, as agreed in your contract. Late content changes are the most common source of unpaid scope creep, so state the rule when you send the review link and remind the client once more before launch.

How can clients review website content without confusing feedback?

Share the staging link and let them comment directly on the page, so each change request is attached to the exact element. With dotts, clients click anywhere on the site and leave a pinned comment without creating an account, which keeps all content feedback in one place instead of scattered across email and WhatsApp.

Is a content template really worth the effort for small projects?

Yes. Building it once takes about an hour, and you reuse it for every project. Even a one-page version with headline, text, and images per page prevents the vague "send me your content" email that causes most delays.

Stop chasing content and start collecting feedback in one place. [Try dotts free →](https://dotts.se)

Further reading

• Web Design Contract Template for Freelancers: What to Include and Why
• Client Onboarding for Freelance Web Designers: The Complete Guide
• Web Design Revision Process: How to Manage Client Revisions Without Losing Control
• Scope Creep in Web Design: How Freelancers Stop It (Before It Eats Their Evenings)