Last one in, best one in, right? So, when something goes wrong, the most cursory of ‘explanations’ tends to surface, written by whoeverblames no other than themselves for the error state. In these instance, there tends to be little to no step directed at the user, meaning sites are coated with pictures of broken cartoons as their equivalent excuse for server failure, and that awkward, accusatory last step looking for the user’s permission typically unauthorized and perhaps incorrectly executed.
In about fifteen words, the reader just wants to know what happened, if it is their fault, and what they can do about it. Everything else is just ornamentation for a bad moment.
An error conversion page allows the user to continue to the next step rather than having to leave the page. In order to achieve this, a proper diagnosis and offer of a remedy is required. An error conversion page is useful because instead of telling a user the server went down and that you already know, you have the opportunity to provide them with something that went wrong along with next steps on how to proceed.
Copying an error message generates a joke about robots and a link that returns you to the homepage. Text copied in the process includes text describing the technical status. So, users are informed about an upstream gateway or a malformed request. Neither of these helps and the latter leaks more to the user about your stack than you intended.
Your voice should stay recognizable but should be more on the quieter side. The writer walks the reader through the individual statuses, such as the case for a server failure, forbidden, an expired session, maintenance, being rate limited, and payment declines, as each of these statuses has different causes and different solutions. One singular, general message is what causes the problem.
Give the status codes and states list your stack produces, and what support people say happens for each. Delivery will be keyed in sets, rather than pages. So, each state can be wired to its own message, with a default written for anything else that is unhandled.
One rate, whatever the format: $10 per 100 words. You are paying for the writer’s time and judgement, so the price scales with the words rather than with a package tier.
| Typical error-page copy | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Core error states | 100 | $10 | $0.10 | $10.10 |
| Error set: 404, 500, 403, maintenance | 250 | $25 | $0.25 | $25.25 |
| Full error and edge-state copy | 500 | $50 | $0.50 | $50.50 |
The writer receives 100% of the writing price. Our 1% fee is added on top of it, and 0.5% is donated to tree planting. Full pricing breakdown.
We match the brief to a writer who has already worked in that subject area. If you have worked with an Articled writer before and want them again, name them and we will check their availability first.
Fill in the order form with your brief and email address. No account needed. You get a confirmation by email, then the finished piece as a document within 3 days.
Something is only funny if the cost is free. Humor fails for lost payments, and more importantly, for lost writing. A playful brand is a fun tone. A playful brand should not end there with a single joke. Unfortunately for the single-joke writers, nothing beats a funny closing statement except a statement with depth. Gaddoleen!
Most sites need four to six error messages and some kind of fallback: not found, server error, forbidden, session expired, and possibly maintenance and rate limited message, if running an API. Writing thirty is overkill and writing one and reusing is the most common failure.
Completely. Copyright transfers to you on delivery, with no attribution requirement and no licence back to us. Nothing written for you is resold, repurposed or republished.
Reviews from completed, paid orders in this category.
Body copy was spot on, but hero headline was off. It explained who we are, rather than what we do for the customer. Perfect in the second attempt. Two rounds are included, so it was free, just a day’s wait.
I gave them 400 support emails and said to grab 20 pertinent questions. I got 18 questions in return and an explanation as to why the other two were the same question. That explanation turned out to be really helpful in resolving tickets.
Writing case studies with customer sign-offs is the most challenging part of my job. This time, I wrote sections in a customer sign-off note. I sent one email instead of four. Case study sections remained approved as is.
We do not ask you to take the no-AI promise on trust. Each draft is run through these platforms and the reports are attached to your delivery email.
Originality.aiAI detection + plagiarism
GPTZeroAI detection
TurnitinAI detection + similarity
CopyleaksAI detection + plagiarism
Winston AIAI detection
ZeroGPTAI detection
SaplingAI detection
Content at ScaleAI detection
Send the brief, get a human draft back within 3 days. No account, no subscription, no AI.
$10 per 100 words · all of it to the writer · 0.5% to trees