Want to submit a guest post to the SAP PRESS Blog? You’ve come to the right place to learn more about the process!
If you’re a strong writer in the English language and have experience with the SAP suite of business solutions, especially with SAP S/4HANA, we’d love to hear from you. Read on to see our content guidelines and other things to know before writing and submitting a post for consideration. The content below should answer any question you have about the kind of content we’re looking for and how the submission process works.
Post Essentials: Every Post Needs These
Successful guest blogs educate readers with high-quality information that help them on their journey to reach their professional goals. These posts should be accessible (easily understood), high-value (worth readers’ time), and knowledgeable and reliable (displaying expertise in your subject).
We look for a few additional things in everything we publish:
- Original content. We have a zero-tolerance policy for plagiarism, and we will also not publish content that has previously been published elsewhere, such as LinkedIn, Medium, SAP Blogs, etc.
- Writing that reflects the style and tone of the SAP PRESS Blog. We are looking for content that is clear, approachable, and helpful to the reader.
- Up-to-date product naming. In an effort to provide timely information about SAP to our readers, product names must be properly listed and capitalized. No references to SAP HANA Cloud Platform or SAP Simple Finance, please.
- Proper attribution of any data, quotes, or outside content referenced in the article.
- No more than one link to your company’s website in the body of the post.
Post Types: What You Can Write About
We’ve spent the past two years compiling a list of types of blogs that work for our readers, and those that don’t. Here are some of our most successful blog post types:
Tips and Tricks
These posts should include shortcuts, workarounds, and other process-specific tasks that readers can use to make their day to day lives easier. Readers should be able to have enough information to perform the task on their own after reading this post. Screenshots illustrating the process are helpful for this kind of post.
Examples of Tips and Tricks posts:
- “How to Integrate SAP SuccessFactors Employee Central with SAP S/4HANA”
- “How to Perform Custom Code Management in SAP Solution Manager 7.2”
- “How to Split Cost of Goods Sold (COGS) with SAP S/4HANA Finance”
These posts should introduce the reader to a specific topic, module, or solution and explain how they provide value in a business context. Readers should be able to have a good understanding of the topic after reading this kind of post.
Examples of Informational posts:
- “SAP BW/4HANA: Modeling, Simplified”
- “Safety Stock with SAP”
- “The Customer 360° View in SAP Commerce Cloud”
A combination of a Tips and Tricks and Informational post, these posts provide beginner or advanced information on a specific topic. Readers should be able to learn both something about a solution and some ways to utilize the solution in their everyday life.
Examples of Fundamental posts:
- “3 Things to Know When Coding ABAP on SAP HANA”
- “SAP S/4HANA Migration with SAP Activate: The Prepare Phase”
- “SAPUI5 Coding Guidelines”
We focus on the following key topic areas of SAP: Administration, Business Intelligence, CRM & Sales, FICO, Human Resources, Logistics, Programming, and SAP HANA.
While we ultimately want to provide future-leaning content based around SAP S/4HANA, we understand many businesses are still utilizing SAP ERP and will consider content based on that suite until the 2027 deadline to move to SAP S/4HANA passes.
We will consider posts from time to time that don’t fit these topics or categories, but you have the best chance of being accepted if it matches one of the formats and topics listed above.
Post Don’ts: Things to Avoid
There are some things that we cannot accept:
- Plagiarism. Please submit original content only.
- Content already covered on our blog before. Please search our site before submitting an article to make sure we haven’t already published on it.
- Anything that may be construed as a link-building scheme.
- Anything overtly promotional for your company or organization.
- Anything that’s offensive or inaccurate.
- Overt criticism of individuals or companies.
Submit: How to Send Us Your Content
Please email marketing(at)rheinwerk-publishing(dot)com with the following:
- Put “Guest Posting on SAP PRESS Blog” in the email subject line.
- Cover letter explaining the content of the post, as well as your intended target audience.
- Completed post as a Word Doc, with clear references for screenshot/figure placement.
- Any screenshots or figures (with attribution) as JPG images in a separate folder, minimum 72 dpi. Read more about our image guidelines here.
- Short author bio (two to three sentences) including a maximum of one anchor text link to your own website.
- Author photo in JPG form, minimum 72 dpi.
If your article meets our editorial standards and aligns with our content strategy, we will respond to let you know your article will be published. That process may take up to 4 weeks due to our editorial calendar.
We may not be able to respond to all submissions. If you have not heard back from us within 4 weeks, you may assume we will be unable to publish your content and you may publish it on your own.
Appendix: Other Things to Know
- Submissions must meet the SAP PRESS Editorial and Marketing teams’ quality standards in order to get published.
- You may republish your guest post to your own blog, LinkedIn, Medium, or SAP Blogs after one month of publication on our site, as long as you provide a notice at the beginning of your post saying “This post originally appeared on the SAP PRESS Blog at https://blog.sap-press.com/.”
- The SAP PRESS Blog team reserves the right to edit and adapt your guest blog content as we see fit, and update it in the future for accuracy and comprehensiveness.
- SAP PRESS reserves the right to include calls-to-action to SAP PRESS content, including but not limited to email newsletters, internal links, and downloadable content.