Give readers a one-click way to keep your recipe. They tap the button, see your recipe and save it to their Cookmarks library, where they can plan it into their week and add it to a grocery list. It’s free and you don’t need an account.
Paste this where you want the button, usually near the top of the recipe card or next to your print and Pin buttons. It picks up each page’s address on its own, so the same code works on every recipe.
Try it: this one saves a Love & Lemons recipe.
<a class="cookmarks-save-button" href="https://www.cookmarks.app/api/save">Save to Cookmarks</a>
<script async src="https://www.cookmarks.app/save-button.js"></script>On WordPress, paste it into a Custom HTML block, or into your theme or recipe card template so it shows on every recipe.
Several recipes on one page, like a roundup? Add data-url with each recipe’s address: <a class="cookmarks-save-button" data-url="https://yourblog.com/recipe/" …>
Where you can’t add scripts, like newsletters, or if you’d rather style the button yourself, link to a single recipe instead:
Every saved recipe credits you by name and links back to your page. Cookmarks recipe pages point search engines to your original, so a saved copy doesn’t compete with your post.
No. The script sets no cookies, stores nothing and makes no requests of its own. Your readers’ browsers download it from cookmarks.app like any other embedded file, and we don’t use those downloads to identify or follow anyone. The button only sends us the recipe’s address when a reader clicks it. The Privacy Policy covers what happens after that.
The script is a few kilobytes, loads with async and doesn’t block your page. If it’s blocked, the button still links to Cookmarks, but readers land on our home page instead of your recipe. Use a plain link (above) where scripts can’t run.
Not yet. Questions or ideas? Email support@cookmarks.app.