Guest Post Guidelines (Write For Us)

If you’d like to write for you can use our contact form to message us or this email: ryan+ddt@mail131.

We are open to receiving guest post inquiries on a variety of different topics.

This site primarily focuses on resolving technology error codes, but there are a variety of relevant sub-domains including:

  • digital marketing,
  • SEO (search engine optimization),
  • information technology,
  • internet culture,
  •  personal computers and laptop software (including Macintosh Apple hardware),
  • tech news,
  • entrepreneurship,
  • make money online tips and case studies,
  • social media marketing,
  • WordPress plugins and themes,

Guest Posting Requirements

Article Quality: Articles need to be at the very least 800 words and ought to deal with the topic comprehensively. Incomplete articles with idiomatic errors that are half-baked and low-quality- we won’t publish them.

Quality takes priority when we decide whether to publish guest blogging submissions. To make certain your article gets published, create an extremely unique piece which is written especially for the readership. Credit: values individual work and if your content is derivative of somebody else’s work, go ahead and provide them with credit. The same applies to pictures which you use in your blog post. Make sure you provide credit where credit is necessary. Screenshots & Videos: Pictures speak a thousand words. Include images to share your message, but do not just add them just for the sake of it. If you’re creating tutorials, please take a screenshot. In case you are writing conversational topics, use Flickr to discover vibrant and relevant photos. Self-promotion: We permit legitimate contribution and will consider providing a backlink to your site so that our readers can get more information about the post you submitted. Copyright: We respect everyone’s work. In the event we discover out that you have duplicated a post from someplace else, you’re going to get an instant ban and we will remove all of your blog articles. Also, by submitting a post to, you provide us copyright ownership of the post. This will help us to handle any DMCA related problems.

Dealing With Comments: Comments are the discussions about your published article. Please answer any questions relevant to your article through the comments. This gives you more publicity and helps out both of our readerships.

Writing The Guest Post

If you’re interested in submitting ‘error code’ content, below we’ve outlined some general guidelines:

The Process

I’ll provide the error code keyword, you’ll Google it, and find different fixes. These fixes will often be buried in a forum, or be included in an article. I’ve even found some in YouTube comments section. Just dig around, find as many unique fixes as possible and rewrite them into a list format- plus always link to the source so it can be cited in the final article. (On the second page of this document I included a sample format for the finished content).

General Rules

  1. Include a “What Is It?” section that explains what the error is, citing your sources. And then list out a bunch of different fixes under separate headers with source URLs.
  2. Put the simplest fixes first (e.g., put “restart phone” above a fix that involves “removing the iPhone battery”) so users reading it can try the easiest solutions first.
  3. No duplicate fixes- each fix should be unique.
  4. When possible, list the relevant operating system, if applicable. For example, if one fix says that it applies to Windows 8, just specify that it works on Windows 8.
  5. Include step by step instructions when available- just do a light rewrite of the step by step so that it’s unique for SEO purposes.
  6. If the instructions are insanely detailed and long, or if there are multiple fixes with long step by step instructions, just do 1 or 2 of them (whatever makes sense given the word count), and just link to the other fixes
  7. Follow the output format on the second page (What a finished piece of content should look like)
  8. Always cite sources so it would look like this: “Over in the Microsoft support community ( , one of the top suggested fixes was…”. That way I can just add the URL into the finished Post.