[WordPress] 外掛分享： Burnpedia Pin Scheduler for Pinterest

內容簡介

Burnpedia Pin Scheduler for Pinterest 是一款專為 WordPress 設計的自動化外掛，能夠自動為您的文章排程 Pinterest 釘圖，節省時間並提升曝光率。它能夠從已發布的內容中生成釘圖，並根據您的設定自動發佈。

【主要功能】
• 自動生成釘圖，發布文章時即時處理
• 支援文章、頁面及 WooCommerce 產品等多種內容類型
• 可從一篇文章生成最多六個不同的釘圖
• 根據文章標題設計封面，無需圖片也能運作
• 自動添加 UTM 標籤以追蹤流量來源
• 批量釘圖已發布的內容，分散在最佳時間段

外掛標籤

開發者團隊

原文外掛簡介

Writing the post is the work. Remembering to pin it, three days later, is the part that quietly stops happening.
This plugin is Pinterest automation for WordPress: it schedules Pinterest Pins for you, automatically, from the content you already publish. Burnpedia Pin Scheduler connects your WordPress site to your Burnpedia account; when a post goes live, it builds a Pin from that post’s image, title and link and hands it to Burnpedia to publish on a schedule — to the board you picked, at a sensible time, without you opening Pinterest.
It works the same way for a blog post, a page, a WooCommerce product or any other public post type, and it can pin the archive you published before installing as well as everything you publish from now on.
What it does

Creates a Pin automatically when a post is published — 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, or the first image in the post when there is none.
Makes up to six Pins from one post, each using a different photograph, a day apart.
Designs a cover from the post’s title when the post has no image at all — free, and at the size Pinterest likes.
Sends the Pin to one fixed board, a board per category, or a board named after your site. A board that does not exist yet is created for you.
Writes the Pin title and description from templates with {title}, {excerpt}, {site} and {categories} tags — editable per post.
Adds UTM campaign tags to the link (utm_source=pinterest…) so Pinterest traffic shows up in Google Analytics or whatever you use. Links that are already tagged are left alone.
Schedules with a delay, so your caches and CDN are warm before Pinterest fetches the image.
Retries by itself, and waits for the reset when the day’s allowance is used up.
Bulk-pins the posts you published before installing, spread over safe best-time slots rather than sent in one burst.
Runs a free Pinterest check-up — a Pinterest SEO check — of every post: which posts have no big, tall image for Pinterest, which are not optimized for Pinterest (a title Pinterest would cut, a description too short to be found, an image with no alt text) and which posts you have never pinned — each one listed with a link to open the post and fix it.
Finds a tall picture further down a post whose featured image is wide, and uses it as the Pin picture in one click — one post or all of them, free.
Shows how many of your posts are ready for Pinterest, and re-checks them by itself every week — inside WordPress, nothing sent.
For any post you choose, can write a new Pin title and description and make a cover image with AI, using AI credit — shown as a preview first, and pinned only when you say so. Optional.
Writes Pin titles and descriptions for many posts in one go with AI — price shown first, each one undoable. Optional.
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 the Pins from this site — the site total on every plan, the per-post breakdown beside each post on the paid plans.
Shows what happened, per post, in an Activity log — including the posts it skipped and why.
Works in the block editor and the classic editor; the per-post Pinterest panel appears in both.

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 every part of the publishing side — automatic pinning, boards, templates, UTM tags, scheduling, retries, bulk-pinning the backlog, the Activity log — works on it.
One reporting feature is paid: the per-post breakdown of how each post’s Pins are doing. The site-wide total is on every plan, free included. Paid plans also raise the daily allowance. AI-written Pin copy and AI images use AI credit: paid plans include some every day, and anyone can buy it — no plan needed — as a one-time bundle. See burnpedia.app/pricing.
You keep your Pinterest password
The plugin never sees your Pinterest credentials. You connect Pinterest once inside Burnpedia, on Pinterest’s own login screen, over the official Pinterest API.
Open source
The plugin is GPL. Its source, and the API it talks to, are documented at burnpedia.app/developers.
External services
This plugin is a client for Burnpedia, a Pinterest scheduling service run by Burnpedia at https://burnpedia.app. The plugin cannot work without it: WordPress has no way to publish to Pinterest on its own, and Burnpedia is what holds the Pinterest connection.
Nothing is sent anywhere until you ask for it. With no key saved, the plugin makes an outbound request only after you press a button for it — the one-press connection below, or a bug report — or open More plugins. Nothing happens on activation, and nothing is sent on its own.
Connecting this site in one press (optional). On the Connection screen you can press Connect this site to Burnpedia instead of copying an API key by hand. When you press it:

Your browser opens https://burnpedia.app/connect/wordpress, carrying the address of this site and its title, so that the approval screen can name the site you are about to connect. It also carries a random one-time request ID and a fingerprint of a secret that never leaves your server.
After you approve it there, this site makes one POST https://burnpedia.app/api/site-connect/claim request, sending that request ID and the secret, and receives an API key which is saved for you. The key is never shown in your browser.
The request expires after fifteen minutes and can be collected only once. If you press Cancel, or never approve it, nothing is sent and nothing is created.
You never have to use it: pasting a key by hand still works.

Once a key is saved, the plugin contacts https://burnpedia.app/api/v1 in these situations:

When 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. The post editor and the Pinterest check-up tab read the same answer (from a five-minute copy) for your AI points balance, the AI prices and the AI credit bundles Burnpedia sells; nothing new is sent for any of it.
When you press “Load my boards” — a GET /api/v1/boards request. Sent: your API key.
When a post is published (with automatic pinning on), or you press “Pin this post now” — 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, and the time the Pin should be published. If the post has no image and “design a cover from its title” is on, no image URL is sent; a flag asks Burnpedia to design the cover from that 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.
When you open the “Pins from this site” tab — a GET /api/v1/pins request. Sent: your API key and this site’s address, so that Burnpedia returns only the Pins that link to this website rather than every Pin on your account.
When 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, so it cannot use up your Pinterest rate limit.

When 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 picture is pinned only if you press “Pin with this cover” (item 3).

When 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 and the check-up only uses this plugin’s own records.

When 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 if it has one. It returns a Pin title and description, saved in that post’s own Pin fields, and it uses AI points (price shown first). Nothing is pinned until you press “Pin with this cover”. If the words cannot be written, no picture is attempted. “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.
When 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 that fails is not charged.
Choosing a tall picture, 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 on the check-up tab are ordinary links to https://burnpedia.app/buy-credit, carrying the chosen bundle and this plugin’s name so the purchase can be credited to it; the plugin itself sends nothing when you click one.
Every request also carries a header naming the plugin and its version (for example wordpress/1.0.0), as a browser identifies itself, for support and compatibility questions.
No visitor data, no analytics, no usage statistics and no content beyond the fields listed above are transmitted. The plugin has no telemetry of its own: it never reports your traffic, your other plugins, or anything about your visitors. Your site’s address is sent as part of a Pin’s own link, when looking up this site’s Pins, in the check-up’s posts’ addresses when you run it, in a picture’s address when you ask AI to write its alt text, on the one-press connection screen (if you use it), and in a bug report if its box is ticked.
Your use of the service is covered by Burnpedia’s terms and privacy policy:

Terms of service: https://burnpedia.app/terms
Privacy policy: https://burnpedia.app/privacy

Pinterest itself is contacted by Burnpedia’s servers, not by your site. Note that Pinterest downloads your image from your own site, so the image URL has to be publicly reachable — the settings screen warns you when it looks like it is not.
The install count (optional, off by default). WordPress.org does not tell
plugin authors how many sites run their plugin. If you switch this on under
Burnpedia Pins → Connection, this site sends a short report:

POST https://burnpedia.app/api/plugin-insights — once when you switch it on,
then at most once a week while an administrator is using wp-admin, once if you
deactivate the plugin, and once if you delete it. Sends exactly nine things: a
random ID generated on this site, which plugin and which version, which of
those four events it is, your WordPress version, your PHP version, your site
language, whether this is a multisite network, and whether an API key is saved
(true or false — never the key). Receives: nothing your site uses.

Your website address is not in that report and is never sent, so we cannot
tell which website you are. Switch the setting off and the ID is deleted, so counting
stops and a later change of mind cannot be joined to it. It is off until you
choose it, no feature depends on it, and nothing about any reader or any
logged-in user is in it.
Report a bug and More plugins (only when you use them). Pressing Send report on Burnpedia → Report a bug sends POST https://burnpedia.app/api/plugin-bug-report: your description, an optional reply email, the plugin, WordPress and PHP versions, theme, language, whether it is multisite and whether a key is saved (never the key) — and your site’s address only if you leave “Include this site’s address” ticked. Opening Burnpedia → More plugins asks WordPress.org (https://api.wordpress.org/plugins/info/) for our plugin list via WordPress’s plugins_api(), as Plugins → Add New does.