... and web developers writing the content for the client can very quickly hit that pitfall. You're not an expert in their business, what business do you have writing THEIR copy?
Besides, If the client doesn't know what they want on their website, what the deuce do they want a website FOR?
Maybe, just maybe, having a website just to have one is a key problem causing clients to draw a blank on writing site content. Developers, having no problem selling clients a site without a purpose, might just have an even worse time figuring out what to write.
Hit-and-run billable is the problem in this case, not writing.
Who caused this problem? A client who doesn't know all there is to know about how and who to target with a web site? Or the developer, blithely ignoring anything to do with the communications part of web design?
Most content can be nailed down right at the client meeting, if the discussion shifts from gimmicks to a reason for the site to exist. If the developer doesn't have the content, they probably don't have a good idea of the target customer, or what the site was supposed to accomplish. That there is no clear idea of who the site is for troubles too many developers not at all.
Once again, what is the cause? Could it be a dysfunctional relationship with clients? If web shops had to figure out which of a dozen CMS systems to install, instead of one-size-fits-all, you'd see the same problems. If you had to be an expert in knowing ecommerce, rather than slapping in the singular shopping cart the programmer knows how to code, you'd see the same problem.
By the way, which cart software has superior human factors? Which cart software supports shopping behavior, not merely the transaction at the end? Which has a built in merchandising tool called a planogram? What, exactly, can be done with Zen cart to foster upsells and cross selling?
More to the point, how do you support effective product page copy with site code? How do you figure out when a user wants more information, and deliver just the right amount, at the right time, when you won't have a thing to do with copy?
In many cases, this might just be a follow-on to every other dimension of web development rather than anything to do with writing skill. In a disturbing number of cases, the refusal to have anything to do with writing is but one of a long list of refusals.
The reason for this is simple, reporters are generally not experts in the topic they cover... Which means if you can't trust them for what you know about, how can you possibly trust them on subjects you know nothing about?
Are web back on this fallacy ...again?!
You can have niche writers on call, who write on very narrow subjects with very good accuracy. Where a newspaper might have someone write off their normal beat, you can employ specialists.
Next are copywriters, who may not be experts but often specialize, so you assemble a stable of writers who hit the major subjects.