Guest Posts Guidelines

Thank you for your interest in writing for LocalizeDirect. We are aiming at creating truly valuable content for the game dev community. Please check the recommendations and requirements below before you get started.

Topics we cover: Game localization, localization QA, game development, game dev software, game marketing and market analysis or other topics in a similar vein.

Length: 1,300-2,500 words of unique content (articles, tutorials, case studies) that has not been published elsewhere (we will do a plagiarism check). We may accept blog posts of a different length if the topics are tackled in sufficient depth. The only rule: no BS, please.

Quality: The post must be the best on its subject. Please supplement it with statistical data, real-life examples and use cases. Source your references with outbound links.

Things to avoid: Intrusive self-promotion. We will mention your company and add one do-follow link to your website but please don’t overadvertise yourself. Affiliate links or things like “this tool got 5 stars on Trustpilot”, “our company got an award as the best service provider”, “use this promo code to sign up with 50% discount” will be removed.

Delivery format: .docx, Google docs. If you have images or screenshots, send them as an attachment to your email.

Copyright: You agree that copyright passes entirely to LocalizeDirect and LocalizeDirect reserves the right to edit your content at any time. We reserve the right to refuse your submission or ask for edits/revisions. We may add our links to the article.

If we share the content via our social media, we’ll tag you/your company in the post.

Contact: Send your ideas to before you start writing so we can advise on whether your idea aligns with our audience.

General Writing Advice

  1. Do your research. Study the top search results in Google, read through the answers on Quora, Reddit or similar websites, think about the gaps and questions that remained unanswered. That’s a great start point!
  2. Use the active voice in the sentences, you instead of us/me. E.g. In this article, you will learn which languages to translate your game into depending on your game’s platform.
  3. Avoid long sentences. One or two lines for each work best. A conversational tone is preferred.
  4. Often, the shorter - the better. Try to explain things as easily and in as few words as possible.
  5. A strong, captivative opening. Start with the problem statement, surprising fact or the story where possible. You have just a few seconds to hook your reader: if they leave after the first paragraph, they’ll probably never come back.
  6. Comprehensive English, no grammar or punctuation mistakes. Use the Hemingway App for text difficulty (aim for max a 7th-grade reader) and run Grammarly for mistakes. You can also use SEMrush SEO Writing Assistant or an alternative for your SEO.
  7. Avoid general and obvious information. Try to make the articles data-based and as applicable as possible. Most of our readers are experienced developers who won’t waste time on things like “Find out what languages are spoken in the countries you want to publish your game to, proofread your text, test your game, etc.” On the contrary, advice like “The games containing such elements as A, will be banned in China. Better replace them with B as the game company C did. Find the full list of a government’s requirements towards the foreign games published to China on website Z” or “Try this tool if you want suggestions on genre preferences in this market” will be highly appreciated.
  8. Links to the external websites should have DA 60+ (check them with a free Ahrefs tool).
  9. Read our blogs to get an idea of the style and format.