Welcome, blogger! 👋
We are open to contributions of high-quality articles to our worldwide appreciated eCommerce Growth Blog.
Let’s cut to the chase and get to the main reason why you’re here: our guest post content guidelines and target audience.
By following our guidelines below, you’ll be able to write content that:
✔️ We accept only guest posts that are:
✔️ The word count for articles should vary between 1500-2000 words.
✔️ The tone of voice must be professional and friendly, at the same time, but not over-promising and exaggerated.
✔️ Pay attention to English grammar, vocabulary, semantics and punctuation.
✔️ Titles must be written in Title Case.
✔️ Headings must be written in Sentence case.
✔️ Add relevant images in your draft, according to the context, along with their sources. Stock images are not accepted.
✔️ Add relevant examples in your draft, according to the context, along with their sources. Do thorough research on your topic before submitting it.
✔️ Add any links to our resources you consider relevant to the context.
✔️ Add a short author bio at the end of the article, with a link to your website and a headshot image of 300×300 px. You will also be the author of your guest post.
✔️ The context must be written according to current global events in relation to eCommerce.
✔️ Do not use the context of your guest post as a direct promotion to another website or a competitor!
✔️ Plagiarism is not tolerated in any way and the article draft is checked from this point of view.
✔️ Check the rest of the articles published on our blog about the topic you chose. Be original and present new angles for your topic!
✔️ Present an outline of the article before beginning the draft: title, headings with main ideas, links you will include and examples.
✔️ Send the article outline and draft in Google Docs, so we can keep track of the progress.
✔️ We publish guest posts only on Fridays, so the turnaround time varies according to the available content slots.
✔️ If the article does not meet the above requirements, we will refuse the collaboration.
The title is the first thing someone will see about your post. You want to make it:
The summary gives the reader a little bit more info on what they can expect from the post. It should be short – try to keep it under 280 characters – the length that could fit in a Tweet.
The introduction sets the stage and context for your post. A good introduction will set the stage for a reader. What are we talking about? When does this apply? Why do we even have a problem?
This short section should directly tell the reader what they will learn by reading this post. Keep it factual and use bullets if you need them. Limit the length to 1
paragraph (or maybe 2).
Use the prerequisites section to link to 2-4 URLs that come just before your article in the user’s “journey”.
Include those prereqs as URLs and, if necessary, give a sentence on each one. When possible, link to resources within \newline – this way the community’s knowledge can build upon each other.
These sections are where you will walk through the tutorial and explain every step to the reader. It’s the meat of the article.
💡 Tip: Default to Detail
Explaining things in detail takes a lot of time to write. As the author, it can
sometimes feel excruciating to spell out every detail.
You’ll know you’re doing it right when you ask yourself, “Is this too much detail? Am I going too slow?”
This level of detail is valuable to readers. If someone is reading the post and they understand what you’re saying, they can skim ahead. But if you skip things then someone who doesn’t understand can’t fill in the blanks.
It’s better to write about fewer topics in detail than to cover a ton of different topics at a shallow level.
A tour of features is structured differently than a coding tutorial in that the examples typically don’t build on each other.
At the end of your post summarize what you’ve talked about. Remind the reader why it’s valuable and what it means for the future. This is also your chance to give a call-to-action!
Close your article by listing resources where someone can go next to learn more. If you used any other sources in your research, give credit and link to them. Give the reader clear steps for where they can learn more.
You can either contact us and one of our marketing representatives will reply or you can complete the form below. 👇