Guest Blog Checklists

Please review the following items carefully to ensure your article meets our publishing standards. Make any necessary adjustments before submitting: 

Recommended Guidelines for Better Engagement

1. Headings (H2 & H3)

Start with H2 for primary headings, followed by H3 for subheadings, and so on. H1 is reserved for the article title, so you don’t need to worry about it.

Example:

H2: Preparation

H3: Check pthread extensions

2. Rich Content(At least 5 min read time)

Tip: In-depth content performs better!
✔ We recommend articles with at least 5 minutes of reading time (~800–1,000 words) for better engagement and visibility.

✔ Add examples, insights, or code snippets to make your post more valuable!
✔ Writers with longer, high-quality posts may earn special badges and extra points.

3. Profile Completion

Complete your profile with a clear photo and relevant social media links at least one (LinkedIn, Twitter, GitHub). Add a brief bio to introduce yourself to readers.


Essential Article Enhancements Guidelines

4. Article Coverage Style

Ensure your article follows one of these styles:

  • Problem/Error/Exception
  • "How to" guide
  • General explanation of a topic

If your article addresses a problem, follow this structure:

  • Introduction: Issue description, cause, and how to resolve it.
  • Include code examples and screenshots of the error and solution.


5. Incorporating Common Questions

Address common questions that your audience may have about the topic to add more value to your content.

6. Code Snippets/ Code Formatting (if code included)

Display code using the code snippet symbol {} in our code editor. Avoid showing code as an image; make it selectable for users to copy. For code formatting guidelines, check Code Formatting on CoderLegion.

7. Code Explanation

Include comments in the code or explanations after each code snippet for better clarity. Example: Switch Case with Enum in Java

8. Code Validation

Ensure your code runs in an online IDE and test it to ensure it's bug-free. Include a screenshot of the successful output in your article if the article is about a resolution to a problem.

9. Cover Image (Optional)

Ensure you have a cover image. Recommended size: 1000px x 420px. Allowed formats: JPG and PNG. For more details, refer to the section "All About Image".

10. Image Resolution

Ensure your image is clear and large enough to be visible at first glance, without requiring zoom. Example: Image Refer to the "All About Image" section for more guidelines.

11. References and Links

Include at least 2-3 outbound links to official, authoritative sources. Mention each source only once in the article.

12. Tags

Add relevant tags like "Python," "Error handling," or others that reflect the article content.

13. Grammar and Spelling

Proofread your article using tools like Grammarly to avoid spelling and grammar mistakes.

14. Markdown Usage

Use markdown divs like "Tip," "Note," "Warning," or "FAQ" to enrich your content. For guidance, refer to Markdown Divs on CoderLegion. Check example articles to see how they are used.

15. Conduct Research for Additional Insights

Explore relevant sources to gather new ideas and insights that can add value to your content.

16. Bold and Italic Text

Use bold and italic for emphasizing key terms, especially in the Introduction and Conclusion.

17. Heading Optimization

Make headings meaningful and include relevant keywords. Avoid vague headings like "Step 1: Preparation." Example optimized heading: "Step 1: Preparation - Check pthread extensions."

18. Article Formatting Tips

Follow general formatting guidelines for a clean and readable structure.

19. Conclusion

Conclude with 6-8 lines summarizing the key points and solutions discussed in the article. Bold important terms in the conclusion for emphasis.


Critical Violations

29. Violations that may lead to rejection:

  • a. Spamming: Repeatedly submitting irrelevant content or over-promoting specific products or services.
  • b. Content Plagiarism: Submitting content or code that has been copied from other sources without proper attribution.
  • c. Excessive Linking: Including too many links, especially irrelevant or low-quality external links, to manipulate SEO.
  • d. Unacceptable Language/Content: Use of offensive, discriminatory, or inappropriate language or content that may harm or offend others.
  • e. Originality: Ensure content and code are unique and not taken from other sources.
  • f. Article from other website without Canonical URL: Ensure if article is republished, canonical url should be mentioned on coderlegion.
  • g. Code Validation Issues: Submitting code that fails to run or has bugs.
  • h. AI generated content: Article generated using AI would not be accepted.
chevron_left