Pinterestbot
SafeUser-agent: Pinterestbot
Category: Social Media Bots
SEO impact if blocked: 0/10
1 crawler operated by Pinterest
https://www.pinterest.com/Who Pinterest is, for site owners
Pinterest operates 1 crawler in our directory, filed under Social Media Bots. Its crawl behaviour is rated safe.
Blocking Pinterest carries an SEO impact score of 0/10. Blocking impact is rated: Varies - Evaluate before blocking.
Our recommendation for Pinterest: Generally safe to allow; provides legitimate crawling value.
Pinterest at a glance
| Operator | |
|---|---|
| Crawler in directory | 1 |
| Categories | Social Media Bots |
| SEO impact if blocked | 0/10 |
| Crawl behaviour | 1 rated safe |
| Website | www.pinterest.com |
| Official crawler docs | Pinterest crawler documentation |
Crawler operated by Pinterest
What Pinterest's crawlers are for
Pinterest runs 1 crawler in our database. Grouped by the job each one does:
- a utility crawler:
Pinterestbot
The highest-priority token is Tier 5. That makes Pinterest a lower-priority operator for most sites: worth a deliberate decision, but rarely the one that decides your visibility.
How site owners treat Pinterest
None of Pinterest's tokens were among the names tracked in our robots.txt study of the Tranco top 10,000, which usually means few large sites write rules for them yet. Your own logs are the best evidence of how often they visit.
Writing one policy for Pinterest
A robots.txt file cannot say "Pinterest"; it can only name Pinterest's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything Pinterest fetches through it
User-agent: Pinterestbot
Disallow: /private/
Allow: /- Decide per job, not per company. Training, search and user-triggered fetching have different trade-offs, even from the same operator.
- Name every token you mean. A token you leave out follows
User-agent: *. - Repeat shared rules. A named group ignores the
*group, so copy anyDisallowlines you still want it to obey. - Verify from outside. Run the LLM crawler checker after any change to see the result for each Pinterest token, including firewall refusals.
Test yourself: does User-agent: Pinterest block all of Pinterest's crawlers?
No. robots.txt matches crawler tokens, not company names. Use the token Pinterestbot.
Test yourself: if you block one Pinterest token, are the others blocked too?
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
Each Pinterest crawler, explained
A one-paragraph brief for every Pinterest token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
- Pinterestbot (
Pinterestbot, Tier 5): a utility crawler that fetches a page to build a link preview when someone shares it. Rated safe. Pinterestbot's operator does not clearly document how it treats robots.txt. Write the Pinterestbot rule anyway, then confirm in your logs that its requests stop. Not tracked in our robots.txt study.
Common mistakes with Pinterest's crawlers
The errors we see most often with Pinterest's crawlers in the files and firewalls we test:
- Treating Pinterest's crawlers as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
- Relying on robots.txt alone when Pinterest's crawlers is rated caution or aggressive. Back the rule with a server-side block.
- Blocking Pinterest's crawlers by IP alone. Ranges change; match the token and verify with logs.
All three hide inside a file that looks correct, so check Pinterest's crawlers from outside after every change.
What our own data shows about Pinterest
Everything below comes from the AI Crawler Check bot database and our two most recent robots.txt scans of the Tranco top 10,000, not from Pinterest's marketing. Pinterest has one token in our database, so the whole picture fits in one place.
Pinterestbot in our records
We first recorded Pinterestbot on March 17, 2026. Pinterest documents it on help.pinterest.com, and we recheck that page before each release. No file in our top-10,000 scans names Pinterestbot, so any rule you write for it puts you ahead of almost every large site.
Among the 9 social preview bots in our database, Pinterestbot sits fifth by priority (Tier 5), level with FacebookBot, facebookexternalhit, LinkedInBot, Quora-Bot. 9 of the 9 share its safe rating. Other operators with a crawler that fetches a page to build a link preview when someone shares it: MicrosoftPreview (Microsoft, Tier 3), FacebookBot (Meta, Tier 5), facebookexternalhit (Meta, Tier 5), GoogleMessages (Google, Tier 5), LinkedInBot (LinkedIn, Tier 5). A policy for Pinterestbot is usually a policy for these too.
A decision record for Pinterestbot
Teams that review crawlers once a quarter keep one short entry per token, so anyone can see why a rule exists and when it was last checked. Filled in from our data, the Pinterestbot entry reads:
- Operator and job: Pinterest; it fetches a page to build a link preview when someone shares it.
- Priority and behaviour: Tier 5, rated safe, blocking impact not documented.
- Suggested starting point: Allow by default; revisit if it costs you bandwidth.
- Enforcement: Pinterestbot's operator does not clearly document how it treats robots.txt. Write the Pinterestbot rule anyway, then confirm in your logs that its requests stop.
User-agent: Pinterestbot
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the Pinterestbot entry once a quarter, or when Pinterest publishes a new token next to it.
Checking Pinterestbot on your own site
Because Pinterest runs only Pinterestbot in our records, one check covers the whole operator. Search your access logs for the string Pinterestbot over the last 30 days, note how many requests it made and which paths it asked for, then compare that with what your robots.txt allows. Match the requests against what Pinterest publishes about the crawler, since that page is the only authority on its behaviour. A Tier 5 crawler rated safe rarely needs more than a quarterly look, and our log checker does the counting for you.
How top sites treat Pinterest's crawlers
From our robots.txt study of the Tranco top 10,000 (5,583 valid files, fetched October 20, 2026):
None of the tokens for Pinterest's crawlers is tracked by name in our study. For scale, 20.1% of top-site files block at least one AI training crawler and 4.3% refuse every unnamed crawler with User-agent: * and Disallow: /, which would catch Pinterest's crawlers too.
More questions about Pinterest
- Will blocking Pinterest affect my Google rankings?
- Only if one of its tokens is a Google search crawler. None of Pinterest's tokens are Googlebot, so classic Google rankings are unaffected.
- How quickly does a robots.txt change take effect for Pinterest?
- Crawlers cache robots.txt, commonly for up to a day. Expect a change to apply within about 24 hours, and confirm it in your logs.
- Can I allow Pinterest on some sections and block it on others?
- Yes. Inside the group for
Pinterestbot, addDisallowlines for the paths to keep private andAllowlines for exceptions. The longest matching rule wins. - Does blocking Pinterest delete content it already collected?
- No. robots.txt only controls future visits. For content already collected, check whether Pinterest offers a removal or opt-out process.
- Is a firewall block better than robots.txt for Pinterest?
- A firewall enforces the decision, while robots.txt asks politely. Many operators recommend robots.txt because blocking their IPs can stop them reading your rules at all. Use robots.txt first, and add a firewall rule only if requests continue.
A five-minute Pinterest review
- Confirm the token. Compare the user-agent in your logs with the tokens listed on this page. A close spelling is not the same crawler.
- Decide the outcome per crawler. Use the briefs above to choose allow, limit or block for each token.
- Write the group. Add or edit one
User-agentgroup per decision and repeat any shared rules inside it. - Publish and wait. Allow about a day for crawlers to fetch the new file.
- Confirm the result. Check your logs, then run the GPTBot and ClaudeBot access check to see the outcome from outside, including any firewall layer.
How to block or allow Pinterest in robots.txt
This rule covers the single crawler Pinterest operates. Add it to the robots.txt file at the root of your domain.
Block Pinterest completely
User-agent: Pinterestbot
Disallow: /
Allow Pinterest explicitly
User-agent: Pinterestbot
Allow: /
These Pinterest rules ask; they do not enforce. If a Pinterest token ignores them, block it at the server or CDN. Paths are case-sensitive, and each rule matches the token, not the full user-agent string.
Frequently asked questions about Pinterest
What crawler does Pinterest run?
Pinterest operates 1 crawler in our directory: Pinterestbot (user-agent Pinterestbot).
Should I block Pinterest?
Generally safe to allow; provides legitimate crawling value. The SEO impact score for blocking is 0/10, where 10 means blocking costs you the most visibility.
How do I block Pinterest in robots.txt?
Add the following to robots.txt at your domain root: User-agent: Pinterestbot then Disallow: /.
Does blocking Pinterest hurt my search rankings?
Blocking impact is rated: Varies - Evaluate before blocking. Google's own ranking crawler is Googlebot, which this operator does not run, so blocking Pinterest does not by itself remove you from Google's index. What it can change is whether AI assistants and analytics tools can read your pages.