Website Content Production Benchmarks 2026: Time, Cost, Staffing, and Output

A website content plan can look easy in a spreadsheet. Twenty pages. Three people. Six weeks. Plenty of time.

Then the interviews slip, product claims need legal review, nobody owns the photos, and the homepage goes through seven rounds because five people are approving it against five different ideas of what “good” means.

That isn’t a writing problem. It’s a production problem.

This resource gives business owners, web teams, and agencies a defensible way to estimate the work. The benchmarks below come from current industry research, but they aren’t a promise that every 1,500-word page takes exactly the same number of hours. A technical service page built from original interviews is a different job from refreshing an existing FAQ.

Use the numbers as a starting range, then adjust for complexity, evidence, review risk, and the condition of the source material.

Website content production benchmarks at a glance

Sources: Orbit Media’s 2025 survey of 808 content marketers, Adobe’s survey of more than 1,600 marketers, HubSpot’s 2026 marketing statistics, and the Content Marketing Institute’s 2026 B2B research.

The first number deserves a warning. Orbit Media’s 3-hour-and-48-minute figure measures the time respondents spend on a typical article. A website page may also need a stakeholder interview, offer definition, search research, proof gathering, wireframe coordination, metadata, CMS entry, internal links, accessibility checks, and approval. Calling all of that “writing” hides most of the job.

A better way to estimate a website page

Estimate each page across six work stages:

1. Brief and research: audience, user intent, offer, source material, competitors, search demand, and required proof.
2. Subject-matter capture: interviews, call recordings, product documentation, customer questions, and sales objections.
3. Draft: page structure, copy, calls to action, title, description, and notes for visual assets.
4. Review: factual review, brand review, compliance review when required, and one consolidated set of comments.
5. Production: CMS entry, image placement, internal links, structured data, forms, and responsive formatting.
6. Quality assurance: proofreading, links, form tests, mobile checks, accessibility basics, analytics, and final sign-off.

This model prevents one common estimating mistake: assuming the person writing the page controls the entire schedule. They usually don’t. A draft might take half a day and then sit in an executive’s inbox for a week.

Practical hours by page type

The following are planning ranges, not survey findings. They are a workload framework derived from the stages above and anchored to Orbit Media’s current article-production benchmark.

Why separate active hours from elapsed time? Because production capacity and calendar duration are different. Six people can touch a page without adding six full days of active work, yet their handoffs can stretch a one-day task across two weeks.

The capacity calculator

Use this equation before committing to a launch date:

Monthly page capacity = available production hours × focus factor ÷ average hours per page

The focus factor accounts for meetings, support work, email, internal coordination, and work that arrives unexpectedly. A full-time employee has roughly 160 scheduled hours in a four-week month, but using 160 as content capacity is fantasy. For a person whose job includes meetings and other marketing work, a focus factor of 0.45 to 0.65 is a reasonable planning assumption. For a dedicated contractor working from approved briefs, it may be higher.

Suppose a marketing manager can reserve 48 hours per month for website content. A writer has 72 hours, a designer has 24, and a web producer has 30. Don’t add them into one 174-hour pool. Calculate capacity at each constrained stage.

If a standard service page needs three manager hours, eight writer hours, two designer hours, and two producer hours, the theoretical capacities are 16, 9, 12, and 15 pages. Writing is the constraint, so the team’s maximum is nine service pages per month. After allowing room for revisions and unusual pages, committing to six or seven would be safer.

That is the difference between resource planning and wishful thinking.

How long should a website content project take?

Page count isn’t enough to answer this. A 30-page brochure site assembled from approved copy may move faster than a 10-page site that needs new positioning, executive interviews, photography, and regulated claims.

Still, teams need a starting point. These project ranges assume one accountable owner, scheduled interview access, consolidated feedback, and no major repositioning after drafting begins.

Add time when customer approvals, translations, regulated review, original photography, or data migration sit on the critical path. Subtract time only when the inputs are genuinely ready: an approved message strategy, named page owners, usable source documents, available experts, and a final decision-maker.

Adobe’s research explains why schedules feel tighter even when teams get faster. Among more than 1,600 marketers, 96% said content demand had at least doubled over two years and 62% said it had risen fivefold or more. Faster drafting doesn’t solve a demand increase of that size. Teams need to reduce duplicate work and build content that can be reused.

The approval tax

Approval delay is usually invisible in the estimate because nobody wants to assign a cost to waiting. But waiting consumes calendar time, creates context switching, and can force designers or developers to redo work built against an old draft.

Adobe found 31% of marketers name lengthy manual approvals as a barrier and 33% cite siloed collaboration. Those are operating-system failures. Another writing tool won’t fix them.

Use one content owner for each page and one final approver for each decision category. A technical reviewer should verify facts. A legal reviewer should assess legal risk. A brand reviewer should protect agreed voice standards. None of them should reopen the business strategy unless the underlying brief is wrong.

Set a review window before drafting begins. Two business days may work for a standard page. A regulated case study may need a week or more. If a reviewer misses the window, the project owner should know whether the page advances, pauses, or escalates. Silence can’t remain an unofficial workflow state.

Consolidated feedback matters too. Three reviewers leaving contradictory comments in three tools creates revision work that adds no customer value. One owner should reconcile those comments before they reach the writer.

What AI changes, and what it doesn’t

AI has already changed production economics. In the Content Marketing Institute’s 2026 B2B study, 87% of marketers using AI for content creation said it improved productivity. The same research reports that 45% plan to increase spending on AI tools in 2026.

That makes AI part of a normal content workflow, not a side experiment. It can organize interview transcripts, compare a draft with a brief, propose page structures, generate metadata options, flag inconsistencies, and create variations for human review.

It does not know why your best customer chose you unless you give it the interview. It cannot verify a product tolerance, customer result, warranty term, or legal claim by instinct. It also tends to smooth specific language into the same polished mush found on thousands of other sites.

The useful metric isn’t “pages generated.” Track accepted output. If AI cuts first-draft time by two hours but adds three hours of fact checking and rewriting, it didn’t increase capacity. Measure the time from approved brief to approved page, the number of review rounds, factual corrections, and post-launch performance.

Build a website content production scorecard

A useful scorecard needs only a few measures. Track them by page type so a homepage isn’t compared with a minor FAQ update.

• Cycle time: business days from approved brief to approved page.
• Active hours: hands-on time by role, including revisions and production.
• First-pass acceptance: percentage of drafts approved without structural rewriting.
• Review rounds: consolidated revision cycles before approval.
• Approval wait: business days spent waiting for a decision.
• Evidence coverage: percentage of important claims supported by a source, example, testimonial, specification, or demonstration.
• Post-launch result: qualified conversions, assisted conversions, organic entrances, engagement, or another metric tied to the page’s job.

Don’t turn the scorecard into surveillance. Its purpose is to reveal system constraints. If approval wait rises for every page, the writer isn’t the problem. If technical pages need repeated factual corrections, the brief or subject-matter review is weak. If production hours rise after approval, design and copy may be getting coordinated too late.

A reusable planning framework

Before work starts, classify every planned page by four factors: complexity, evidence, review risk, and source readiness.

Complexity measures how hard the offer or subject is to explain. Evidence covers the proof that must be found or created. Review risk accounts for the number and type of required approvals. Source readiness tells you whether the team has useful inputs or only a page title.

Score each factor from one to three. A simple contact page with approved details may score four. A technical service page that needs an engineer interview, customer proof, and compliance approval may score 11 or 12.

Then sort the backlog into three production classes:

This simple classification is more honest than assigning every page the same due date. It also helps an agency explain why two pages with similar word counts can have very different costs.

Where teams lose the most time

Content teams often try to save time at the drafting stage because it is visible. The bigger losses happen earlier and later.

Poor briefs send writers searching for an offer that the business hasn’t defined. Unscheduled expert access stops research. Drafts move into design before claims are approved. Reviewers edit for personal taste instead of an agreed audience and objective. Finished pages wait for images, form routing, analytics, or CMS access.

Orbit Media’s survey shows a typical article takes 3 hours and 48 minutes to produce. If your standard page takes three weeks to approve, shaving 30 minutes from drafting won’t materially change delivery. Fix the queue.

Start by recording the date each page enters and exits every stage. After one project, you’ll know whether your constraint is research, writing, review, design, production, or QA. Then make the next investment against evidence.

Frequently asked questions

How many website pages can one writer produce per week?

For new, evidence-based service pages, two to four approved drafts per week is a defensible starting range. A writer may draft more when briefs and source material are ready, but interviews, research, revisions, and coordination reduce output. Use the stage-based capacity formula instead of treating word count as the whole job.

How much time should subject-matter experts expect to spend?

Plan 45 to 90 minutes for an initial interview on an involved page or closely related group of pages, plus 20 to 45 minutes for factual review. Technical, regulated, or research-heavy content may need more. Recording one strong interview and reusing it across related pages is usually more efficient than sending repeated email questions.

Should content be finished before web design starts?

Strategy and representative content should start before detailed design, but every final page doesn’t need to be complete first. Designers need real headlines, proof, calls to action, content hierarchy, and examples from major page types. Work can then continue in parallel if copy and design share a component plan and neither team treats placeholders as approved content.

What is the best benchmark for content quality?

There isn’t one universal quality score. A page succeeds when it performs its assigned job with accurate, useful, differentiated information. Pair production measures such as acceptance rate and revision rounds with an outcome such as qualified leads, completed bookings, sales-assisted use, or organic discovery.

How often should these benchmarks be updated?

Review internal production data after each major project and update planning assumptions at least twice a year. External benchmarks give you a starting point. Your own cycle time, approval delay, and outcome data should become the stronger guide once you have enough consistent observations.

Turn the benchmark into a workable plan

The main lesson is simple: don’t estimate website content as words divided by typing speed. Estimate the system. Count research, expert access, evidence, review, production, QA, and waiting time. Find the constrained role, reduce unfinished work, and judge AI by accepted output rather than draft volume.

If you need a website plan built around real capacity and business outcomes, talk with Your Web Team.