<center>![Oracle-D-guide](https://files.steempeak.com/file/steempeak/daan/Y93RNt7w-Oracle-D-guide.png)
</center><center><sub>[Oracle-D is a registered trademark](https://oracle-d.com/tos/)</sub></center>

---

When I was checking out some of the recent entries for the Oracle-D State of the DApps task, I noticed that some people were not exactly following the guidelines that are explained in [Oracle-D's general guidelines video](https://www.youtube.com/watch?v=_5N-HSM0TIs&feature=youtu.be). It's really in your best interest to adhere to those guidelines as best as possible, since doing so will greatly improve your chances to get a high rating from the Oracle-D reviewers. 

While I'm not exactly an authority on the Oracle-D platform, I have [won their previous task](https://steemit.com/social/@dapplovers/announcing-the-winners-of-review-a-social-dapp-contest-ft-state-of-the-dapps), which was sponsored by State of the DApps. Keep in mind that I had never even participated with an Oracle-D writing task before. 

The main advantage that I had over other competitors, was that I had watched the Oracle-D guidelines video around 3 times in a row. I think that I know fairly well what Oracle-D is looking for when they review writing task entries and it's really not that hard to adjust your writing to have a better chance at getting a positive review. 

---

## Keywords Keywords Keywords

Paying close attention to the keywords you use within your article and especially in links is absolutely necessary. Oracle-D has guidelines about the use of keywords in each task. You should really try to incorporate those keywords as naturally as possible, in a way that doesn't make them stand out among the rest of your content. 

You've probably come across the term *long tail keywords* in some of the Oracle-D tasks. These are specific sets of keywords that are grouped together, for which people are looking for when they use search engines. You should always try to use these long tail keywords for links. Again, you want to use them in a way, so they don't disrupt the flow of your article. 

Here's an example of how I incorporated long tail keywords into my [winning article](https://steemit.com/partiko/@daan/meet-partiko-the-social-media-dapp-of-the-future): 

<center>![oracle-d-keywords](https://files.steempeak.com/file/steempeak/daan/hSevhA09-oracle-d-keywords.png)</center>

Mind you, this isn't perfect, there's still some room for improvement. The links could have been a bit shorter and they could have focused more on high-quality keywords. I am pretty happy with how I've incorporated that last link into the story, that specific sentence was in the task requirements. 

Also keep in mind that you should use keywords sparsely, most search engines notice when you spam certain keywords throughout your article. **Make sure that you try to incorporate important keywords in your main title, subtitles (headers) & links!** 

---

## Image Alt Text, Titles & Sub Text

Correctly tagging and naming your images is a must. The website or service you're writing about will see great benefits if you always give your images an appropriate title and alt text, again, pay close attention to the keywords you're using. 

<center>![Oracle-d-images](https://files.steempeak.com/file/steempeak/daan/WV3ffUUv-Oracle-d-images.png)</center>

Sometimes, it might be a good idea to also put a subtext under an image. In the case of my latest entry for the most recent [State of the DApps task](https://steemit.com/social/@dapplovers/3vf52x-review-a-social-dapp-and-earn-rewards-ft-state-of-the-dapps), I opted to include a screenshot from the State of the DApps website and accompany that screenshot with an appropriate subtext. 

<center>![oracle-d-image-subtext](https://files.steempeak.com/file/steempeak/daan/zCMqB9JI-oracle-d-image-subtext.png)</center>

As you can see, you can easily add a subtext by using the HTML element `<sub>`. 
Using this element will give you this result: 

<center>![Image-subtext](https://files.steempeak.com/file/steempeak/daan/i7Pz4zhz-Image-subtext.png)</center>

I personally use the free & open-source application ShareX to take precise screenshots of websites or other applications. This screenshot tool allows me to quickly edit, add image effects & rename images. All screenshots in this article were made with ShareX. 

#### [Check out my guide on how to use ShareX](https://steemit.com/utopian-io/@daan/the-best-open-source-screen-capture-tool-capture-edit-and-upload-screenshots-with-sharex-8f89f85faacd5est)

---

## Do NOT Mention Oracle-D or Other Projects

This is one mistake I see many people make. The Oracle-D guidelines video clearly states that you should not mention Oracle-D or other projects in your articles. I'm sure there are a couple exceptions to this rule, with the State of the DApps tasks, it's basically necessary to mention other projects in your articles. Though, you should really never mention Oracle-D in your articles! 

The goal is to write articles as you would normally write them. When you're putting references to Oracle-D in your articles, they lose their value as *real content*, made by *real people*. Then it just becomes clear that they're just promotional essays to earn the author money, you really want to avoid that. 

Let the project you're promoting be the hero of your article! Make sure that you're writing, because your passionate about their project, not because you want to earn a quick buck. 

---

## Authoritative vs Personal Writing Style

This concept is explained pretty decently in the [Oracle-D guidelines video](https://youtu.be/_5N-HSM0TIs?t=172)(linked to correct timestamp). You basically only want to write in an authoritatively writing-style when you're absolutely certain that you know the subject well enough AND if you have an excellent grasp of the English language. 

Using a personal writing style gives you a bit more leeway in terms of grammar and sentence structure. I generally find it to be much easier to write in a more personal style, just because you're able to form a better connection with your readers. 

If you're not a native English speaker, I would really suggest using a personal writing style, just because you'll probably find it easier to construct proper sentences. 

> **Protip** - Always capitalize your I's. I've seen many people who do not do this and it makes your articles look extremely unprofessional. 

---

##  

---

## Call to Action

Try to end your blogs with an enticing *call to action*. You want your readers to perform a certain task after having read your article, whether it's visiting a website or engaging with the organization they've written about. An excellent *call to action* should make your readers want to take the next step. 

An example from my [latest Oracle-D task](https://steemit.com/stateofthedapps/@daan/steampeak-dapp-review-steem-front-end-for-power-users): 

<center>![call-to-action-oracle-D-](https://files.steempeak.com/file/steempeak/daan/FELcjO53-call-to-action-oracleD.png)</center>

---

## Disclaimers

Disclaimers should only be used if you're giving out legal or investment advice in your blog posts. I always find it a bit weird when I'm seeing disclaimers on articles that really don't need a disclaimer. You might think '*better safe than sorry*', but it doesn't look good when you're over-using disclaimers. 

**Do use them when needed, but don't overdo it!**

---

## Conclusion 

Really try to put yourself into the Oracle-D customer's mind and think about what they as a customer would want. They have no need for low-quality articles, written by people who are just writing to earn a reward. They want honest coverage and content written by real people, with real thoughts. 

It's not bad to be critical, as long as you're presenting it in a constructive way. Learn more about SEO optimization, while still being true to yourself. Both your readers and the Oracle-D client will thank you for it. 

## [Visit the Oracle-D website, to see how they're building communities using blockchain technology!](https://oracle-d.com/)

---

## Post Beneficiaries

**5% of the post rewards will go to @oracle-d**
**5% of the post rewards will go to @dapplovers**

---

<center>![post-beneficiaries](https://files.steempeak.com/file/steempeak/daan/LxAJKpmc-post-beneficiaries.png)</center>

<center>*Post written using [SteemPeak](https://steempeak.com)*</center>

---