Want to write a guest post for the Survicate blog?

Survicate content is read by thousands of people interested in how surveys and customer feedback help drive business growth, boost customer satisfaction, and improve customer experience.

Our audience consists mostly of Marketing, Product, and Customer Success specialists working at SaaS, technology and e-commerce companies. If you have previous writing experience and want to tap into our audience, we’re open to guest posts.

Fill out the form at the bottom of this page and let us know what topic you’d like to write about – when you do, please bear in mind that we do not consider articles that aren’t related to surveys, customer feedback, customer satisfaction, or best practices in marketing and customer service.

Editorial Requirements:

Length & structure:

Article should be a minimum of 1000 words (that being said, bear in mind that we value quality over quantity. We won’t accept posts where you repeat yourself just to hit this threshold).

Provide a clear structure with an introduction, body, and summary/takeaways. Keep paragraphs short for readability. Use headings and subheadings.

Please make sure to support your opinions/theses with examples on the market, wherever applicable (people love learning from practical examples!).

Title & keyword:

When you pitch us the article, please submit two title variations (we will choose one).

Submit the SEO keyword that will be targeted in the article; provide the keyword difficulty and volume numbers. You can use Neil Patel’s UberSuggest tool to check these.


Provide at least 3 links to external, authoritative websites for every 1000 words. We don’t mind linking to content on your website or blog as long as it’s relevant and the copy isn’t promotional. However, keep in mind that you can link to your website no more than 2 times in the article.

Also, link to at least one article or website on the survicate.com domain.


For every 1000 words, the keyword must be used at least 3 times.
The keyword must appear in at least one heading.


Images are welcome, but make sure you have the right to use them. All images, if not created by the article author, need to have the source listed.

Maximum width of images: 650 px.

Illustrations must be related to the article content, for instance, graphs and/or infographics (no gifs).

Author’s bio:

When you submit your first draft, also send over a short (2-3 sentence) bio and a Gravatar-linked email address.

What happens if your topic is accepted?

We will ask you to submit an outline of the piece. If we accept the outline, you will be notified that you can start writing the draft.

We will review the first draft of your article at the soonest possible availability (bear in mind though that this might take a while due to the large number of guest post submissions we receive).

Once we review your draft, we will ask you to apply or review any changes within no longer than 5 working days. Otherwise, the text will be removed from our editorial calendar and might not be published or will be significantly postponed.

Terms of cooperation:

We reserve the right to apply minor changes (i.e. change of single words/phrases, change of title to a more SEO-friendly one; changes that won’t impact the content or structure) in the pre-publishing phase and as the text is SEO-optimized in the future.

We reserve the right not to publish the piece if the submitted draft is below our editorial, subjective standards.

Please note:

Due to the number of guest post inquiries, we reserve the right not to respond to all incoming emails.

Guest post inquiries sent via any other channel than the form provided below will not be considered by our editorial team.


If you do not receive feedback within the next 14 days, feel free to pitch the article to other outlets.

We do not accept sponsored posts. Please do not write to us if you want us to advertise or promote your products/services.

We accept guest posts only from authors who will share the piece with their professional networks, be it social media or newsletter.