SleekPixel for Toolset Types custom post types
Toolset Types lets non-developers register custom post types, taxonomies and fields. Each CPT lives in wp_posts and the fields write to wp_postmeta with a wpcf- prefix. SleekPixel reads those fields and renders per-CPT share cards on save.
♾️ Lifetime License available
Toolset Types CPTs deserve their own share cards
Toolset Types is the long-standing OnTheGoSystems plugin for registering custom post types and fields through a UI. Each registered CPT lives in the standard wp_posts table. Toolset custom fields write to wp_postmeta with a prefix of wpcf-, so a 'price' field on a Property CPT lands as wpcf-price. Taxonomies and relationships use standard WordPress mechanisms with Toolset metadata layered on top.
SleekPixel reads the Toolset Types CPT registry through the plugin's API and exposes each registered CPT as a separate template scope. Each Toolset custom field is reachable by its wpcf- meta key. So a Property CPT template can map wpcf-price to the share card subtitle, wpcf-bedrooms to a stat block, and the standard featured image to the card surface.
The 1200 by 630 PNG lands in uploads on every Toolset CPT save. The SEO plugin's og:image filter publishes the URL into the post head, and scrapers see a card that reflects the actual Toolset data on every CPT update.
Workflow
Toolset Types to per-CPT share cards in four steps
Install on a Toolset site
Build a template per CPT
wpcf- fields to slots, pick accent colors and decide which post-level fields feed the layout.
Save a Toolset post
save_post. SleekPixel renders the share card for that CPT to uploads with the post's actual field values.
Share the post URL
og:image filter. Each Toolset CPT shares with its own card design.
Output
Sample Toolset Property listing share
Rendered from a Toolset Types Property CPT with wpcf-price, wpcf-bedrooms and featured image, plus standard post fields.
Comparison
Default Toolset share vs SleekPixel for Toolset Types
Logo on every Toolset CPT
- Toolset custom fields never reach the og:image meta on shares
- Property prices and stats invisible to scrapers across the site
- Same site logo on every Toolset CPT URL regardless of type
- Toolset templates render on page but not in share previews
- Editing a Toolset post does not refresh the share card scrapers see
SleekPixel
- Reads Toolset Types CPTs from the plugin's registered types
-
Pulls Toolset custom fields from
wp_postmetawithwpcf-prefix - Renders separate templates per registered Toolset CPT
- Refreshes on every Toolset post save, including relationship edits
- Works alongside Toolset Views and Toolset Blocks on the same site
Features
What SleekPixel gives you for Toolset Types
Toolset CPT registry aware
The plugin reads the Toolset Types CPT registry and offers a separate template scope per registered CPT, so each type can have a share card design tailored to its purpose.
Custom field mapping
Toolset custom fields with the wpcf- prefix map to template slots by their meta key, so any registered Toolset field can feed the share card directly without manual exports.
Refreshes on every save
The render hook fires on save_post for every Toolset CPT, so editing any Toolset custom field through the post editor refreshes the share card automatically.
Use cases
Where Toolset Types sites benefit most
Real-estate listing sites
Property listings built on Toolset CPTs need per-listing share cards naming the price, bedrooms and location, not just the same site logo across every property.
Toolset directory sites
Directory sites with Toolset CPTs for businesses, services or events benefit when shares of individual listings preview the listing instead of the site itself.
Multi-CPT content sites
Sites with multiple Toolset CPTs (reviews, profiles, events) get per-type share cards so the share matches the editorial format of each content type.
The bigger picture
Why Toolset Types sites need per-CPT share cards
Toolset Types exists because WordPress sites need custom content types beyond the default post and page. Property listings, event calendars, restaurant directories and member profiles are all CPTs in the Toolset world, each with its own field schema and editorial logic. The whole point of registering a CPT is that the content is structurally different from a blog post.
Sites that ignore per-CPT share cards lose that signal at the share level. Every Toolset post shares with the same site logo, regardless of whether it is a property or a profile. SleekPixel restores the per-CPT signal.
Each CPT gets its own template, its own field mappings and its own accent. Shares of a property preview the property. Shares of a profile preview the profile.
The cost is one license. The benefit is per-type share previews on every Toolset CPT URL the site ships.
Questions
Common questions about SleekPixel for Toolset Types
Both. SleekPixel reads the Toolset Types CPT registry and the wpcf- postmeta keys directly. Toolset Views, Toolset Forms and Toolset Blocks coexist but are not required.
Yes. Toolset fields write to wp_postmeta with the wpcf- prefix. SleekPixel reads any meta key by name as a template slot input, so all Toolset field types are reachable.
Yes. Toolset relationships resolve to related post IDs that SleekPixel can dereference inside templates. So a Property CPT can pull data from its related Agent CPT into the share card on every save.
 
No. SleekPixel writes the PNG and exposes the URL through a filter. Yoast accepts the URL as the og:image input on every CPT, so Yoast still emits the meta tag for the scraper.
Yes. That is the default behavior. Each registered Toolset CPT gets its own SleekPixel template scope, so a Property CPT and an Event CPT can have completely different share card designs on the same site.
 Yes. Toolset Blocks renders fields on the page. SleekPixel reads the underlying Toolset CPT data directly from postmeta, so the share card is independent of which Toolset Blocks layout the page uses on the frontend.
 
No. The render runs on save_post in the background. Bulk imports through Toolset's CSV importer trigger share card renders in the background too, without blocking the WordPress admin during the import.
Yes. Repeatable Toolset fields store as arrays in wp_postmeta. SleekPixel can access an entry by index or aggregate them (count, average, list) into a single template slot inside the share card.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkoutBrowse more
- YouTube banner art
- Threads post images
- Ko-fi banners
- X Space banners
- Spotify Canvas
- Gumroad product covers
- Buy Me a Coffee banners
- Nostr note images
- LinkedIn event banners
- Telegram bot avatar
- Twitch schedule banners
- YouTube channel banners
- Instagram collab post images
- Flickr cover photo
- YouTube Music cover art