Account setup
How to claim your website on Pinterest — and what claiming actually changes
Claiming a domain is the step that attaches your name to every save of your content. It is also the most confused step on Pinterest: it is not a verified badge, it is not an Analytics switch, and it does not create rich Pins. Here is what it does, the four ways to verify, and the failures that keep a claim from completing.
What changes
Four documented effects of claiming a domain
Claiming is not cosmetic. Pinterest publishes exactly what happens whenever an image from a claimed website is saved, and all of it is attribution: the save points at you instead of at a loose image. That is the whole reason to do it before you start publishing at volume rather than after.
| What a claim gives you | What Pinterest says |
|---|---|
| Your profile picture appears alongside the Pin | Pinterest states that whenever an image from your claimed website is saved, your profile picture will appear alongside the Pin. |
| The Pin links back to your Pinterest profile | The same rule says the Pin will link to your Pinterest profile, so a save of your work becomes a route back to your account instead of an anonymous image. |
| People see the option to follow you | The third documented effect of a save on claimed content is that people will see the option to follow you on Pinterest. |
| You can see how often your content is shared | Pinterest describes claiming as giving you insight into how often your content is shared on Pinterest — the domain-level view you cannot get while your site is unclaimed. |
Effects and wording from Pinterest’s Claim your website page, re-fetched October 2026. No third-party blog is cited on this page.
What it is not
Five things claiming does not do
Most of the frustration around claiming comes from expecting it to deliver something it was never designed to deliver. Each of these five is a different switch, in a different place, with different prerequisites.
| Not the same as claiming | What it actually needs |
|---|---|
| Analytics | Analytics is gated on a business account, not on claiming. Pinterest states that to view Pinterest Analytics you need to set up a business account. Claiming and business-account setup are two separate jobs, and doing one does not do the other. |
| A verified badge | Verified accounts is a separate programme with its own review. Claiming a domain never produces a verification badge, and a badge does not claim a domain. |
| Rich Pins | Rich Pins are generated from the metadata on your own pages, and they apply once that metadata is valid — the work happens in your site head, not in the claim flow. Claiming and rich Pins are complementary, not interchangeable. |
| Marketplace storefronts | To claim a website you must own the domain, subdomain or subpath and be able to edit the source code. That single requirement is why most social accounts, and stores hosted on marketplaces such as Etsy, eBay and Amazon, cannot be claimed at all. |
| A free-for-all | A website can only be claimed by one Pinterest account. Each website you claim is treated as a separate domain unless the addresses route to the same place. |
The practical order that avoids rework is: claim the domain, put valid metadata on the pages you want to promote, set up a business account, then read Analytics. The rich Pins guide covers step two, and the free rich Pin validator checks whether your metadata would qualify before you publish.
The four routes
Pick the verification method your site can actually support
Pinterest offers four methods, and it labels one of them as limited. All four end in the same place, so choose on what you are able to change: the site code, the file system, or the DNS.
| Method | What it is | When to pick it |
|---|---|---|
| Google Merchant Center | Connect the Google Merchant Center account that holds your product data, by entering its ID and signing in with the matching Google account. | Pinterest labels this option as currently available for some accounts — do not be surprised if you do not see it. |
| HTML tag | Copy a personalised meta tag from Pinterest into the head section of your site. | The fastest route on any site where you can edit a template, an SEO plugin or a theme header. |
| HTML file | Download a file from Pinterest and upload it to your web server. | The file must sit in the root folder. Pinterest states that a file uploaded to a subfolder cannot be accessed. |
| DNS TXT record | Copy a personalised TXT value from Pinterest into your domain DNS records. | The best option when you cannot edit the site itself. DNS changes can take up to 72 hours to take effect. |
Every route starts in the same four clicks, and every route ends with the same verification box.
| # | Shared start | Detail |
|---|---|---|
| 1 | Log in to your Pinterest business account | Pinterest links straight to the business login from every version of these instructions. |
| 2 | Open the menu | Click the chevron-down icon at the top-right corner to open the menu. |
| 3 | Select Settings | The claim flow lives in the account Settings area, not in the profile editor. |
| 4 | Click Link to Pinterest | It sits in the left-side navigation of the Settings area. |
| 5 | Click Claim next to Websites | This is where the four verification methods are offered. The last step is always the same: enter your website URL and click Verify. |
Method one
The HTML tag
The tag route is the one most bloggers use, because a single line in a header template or an SEO plugin field is enough. Pinterest places the tag in the head section, before the body section, and checks the live page for it.
| # | Step | What happens |
|---|---|---|
| 1 | Copy the tag | Click the text in the box below Add HTML tag to copy it, then click Continue. |
| 2 | Open your site head | In a separate window, log in to your website and open the index file. |
| 3 | Paste it into the head | Add the tag to the head section, before the body section. On most hosts this means the site header template, a theme header file, or a verification field in an SEO plugin. |
| 4 | Verify | Return to Pinterest, enter your website URL in the text box and click Verify. Pinterest then checks the live page for the tag. |
Methods two and three
The HTML file, and the DNS TXT record
These two exist for the cases the tag cannot reach. The file route suits a site where you can drop something into the web root but would rather not touch templates; the TXT route suits a site you do not control at all.
| # | HTML file | What happens |
|---|---|---|
| 1 | Download the file | Click Download below Upload HTML file, then click Continue. |
| 2 | Upload it to the root | Upload the HTML file to your web server at the root folder. Pinterest is explicit that a subfolder will not work. |
| 3 | Verify | Return to Pinterest, enter your website URL and click Verify. The check reads the file from the root of the domain. |
| # | DNS TXT record | What happens |
|---|---|---|
| 1 | Copy the record | Click the text in the box below Add TXT record to copy it, then click Continue. |
| 2 | Paste it into your DNS | Log in to your domain host and paste the value into your DNS record section. If your host requires it, add @ in the Host field. |
| 3 | Wait for propagation | Pinterest warns that you may need to wait up to 72 hours for the change to take effect. Verifying too early simply fails. |
| 4 | Verify | Return to Pinterest, enter your website URL and click Verify. |
One reassurance applies to all three: the code, file or record is temporary. Pinterest states that once you have successfully claimed a website you can remove it, and the claim stays. The verification artefact is proof at the moment of checking, not an ongoing dependency.
When it fails
Six failures, and the documented fix for each
A failed verification is nearly always one of six things, and five of them are rules Pinterest writes down rather than errors you have to guess at.
| Symptom | Fix |
|---|---|
| The HTML file never verifies | Check the location before anything else. The file has to be at the root of the domain; a copy inside a subfolder cannot be reached by the check. |
| The TXT record never verifies | Allow for propagation — Pinterest documents a wait of up to 72 hours — and confirm the value was pasted whole, including any @ host entry your DNS provider expects. |
| Pinterest says the site belongs to someone else | A website can only be claimed by one Pinterest account. If the domain was claimed by a previous owner, developer or agency account, it has to be released from that account first. |
| Two properties collapse into one entry | Each website you claim is treated as a separate domain unless the addresses route to the same place. A www and non-www pair that both resolve to the same site is one claim; genuinely separate hosts are separate claims. |
| You removed the tag and the claim stayed | That is expected. Pinterest says that once you have successfully claimed a website you can remove the HTML tag, the HTML file or the TXT record. The claim lives on the account, not on the code. |
| Saved Pins stop linking to your profile | Check Settings, then Claimed accounts. Unclaiming a website disconnects the Pins associated with that site from your account. |
After the claim
What to do in the first week after verifying
A claim is an input, not an outcome. Four follow-ups turn it into something you can measure — and confirm the state of an account you will be operating for years.
| Next step | Why it matters |
|---|---|
| Add rich Pin metadata | Article, recipe and product rich Pins read metadata from your pages, so the pages you care about need valid tags before they can carry the extra information Pinterest shows in the Pin closeup. |
| Add your website to your profile | Pinterest’s own what-next list pairs the claim with adding a link to your website on your profile. The claim attributes saves; the profile link gives visitors somewhere to go. |
| Set up a business account if you have not | Analytics needs a business account. Claiming first does not skip that step. |
| Review what the claim changed | Open Settings, then Claimed accounts, to confirm the website is listed under Websites. This is also the screen where an unclaim is started. |
From there the measurement side is the seven-metric Analytics guide, the free analytics calculator for turning those numbers into rates, and the profile audit for the account-level checks that sit around the claim. If you want the whole sequence in order, the five-stage content workflow starts from account setup and ends at scheduling.
Sources
- Pinterest Business Help — Claim your website (the four verification methods and their table, the shared Settings → Link to Pinterest → Claim click path, the per-method steps, the root-folder rule for the HTML file, the 72-hour DNS wait, the one-account rule, the separate-domain rule, the marketplace limitation, the find-your-claims and unclaim steps, and the profile picture / profile link / follow effects of a save)
- Pinterest Business Help — Create rich Pins (rich Pins syncing automatically from site metadata, the article / recipe / product types, the 24-hour sync note, and the page-level opt-out tag)
- Pinterest Business Help — Review Pinterest Analytics (the business-account requirement for Analytics, and the 30-day Overview window)
Every step, rule and limit above comes from Pinterest’s own Help Center pages, re-fetched and string-matched in October 2026. No third-party blog is cited on this page.