> For the complete documentation index, see [llms.txt](https://tmniche-docs.keywordrush.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmniche-docs.keywordrush.com/building-a-site/pinterest-pins.md). # Pinterest pins TMN can make a **Pinterest pin** for every new article: a tall 2:3 image with the article's headline on it. Pinterest picks the pins up from an RSS feed on your site and posts them to your boards on its own — there's no Pinterest login or API key in TMN. ![Pins generated by TMN](https://990045058-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdIjKWGZMI5JKGQiOB3ml%2Fuploads%2Fgit-blob-7e77ff849dc2cd5437c564fa432b8c55fdd83e85%2Fpinterest-pin-examples.webp?alt=media) The pin is a separate image. Your featured image stays as it is. ## Turn it on Pins are set per **Generation Preset**, under **Images → Pinterest pin**. They're **off by default**. * **Generate pins** — turn it on to get a pin with each new article. * **Photo style** — **Bright lifestyle photo** (recommended, the look that does well on Pinterest) or **Same style as the featured image**. * **Headline font** — one of six typefaces, or **Auto**. * **Accent color** — colors the key words of the headline and the corner badge. Pick one of eight colors, enter your own (for example your brand color), or leave it on **Auto**. **Auto** picks a font and a color from your site's domain, so every pin on the site shares one look and a board reads as one series. Custom colors are matched closely, not exactly. ![The six headline fonts](https://990045058-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdIjKWGZMI5JKGQiOB3ml%2Fuploads%2Fgit-blob-af8b42022d1be90456e56c880f2a61b938edc747%2Fpinterest-pin-fonts.webp?alt=media) Each pin gets its own photo, headline and badge from the article, plus a Pinterest title and description. {% hint style="info" %} Pins are made only for articles generated **after** you turn the option on. Existing articles don't get one. {% endhint %} ## Connect Pinterest You do this once, in Pinterest, on a desktop browser. The **Too Much Niche → Pinterest** page in your WordPress admin has the same steps and your feed URLs. 1. **Claim your website.** Pinterest auto-publishes only from a claimed website, and that needs a free business account. See Pinterest's guides: [Claim your website](https://help.pinterest.com/en/business/article/claim-your-website) and [Get a business account](https://help.pinterest.com/en/business/article/get-a-business-account). 2. **Create your boards** — for example one per category of your site. 3. **Connect a feed.** In Pinterest: **Settings → Import content → RSS → Connect**, then scroll down to **Auto-publish** and click **Connect RSS Feed**. Paste a feed URL from the **Too Much Niche → Pinterest** page and choose its board. See [Auto-publish Pins from your RSS feed](https://help.pinterest.com/en/business/article/auto-publish-pins-from-your-rss-feed). ![Pinterest Settings → Import content, with the RSS Connect button](https://990045058-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdIjKWGZMI5JKGQiOB3ml%2Fuploads%2Fgit-blob-8fe9d2d9a17628e71ff73261011fa0baf8af8121%2Fpinterest-import-content-rss.webp?alt=media) {% hint style="info" %} Pinterest's help article still calls this menu **Create Pins in bulk**. In the current Pinterest settings it is **Import content**. {% endhint %} Pinterest adds new pins within 24 hours, up to 200 per day, oldest first. ## Which feed to use The **Too Much Niche → Pinterest** page lists: * **All categories** — every pin on the site, for one main board. * **One feed per category** — for a board per topic. TMN puts each article in its hub's category, so these follow your content plan. Each feed fills one board. You can connect several. If an article is in two connected feeds, its pin goes to both boards, which is fine on Pinterest. The **Last fetch** column turns green once Pinterest has read that feed. ## What goes into the feed * Only **published** posts with a pin. A scheduled post joins the feed when it goes live. * Not drafts, pending, private or password-protected posts. * The latest 50 pins per feed. ## Cost A pin doesn't use any of your article allowance. On your own OpenAI key, the pin image is billed to your OpenAI account, like the featured image — see [Bring your own API key](/account-and-licensing/byo-api-key.md). ## Troubleshooting **There's no RSS option under Import content in Pinterest.** Your website isn't claimed yet, or you're not on a business account. Pinterest shows the option only after the claim, and only on desktop. **"RSS feed cannot be fetched".** Pinterest couldn't load the feed. Open the feed URL in a private browser window — it should show XML. If your site sits behind a firewall or bot protection (for example Cloudflare), allow Pinterest's crawler. **"Links in the RSS feed are not under the claimed domain".** The claimed address and your site address differ, for example `www.` against no `www.`, or `http` against `https`. Claim the exact address your site uses. **An article has no pin.** Check that its preset had **Generate pins** on when the article was generated. Pin generation never blocks an article: if a pin fails, the article is still published without one. **Last fetch stays grey.** Pinterest hasn't read that feed yet. Check that you connected it in Pinterest, and give it up to a day. ## Where it's stored The pin is an image in your **Media Library**, attached to the post. It isn't set as the featured image. On the article page, Pinterest's **Save** button offers the pin instead of the wide featured image. Developers: the pin's attachment ID, Pinterest title and description are in the post's `_tmn_pin_id`, `_tmn_pin_title` and `_tmn_pin_description` custom fields. ## Next * [**Use presets**](/building-a-site/presets.md) — where the pin settings live. * [**Generate & publish articles**](/building-a-site/generate-articles.md) — pins are made as each article is generated. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://tmniche-docs.keywordrush.com/building-a-site/pinterest-pins.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.