Title: Adding support for Custom Post Type
Last modified: February 5, 2019

---

# Adding support for Custom Post Type

 *  [Enrico Sorcinelli](https://wordpress.org/support/users/enricosorcinelli/)
 * (@enricosorcinelli)
 * [7 years, 4 months ago](https://wordpress.org/support/topic/adding-support-for-custom-post-type/)
 * Currenty this plugin adds the metabox only for hard-coded `post`, `page` and `
   product` post types.
 * This [patch](https://gist.github.com/enrico-sorcinelli/9145c9c05c83a7c8d7c5030feab676c3)(
   based on plugin version 1.0.3) allows to add SEMrush metabox also for CTP you
   desire with the use of `semrush_seo_writing_assistant_post_types` filter.
    -  This topic was modified 7 years, 4 months ago by [Enrico Sorcinelli](https://wordpress.org/support/users/enricosorcinelli/).

Viewing 1 replies (of 1 total)

 *  [onskulsm](https://wordpress.org/support/users/onskulsm/)
 * (@onskulsm)
 * [7 years, 4 months ago](https://wordpress.org/support/topic/adding-support-for-custom-post-type/#post-11210482)
 * Since the latest release (1.0.4) this option is available in the main plug-in(
   without installing the patch)

Viewing 1 replies (of 1 total)

The topic ‘Adding support for Custom Post Type’ is closed to new replies.

 * ![](https://ps.w.org/semrush-seo-writing-assistant/assets/icon.svg?rev=1950877)
 * [Semrush SEO Writing Assistant](https://wordpress.org/plugins/semrush-seo-writing-assistant/)
 * [Support Threads](https://wordpress.org/support/plugin/semrush-seo-writing-assistant/)
 * [Active Topics](https://wordpress.org/support/plugin/semrush-seo-writing-assistant/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/semrush-seo-writing-assistant/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/semrush-seo-writing-assistant/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [onskulsm](https://wordpress.org/support/users/onskulsm/)
 * Last activity: [7 years, 4 months ago](https://wordpress.org/support/topic/adding-support-for-custom-post-type/#post-11210482)
 * Status: not resolved