Burnpedia Image Save Button Analytics

No. The button, the counting and the whole analytics screen work with no account of any kind, and nothing leaves your site. A Burnpedia account is needed for exactly one thing: showing how your own Pins for those posts are doing on Pinterest. A free account shows the site-wide total of impressions, saves and outbound clicks; the per-post columns are on Burnpedia's paid plans.

Yes, and you do not have to set everything up again. With that plugin on the site, Save Button detects its settings and offers to copy the ones that have an equivalent here — in one press, with a list of exactly what will change shown first. It never edits their settings and never deactivates them, so you can run both side by side and keep whichever you prefer.

No visitor data is collected: no IP address is stored; rate limiting keeps only a short-lived salted hash that cannot be read back to an address and expires within minutes. No cookie is set, no user agent or referrer is kept, and nothing about a reader is ever sent off your server.

It does the same job. Pinterest's original Pin It button was a script you loaded from Pinterest; this is a save button your own site draws, so nothing is fetched from Pinterest and nothing about your readers is sent anywhere. Pressing it opens the same save window. If you already run Pinterest's own Pin It button (pinit.js), this plugin detects it and stays out of the way rather than putting two buttons on one image.

Yes — Save Button → Button → When it shows. Hover is the default on a desktop because a button that is always visible sits on top of the photograph you want people to look at. On phones and tablets it is always shown either way, because there is no hovering with a finger.

The usual reasons, in the order they turn out to be true:

1. A page cache has not been cleared yet. Purge it and reload.
2. Pinterest's own widget is on the page. If pinit.js is loaded — often by a tag manager — this plugin steps aside rather than drawing a second button.
3. The image is smaller than the minimum. The default skips anything under 200 pixels in either direction, which is what keeps buttons off icons and author photos. Lower it under Save Button → Button.
4. The image, or something around it, carries an excluded class — no-save, one you added yourself, or Pinterest's data-pin-nopin attribute.
5. The post type is switched off, or the theme prints the post body without running WordPress's own content filter, which some page builders do.

Almost always a security plugin. Several of them switch the WordPress REST API off for logged-out visitors, and that is the path the count travels on — so the button still works, and the number never moves. There is a Send a test click button on the Analytics screen that sends one real click along exactly the same path a reader's browser uses, without your login. It answers the question in about a second.

One deferred JavaScript file of under 8 KB over the wire and one stylesheet under 2 KB, both served from your own site, with no jQuery, no framework and no external request at all. The buttons are drawn over your images rather than inserted into them, so the page does not move when they appear.

No. It never edits your content. The buttons are drawn in a layer above the page, which is also why full-width images stay full width.

The largest one your site offers. WordPress makes several sizes of every image you upload, and a browser on a phone downloads a small one — saving that copy would leave a phone-sized Pinterest image on somebody's board forever. This plugin reads the whole set and hands over the biggest, so what people save is always the sharp copy.

Yes. Every post has a Save Button (Burnpedia) box in the editor sidebar with one field: the Pin description for that post's images. Whatever you type there is what Pinterest fills in when a reader saves any image from the post. Leave it empty and nothing changes — the image's own alt text is used, and then the post title. An individual image that carries Pinterest's own data-pin-description attribute keeps that, because it is a more specific choice than a whole-post default. The box appears for anyone who can publish that post type. It is not shown to contributors, because the text goes out on a public Pin under your site's name.

Open Save Button → Analytics and look for Images that would be Pinned with no description. It lists the posts whose images have no alt text — ranked by how often readers save from them, or by date if nobody has saved anything yet — and says how many images in each need it. Each post title links to its editor. It matters for Pinterest specifically: an image with no alt text is saved with the post's title as its description, so a post with six photographs sends six Pins with identical text. Writing alt text fixes that, and it also helps people using screen readers and search engines. A Pin description set on the post removes it from the list too, but it gives every image in that post the same words again. The list reads only your own posts. It sends nothing anywhere.

Yes. Open a post, find the Save Button (Burnpedia) box and choose a hidden Pin image. It is usually a tall graphic, often 1000 by 1500, with the headline set across it — the shape that works in a Pinterest feed and would look wrong in the middle of an article. Readers never see it. When somebody presses the save button anywhere on that post, Pinterest opens with that graphic rather than the photograph they pressed, and with your Pin description. A copy of it is also placed in the page, hidden, which is where Pinterest's own browser tools look for images to offer. Two honest notes. Their browser does download it even though they never see it — that is exactly what makes it findable, so only set one on posts where you want it saved. And the count still records which photograph they pressed, because "which picture makes people save" is worth knowing separately from what gets saved.

Yes, four ways: add the class no-save, add data-pin-nopin to the image, add your own class names under Save Button → Button, or raise the minimum image size.

It is honest, and it is not a billing system. Presses are counted as they arrive, with two limits that keep somebody from inflating it: no more than 30 clicks a minute from one visitor, and no more than 2,000 a day on any one post. Your own clicks, while you are logged in, are never counted.

If you also run our scheduling plugin, yes: every row in the table gets a Schedule a Pin button that opens that post at the scheduling panel, so the image readers are already saving is one click from being queued. Nothing appears if you do not have that plugin. This one never suggests installing anything.

No, and there is nothing that could. The plugin never stores an IP address, a user agent, a referrer or a cookie, so no visitor detail exists here to be sent. If you have connected a Burnpedia account, the plugin sends your daily totals — this website's address, a date and a whole number per day — so those counts can sit beside your Pin results in your dashboard. It goes at most once every twelve hours, only while you are on the Analytics screen. You can switch it off under Save Button → Account, and with no API key saved nothing is sent at all.

Everything it wrote is removed: the settings, the counts, the daily series and the caches. Your posts and your images are not touched.