This plugin is Pinterest automation for WordPress: it makes Pinterest Pins from the content you already publish. It connects your site to your Burnpedia account: when a post goes live, it builds a draft Pin from the post’s image, title and link; you approve it with one tick, and Burnpedia publishes
PricingFree downloadThe WordPress.org download is free. Pro versions, add-ons or external services may cost extra.
CompatibilityRequires WordPress 6.5 and PHP 7.4.
SourceWordPress plugins · Nov 17, 2026
01 / Source details
Aboutthistool.
This plugin is Pinterest automation for WordPress: it makes Pinterest Pins from the content you already publish. It connects your site to your Burnpedia account: when a post goes live, it builds a draft Pin from the post’s image, title and link; you approve it with one tick, and Burnpedia publishes it to the board you picked, on a schedule, without you opening Pinterest.
How Burnpedia Pin Scheduler for Pinterest is different
It is built for Pinterest alone:
Up to six Pins from one post , each from a different picture in it, a day apart.
Your older posts too , spread over the days ahead, not in one burst.
A free Pinterest check-up of your posts (up to 5,000 a scan), each one listed with a link to fix it.
A plain reason for every post it skips , in the Activity log.
Every Pin is one you chose , and its screen says why.
What it does
Drafts a Pin when a post is published, for you to approve in Burnpedia — or only for the posts you tick.
Pins posts, pages, WooCommerce products and any other public post type you switch on.
Uses the featured image, else the post’s first image, else a free cover designed from its title.
Makes up to six Pins from one post, each using a different photograph, a day apart.
Sends each Pin to one board, a board per category or one named after your site, and creates a board that is missing.
Writes the Pin title and description from templates with {title} , {excerpt} , {site} and {categories} tags — editable per post.
Adds UTM tags to the link ( utm_source=pinterest …) so Pinterest traffic shows in Google Analytics.
Schedules with a delay so caches are warm, retries by itself, and waits out a used-up daily allowance.
Bulk-pins the posts you published before installing, spread over safe best-time slots.
Runs a free Pinterest check-up — a Pinterest SEO check — of every published post, up to 5,000: no big, tall image, a title Pinterest would cut, a description too short to be found, no alt text, never pinned — each with a link to fix it.
Uses a tall picture further down a post when the featured one is wide — one click, one post or all, free.
Shows how many of your posts are ready for Pinterest, and re-checks them by itself every week — inside WordPress, nothing sent.
With AI credit (optional), writes Pin titles and descriptions and makes cover images, for one post or many: price shown first, a preview before anything is pinned, each one undoable.
Writes alt text with AI for every picture a post’s Pins use — one post or many. Optional.
Reports impressions, saves and link clicks for this site’s Pins — the site total on every plan, per post on the paid plans.
Shows what happened, per post, in an Activity log — including the posts it skipped and why.
Works on the free plan
Nothing here is locked by the plugin: no trial, no time limit, no feature switched off until you pay us for the plugin. A free Burnpedia account publishes up to 3 Pins a day , and the whole publishing side works on it.
Paid plans add the per-post breakdown and a higher daily allowance. AI words, covers and alt text use AI credit: paid plans include some every day, and anyone can buy a one-time bundle, no plan needed. See burnpedia.app/pricing .
External services
This plugin is a client for Burnpedia , a Pinterest scheduling service at https://burnpedia.app . The plugin cannot work without it: Burnpedia holds the Pinterest connection.
Nothing is sent until you take one of the steps below. With no key saved, a request leaves only after you press a button for it — the one-press connection below, or a bug report — open More plugins , or switch on the install count. Nothing happens on activation.
Connecting this site in one press (optional). On the Connection screen you can press Connect this site to Burnpedia . When you press it:
Your browser opens https://burnpedia.app/connect/wordpress , carrying the address of this site and its title, so the approval screen can name the site, and which plugin and version asked. It also carries a random one-time request ID and a fingerprint of a secret your browser never sees.
While you approve it there, this site asks POST https://burnpedia.app/api/site-connect/claim at least three seconds apart, at most 100 times each time the Connection screen is opened while the request is live, and once each time you press I have approved it . Each ask sends that request ID and the secret, and names the plugin and its version in its headers; it does not carry your site’s address, not even in its User-Agent header. Once you approve, the answer is an API key, saved for you and never shown in your browser.
The request expires after fifteen minutes and its key can be collected only once. If you press Cancel, or the request expires, the asking stops and no key is created.
Once a key is saved, the plugin contacts https://burnpedia.app/api/v1 in these situations:
01When you open the plugin’s settings screen or press “Check connection” — a GET /api/v1/me request that returns your Burnpedia plan, the Pinterest accounts connected to it, how much of today’s Pin allowance you have used and when it resets, and, during a Pro trial, the days left and a short-lived checkout link. Sent: your API key. Other screens reuse it for five minutes.
02When you press “Load my boards” — a GET /api/v1/boards request. Sent: your API key and the Pinterest account you picked ( account ), if any.
03Whenever a Pin is sent (a post published with “Draft a Pin when a post is published” on, “Pin this post now”, “Send a test Pin”, “Run it now”, Pin older posts , held-back posts, retries) — a POST /api/v1/pins request. Sent: your API key, the Pin title, the Pin description, the post’s public permalink, the URL of the post’s image and that image’s alt text from your Media Library (if any), the board name or id, the Pinterest account you picked ( account , if any), and the time the Pin should be published. When a person chose the Pin (“Pin this post now”, “Send a test Pin”, a ticked post, a kept cover), it also sends picked: true ; without it, Burnpedia keeps the Pin as a draft for your OK. With no image and “design a cover from its title” on, no image URL is sent; a flag asks Burnpedia to design the cover from the title. With “let Burnpedia generate one with AI” also on, the same flag asks for a generated photograph behind it, which spends AI points on your Burnpedia account; if it cannot be generated you get the free designed cover instead. Nothing extra about your site is transmitted for either.
04When you open the “Pins from this site” tab — GET /api/v1/pins requests (the list and its counts). Sent: your API key and this site’s address, so that Burnpedia returns only this site’s Pins.
05When you open the “Pins from this site” tab, or the posts list in WordPress — a GET /api/v1/analytics/site request. Sent: your API key and this site’s address. It returns the impressions, saves and clicks Burnpedia has already recorded for your Pins; it does not ask Pinterest anything.
06When you press “Make a preview” under “Try an AI cover” in the post editor — a POST /api/v1/covers request. Sent: your API key, the Pin title, the post’s public permalink, and a flag asking for an AI photograph. It uses AI points (cost and balance shown first) and creates no Pin; the preview is shown straight from burnpedia.app, and the picture is pinned only if you press “Pin with this cover” (item 3).
07When you press “Scan all posts” on the Pinterest check-up tab — POST /api/v1/pinned-status requests, up to 500 addresses each. Sent: your API key and the public addresses (permalinks) of your published posts that this plugin has not pinned yet. It returns, for each address, whether it was ever pinned by your Burnpedia account or is on your connected Pinterest account. Every other check-up result — picture size, alt text, title length, description — is worked out inside WordPress and is not sent anywhere. With no key saved, nothing is sent.
08When you press “Make it with AI” on a post in the Pinterest check-up — a POST /api/v1/copy request, then the POST /api/v1/covers request described in item 6. Sent to /copy : your API key, the post’s title, its public permalink, and its excerpt (or its opening words). It returns a Pin title and description for that post and uses AI points (price shown first); nothing is pinned until you press “Pin with this cover”. “Write titles & descriptions” sends the same /copy request once per ticked post, without the cover; posts that already have their own words are skipped and nothing is sent for them. “Make cover previews for the ticked posts” sends both requests per ticked post; kept covers go out through item 3, one a day.
09When you press “Write alt text with AI” (or “Write alt text for the ticked pictures”) in the check-up — a POST /api/v1/alt-text request per picture. Sent: your API key, the public address of a picture that post’s Pins use, and the post’s title. Burnpedia fetches the picture to describe it and returns one sentence, saved as the picture’s alt text. It uses AI points. Nothing is sent for a picture that already has alt text.
An AI request Burnpedia cannot complete is not charged.
The tall-picture choice, the readiness score, the “scan again” reminder and the weekly re-check of your posts all run inside WordPress and send nothing.
The Buy AI credit buttons are ordinary links to https://burnpedia.app/buy-credit , carrying the chosen bundle and, like every link to Burnpedia, this plugin’s name and version; the plugin itself sends nothing when you click one. Each also names its screen ( utm_content ); Design a Pin and Pin it again with a new picture add the post’s title, permalink and from .
Every request to /api/v1 carries headers naming the plugin and its version; a Pin request also carries a random one-time key, so a retry never makes a second Pin. Only under a yes given since 1.0.46 to the install count below, each also says whether this site has used Pin older posts , and under which version of the words (see that paragraph).
Except the opt-in install count below (and t
See it in action
Screenshots & previews.
The Pinterest check-up: how many posts are ready for Pinterest, which have no big Pinterest image, which are not optimized for Pinterest, and which you have never pinned — each finding with a "Fix it" link."Make it with AI" on one post: a Pin title, a description and a cover preview. Nothing is pinned until you choose it.A tall picture found further down a post, offered as its Pin picture, and the picture's alt text written with AI.Pin titles and descriptions for several posts at once, with the price for the whole selection shown first.Alt text for the ticked pictures, written with AI one after another — priced first, each post with its own Undo.One button uses the tall picture on every post that has one, and says how many first.AI cover previews for the ticked posts. Nothing is pinned until you tick Keep on a cover, and kept covers are pinned one a day.The settings screen: connection status, plan, and today's Pin allowance.Automation settings: draft a Pin when a post is published (you approve each one), with the reason one click away under Why?; which posts, which board.Pin older posts: tick the posts from your archive to pin, spread over safe posting times.Pins from this site: the readiness score, and impressions, saves and clicks for this website's Pins.Your best posts on Pinterest (paid plans): the posts sending the most clicks to your site, each with "Pin it again with a new picture".The Pinterest box in the post editor: the Pin picture, title, description and board for one post."Fix it" from the check-up opens the post with the field to change already selected.The Activity log: what was pinned, what was skipped, and why.Report a bug from inside WordPress: it goes straight to the people who build the plugin, and nothing is sent until you press Send.
02 / Source details
Gettingstarted.
01Install and activate the plugin.
02Go to Burnpedia → Connection and press Connect this site to Burnpedia . Approve it in the tab that opens — a free account takes a moment to make if you do not have one — and this site collects its own key. There is nothing to copy or paste. You are then asked one question, “draft a Pin when I publish?” , and that is the setup.
Publish a post to try it: its Pin waits for your OK in Burnpedia under Waiting for your OK . The Activity tab shows what happened.
Connecting by hand instead. If your site cannot reach the internet, or you would rather do it yourself:
03Create a free account at burnpedia.app and connect your Pinterest account there (this happens on Pinterest’s own login screen).
04In Burnpedia, open Dashboard → API and create an API key. It is shown once — copy it.
05In WordPress, go to Burnpedia → Connection , paste the key and save.
06Open the Automation tab, turn on “Draft a Pin when a post is published (you approve each one)”, choose your board, and save.
03 / Source details
Frequently asked questions.
Do I need a Burnpedia account?
Yes. This plugin is a client for Burnpedia, and it cannot publish to Pinterest without one — WordPress has no way to post to Pinterest on its own. Creating one is free, takes a moment, and needs no card. Pinterest itself is connected inside Burnpedia, on Pinterest’s own login screen.
Does this post to Pinterest when I publish?
It makes the Pin, and you approve it. Turn on “Draft a Pin when a post is published (you approve each one)” under Automation , and every post you publish becomes a draft Pin in Burnpedia, waiting for your OK under Waiting for your OK ; tick it and it goes to Pinterest at its time. A post you pin by hand from the post editor ( Pin this post now , old posts too) or tick on Pin older posts needs no second step for its first Pin; with more than one Pin a post, its other pictures wait for your OK too.
Why don’t my Pins post by themselves any more?
Why your Pins now wait for your OK:
Pinterest’s rules for apps like Burnpedia say “the end user must choose each Pin to be published”, so a Pin made for you automatically (from your WordPress site, a repeat or an app) now waits here for your OK instead of publishing by itself.
We know it is one more tap. It keeps your Pinterest account in good standing, and it takes seconds: tick the Pins you want and press “Approve the ticked ones”.
Pins you make yourself in Burnpedia still publish at their time, as before.
Your Pins that wait for an OK are in Burnpedia under “Waiting for your OK”: burnpedia.app/dashboard/waiting . Pinterest’s rule: policy.pinterest.com/en/developer-guidelines . The same words are in the plugin, under Automation → Why?
How is it different from other Pinterest plugins?
It is built for Pinterest alone: see How Burnpedia Pin Scheduler for Pinterest is different in the Description above.
Can I schedule Pins instead of posting them immediately?
Yes. Pins are scheduled by default, with a delay you choose, so your caches and CDN are warm before Pinterest fetches the image. Straight-away publishing is one setting away. A drafted Pin keeps that time if you approve it before then; approved later, it goes the next day with room, at the same hour.
Do I need a paid account?
No. A free Burnpedia account publishes up to 3 Pins a day, and the whole publishing side works on it. Nothing in the plugin is locked; what Burnpedia meters is the daily allowance, the per-post breakdown on Pins from this site , and AI credit.
What happens when I hit 3 Pins a day on the free plan?
Nothing is lost. The post waits in line, and after the daily allowance resets the waiting posts go out one at a time, in order, at the day’s best posting times — never all at once, and no retry is used up. The Activity tab shows the line and when the next one goes, in your site’s own timezone.
Why does a new Pinterest account send only 5 Pins a day?
A Pinterest account that is new to Burnpedia starts slowly: at most 5 Pins a day in its first week and 10 in its second, then the usual pace. A young account that suddenly sends many Pins is what Pinterest blocks. Nothing is lost: the other posts wait in line, and the Activity tab says why they wait.
Does this need my Pinterest password?
No, and it never asks for one. Pinterest is connected inside Burnpedia through Pinterest’s official OAuth login, on Pinterest’s own domain.
Why did my post not get pinned?
The Activity tab gives the reason for every post it skipped. The usual ones are: the post is password protected, its category is excluded, or the day’s Pin allowance is used up (in which case it waits in line and goes out after the reset). A post with no image is no longer one of them by default — it gets a designed cover instead.
Why did my Pin fail?
The Pins from this site tab says why beside every failed Pin, in one plain sentence, with a button for the one thing to do: reconnect Pinterest, choose another picture or board for the post, or open the Automation settings. Then send the post again.
What happens to a post that has no image?
It gets a cover designed from its title: the headline set in one of Burnpedia’s colour palettes, at 1000×1500. It is free, uses no AI points, and the same post always gets the same cover. Switch it off under Automation → Image and such posts are skipped and logged, as they were before.
My Pins fail with an image error.
Pinterest fetches the image from your server, so the image URL must be reachable from the public internet. Local development sites, sites behind HTTP authentication, and private networks cannot work — the settings screen shows a warning when it detects one.
A picture too small for Pinterest (under 77 pixels on its shorter side) is caught before the Pin is made. The post’s next picture is used instead, at the same time; with none left, the post gets a cover designed from its title, or, with covers off, the Activity tab says why it was skipped.
Pinterest says my link “may lead to spam”.
Pinterest has blocked links to your website’s address — it is about the address, not the Pin. Burnpedia stops sending Pins to that site from your Pinterest account at once, keeps the others waiting with nothing lost, and tries one Pin again after 7 days (longer if it is still blocked). The Activity and Results tabs say so in plain words, with a link to ask Pinterest to unblock the site.
Can I pin an old post?
Yes, one at a time or in bulk. Open a single post and use Pin this post now in the Pinterest box; to work through an archive, the Pin older posts tab lists every published post that has no Pin yet and queues the ones you tick, spread over safe posting slots rather than sent in one burst.
Does it work with WooCommerce products?
Yes. Any public post type can be pinned — WooCommerce products, pages, portfolios, recipes, or any custom post type your theme or plugins register. You choose which ones under Automation ; attachments are excluded on purpose.
Does it work with the block editor and the classic editor?
Both. The per-post Pinterest panel appears in the block editor sidebar and in the classic editor, and the image is read from the featured image or from the images in the post content either way.
Does it also post to Instagram, Facebook or X?
No — this plugin does Pinterest only, and does it properly. If you need other networks, use a separate plugin for them alongside this one.
Does it show Pinterest analytics inside WordPress?
Yes. The Pins from this site tab is a Pinterest analytics screen for the Pins this website published: impressions, saves, and clicks through to your site. The site-wide total is on every plan, free included; the per-post breakdown is on the paid plans. The numbers come from Burnpedia’s own copy of Pinterest’s data, so opening the screen never spends your Pinterest rate limit.
Can I see how my Pins are performing without leaving WordPress?
Yes. The Pins from this site tab shows impressions, saves and clicks through to your site. That site-wide total is on every plan, free included.
The per-post breakdown — the same numbers beside each post in the posts list, which answers which post Pinterest is sending people to — is on the paid plans. Either way the numbers come from Burnpedia’s own copy of the data, so opening those screens never uses up your Pinterest rate limit. Pinterest reports about two days behind, and the screen says so.
Can I change the Pin’s title, description or board for one post?
Yes — all three are in the Pinterest box in the post editor and override the site-wide templates.
Does it pin a post twice if I update it?
No. A post is pinned once. Re-publishing an already-pinned post does nothing; use “Pin this post now” if you want another Pin.
Which post types can it pin?
Any public post type on your site — choose them under Automation . Attachments are excluded on purpose.
Does it work with custom fields, page builders, or a headless setup?
It reads the featured image and the post content, so anything that stores those normally works. The burnpedia_pin_image_url and burnpedia_pin_payload filters let you supply your own values.
Is it GDPR-relevant?
The plugin sends no personal data about your visitors anywhere. It sends only what is listed under “External services”, for example the Pin fields once you save an API key, and a bug report only if you send one. Settings → Privacy offers a suggested paragraph for your privacy policy that says what goes to Burnpedia. This is not legal advice.
How do I find which of my posts are not optimized for Pinterest?
Open the Pinterest check-up tab and press Scan all posts . It lists every published post, up to 5,000, with no big, tall image for Pinterest (none at all, narrower than 1000 pixels, or less than a quarter taller than it is wide), every post that is not optimized for Pinterest (a Pin title over 100 characters, which Pinterest cuts off; a description too short to be found; an image with no alt text; pinning switched off) and every post you have never pinned. Each post has a link to view it and to edit it, and each finding a Fix it link that opens the post with the field to change already selected — the Pin title, the Pin description, the Pin picture, or the picture’s alt text. The scan is free and the picture and text checks never leave your site.
Does it help with Pinterest SEO?
It checks the things that decide whether a Pin can be found on Pinterest: a Pin title short enough that Pinterest does not cut it, a description long enough to be searched, alt text on the picture, and a big, tall image. The Pinterest check-up lists every post that misses one, and Fix it opens the field to change. It does not do keyword research, and it does not change your site’s own search engine settings.
Which of my posts have never been pinned?
The check-up’s Never pinned by you list. It counts Pins this plugin made, Pins made in your Burnpedia account, and Pins on your connected Pinterest account, including ones you pinned by hand. Pinterest does not tell anyone whether somebody else pinned your page, so the list means never pinned by you. From there, the Pin older pos
FinderPress Media Auditor helps site administrators scan for broken images, missing Media Library files, unreachable media URLs, and other media issues across WordPress content. Use it to audit images, video, audio, PDFs, featured images, and attachment files without sending scan data to an external
The Accepted Payment Methods plugin is a straightforward, lightweight solution that enhances your website by displaying visually appealing icons of the payment methods you accept. This plugin is ideal for a variety of websites, including e-commerce platforms, service-oriented websites, and informati