How to Claim Website on Pinterest: Step-by-Step Guide

What does claiming a website on Pinterest mean?

A Pinterest website claim is a verification record that proves a Pinterest business account controls a specific domain. Once Pinterest confirms the record, the domain appears under the account’s claimed properties.

The practical benefit is attribution. If someone saves an image from a claimed website, Pinterest can connect that content to the verified account and display account information alongside eligible Pins. That link helps users identify the original publisher rather than an account that happened to save the page later.

Claiming also improves the account owner’s access to website-related analytics inside Pinterest. You can examine how content from your domain performs, including content saved by other users. The available reporting can vary by account and dashboard version, but the verified domain gives Pinterest a reliable source to associate with your account.

A claim is not a copyright registration. Pinterest may still contain copied images, outdated URLs, or Pins created by unrelated users. You’ll need Pinterest’s reporting tools if somebody republishes protected work without permission.

Website verification also differs from Rich Pins and the Pinterest Tag. Rich Pins use metadata from a page to show details such as an article headline or product information. The Pinterest Tag records actions for advertising measurement. Claiming establishes domain ownership. A creator may use all three, but each performs a separate job.

Pinterest generally expects you to claim a domain you control. A profile page on Amazon, Etsy, Substack, or another hosted marketplace usually can’t be claimed because you can’t edit its root files or DNS records. Owning the content on a page isn’t the same as controlling the domain.

• Website claim: Proves that your Pinterest business account controls a domain.
• Rich Pins: Read supported metadata from individual pages.
• Pinterest Tag: Measures selected website actions for advertising and conversion reporting.
• Copyright report: Addresses unauthorized use of protected work.

What do you need before claiming your Pinterest website?

You need a Pinterest business account and permission to edit either your website code, root directory, or DNS records before starting verification. A free personal Pinterest account can be converted to a business account through account settings if necessary.

Use the Pinterest account that should own the long-term relationship with the domain. This matters for a small team. If a freelance marketer claims your bakery’s website through the marketer’s own Pinterest account, transferring control later may require removing the existing claim and repeating verification.

Confirm the final version of your domain as well. A visitor might type example.com while the site redirects to www.example.com, or the reverse. Open the website in a private browser window and copy the address that remains after every redirect finishes. Pinterest’s verification screen will guide you through entering the website address.

You should also know who controls the site. A WordPress administrator can usually add a verification tag through a suitable plugin. A Shopify store owner can edit theme code. DNS verification requires access to the registrar or DNS provider, which could be Cloudflare, GoDaddy, Namecheap, or the company hosting your nameservers.

Make a backup before editing theme files. One misplaced character inside a template can affect the page layout, while an incorrectly saved DNS record can delay verification. The Pinterest code itself is small; the risk comes from editing the wrong location.

• Pinterest access: Use a business account with permission to manage claimed accounts.
• Domain control: Have access to site code, the root directory, or DNS settings.
• Correct address: Identify the live domain after HTTPS and www redirects finish.
• Backup: Save the current theme file before making a manual code change.
• Existing claim check: Confirm that a former employee, agency, or old account hasn’t already claimed the domain.

How to claim website on Pinterest?

To claim a website on Pinterest, open the business account’s settings, select the claimed-accounts area, choose the website option, and complete one of Pinterest’s verification methods. The wording and menu position can move as Pinterest updates its desktop interface, but the verification choices remain tied to business settings.

Pinterest will present a unique verification value. Don’t copy a tag from a tutorial or another website. The value identifies your Pinterest account, so you must use the exact code shown while signed in.

For the HTML tag method, copy the complete meta tag. Add it inside the <head> section of the homepage, before the closing </head> tag. Publish the change, clear any website cache, and view the public page source to confirm that the full tag appears. Return to Pinterest, enter the domain if requested, and submit it for verification.

For the HTML file method, download the file supplied by Pinterest without renaming or editing it. Upload that file to the root directory of the website. The finished file should open at a URL on your domain, such as example.com/pinterest-generated-filename.html. A file stored inside an uploads folder or media library won’t meet a root-directory check.

For DNS verification, copy Pinterest’s TXT value and open the DNS manager for the domain. Create a TXT record using the host specified by the provider, commonly @ for the root domain, and paste the Pinterest value into the content or value field. Save the record. Don’t add quotation marks unless the DNS provider inserts them automatically.

Return to the Pinterest claim screen after publishing the selected record. Enter your website address and submit the verification request. An HTML tag or file can often be detected quickly. DNS changes may take longer because resolvers cache older records; allowing up to 72 hours before troubleshooting propagation is reasonable.

Keep the verification record in place after Pinterest approves the claim. Removing the meta tag, file, or TXT record can make future ownership checks fail. The code has no visible effect on your homepage, so deleting it offers no useful performance benefit.

• Step 1: Sign in to the correct Pinterest business account on desktop.
• Step 2: Open Settings and find Claimed accounts or the website claim option.
• Step 3: Choose an HTML tag, HTML file, or DNS TXT record.
• Step 4: Publish the unique verification record on your domain.
• Step 5: Return to Pinterest and submit the domain for verification.
• Step 6: Leave the approved record installed.

Should you use an HTML tag, HTML file, or DNS record?

The HTML tag is best for most creators, while DNS verification is the strongest choice for a domain managed across changing themes or website platforms. The HTML file works well for developers with direct access to the web server.

An HTML tag is quick and easy to inspect. You can open the homepage source, search for “pinterest,” and see whether the code loaded. The trade-off is durability. A theme replacement, plugin cleanup, or website migration can remove a tag added through the old setup.

The HTML file avoids editing a template. It’s a good option on a custom-built site where the developer can upload directly to the public root. Many hosted website builders block root-file access, though. Uploading the file to a normal media library doesn’t count because Pinterest checks a specific public location.

A DNS TXT record sits outside the website theme. Rebuilding a WordPress site or switching from one storefront template to another won’t normally remove it. DNS is my preferred method for a company domain when the owner controls the records. The downside is slower feedback. A typo can be hard to spot, and a DNS change may not appear everywhere immediately.

Don’t use more methods than necessary. One valid record is enough. Installing all three creates extra cleanup work and makes it harder for another administrator to know which record Pinterest actually detected.

• HTML tag: Choose this for a standard creator site when you can edit the homepage head.
• HTML file: Choose this for a custom server where you can upload files to the public root.
• DNS TXT record: Choose this for durable verification that should survive a redesign or platform migration.
• Ask a developer: Do this if the domain handles email, storefront traffic, or other business services and you’re unsure about DNS.

How do you add Pinterest verification to WordPress, Shopify, Squarespace, or Wix?

Pinterest verification works on WordPress, Shopify, Squarespace, and Wix when the platform gives you a supported place for the HTML tag or a connected domain’s DNS record. Use the platform’s built-in verification field when one exists because it is less likely to disappear during a routine theme update.

On self-hosted WordPress, a reputable SEO or header-code plugin can place the Pinterest meta tag in the site-wide <head>. Some SEO plugins include a dedicated Pinterest verification field. Paste only the portion the field requests; a field labeled verification value may reject the complete <meta> tag. Avoid editing header.php directly unless you maintain a child theme, since a theme update can overwrite the change.

Shopify store owners can open the active theme’s code editor and place the full tag inside the <head> section of theme.liquid. Save the file, then inspect the published storefront rather than the preview alone. Shopify’s Pinterest sales channel or app may offer a connected setup in supported regions, but manual verification remains useful when an app connection fails.

Squarespace users should place the tag in the site’s header code-injection area if their plan supports that feature. Paste it into the header field rather than a page-level content block. A visual code block can display code to visitors without adding it to the document head, which Pinterest won’t accept.

Wix users should look for the site-verification or SEO verification controls in the dashboard. Add Pinterest as a custom meta-tag verification if the option is available. Publish the website after saving; changing a dashboard field without publishing may leave the live homepage unchanged.

DNS is the fallback for any builder that blocks code access. The DNS record belongs wherever the domain’s authoritative nameservers are managed, which may differ from the company that sold you the domain. Check the nameserver values first instead of adding the TXT record to an inactive DNS panel.

Why is Pinterest unable to verify your website?

Pinterest verification usually fails because the record is missing from the live site, placed in the wrong location, altered during copying, or still moving through DNS caches. Check the public result before repeatedly pressing Pinterest’s verification button.

For an HTML tag, open the homepage and use the browser’s View Page Source command. A page builder’s editor view isn’t enough. Search the source for the unique verification value. If the tag is absent, clear the site cache, CDN cache, and optimization plugin cache. Then reload the source in a private window.

Placement matters. Pinterest expects the meta tag inside the document’s <head>. A tag inserted in the page body, footer, blog post, or hidden visual block can appear in a browser without satisfying the ownership check.

For an HTML file, paste the exact file URL into a logged-out browser. The file must load directly without a sign-in prompt, 404 error, or redirect to the homepage. Security plugins sometimes block unfamiliar HTML files. A managed host can confirm whether the file sits in the public root.

For DNS, use a public DNS lookup tool to check whether the TXT record has propagated. One common mistake is entering the full domain in a host field that automatically appends the domain. That creates a record at example.com.example.com. Another is adding the record to a registrar even though Cloudflare or a different host controls the active nameservers.

An existing claim can also stop the process. Ask former staff members or agencies whether the domain remains attached to another Pinterest account. If you control that account, remove the old claim before adding the domain to the correct business profile. If you don’t control it, follow Pinterest’s support process and be ready to prove domain ownership.

Finally, check redirects and access rules. Password protection, maintenance mode, regional blocks, aggressive bot filtering, or a CDN firewall can prevent Pinterest from reading the homepage. Temporarily allowing Pinterest’s verification request is safer than disabling the entire firewall.

• Tag missing: Clear caches and confirm the value in the live page source.
• Wrong placement: Move the meta tag into the homepage <head>.
• File unavailable: Put the untouched HTML file in the public root directory.
• DNS not visible: Check the active nameservers and wait for propagation.
• Domain already claimed: Remove the claim from the previous Pinterest account.
• Crawler blocked: Review maintenance mode, password protection, and firewall rules.

What should you do after Pinterest approves the website claim?

After Pinterest approves the website claim, confirm the domain appears in Claimed accounts and start measuring content tied to that domain. Take a screenshot of the approved status and record which verification method you used. That small note saves time after a redesign.

Create a fresh Pin from one of your own public pages. Use the page’s final canonical URL, not a tracking redirect or temporary preview address. Check the published Pin to see whether Pinterest associates it with the correct account and destination.

Then review website-related reporting in Pinterest Analytics. Look for pages that attract saves or outbound clicks, and compare the Pin creative attached to each URL. A recipe image that earns saves may need a clearer text overlay to produce clicks. A product Pin with clicks but few saves may still be doing its job.

Set up Rich Pins separately if your content type supports them. Article publishers should maintain accurate Open Graph or supported metadata for the headline and description. Stores need clean product data. Claiming the domain doesn’t repair missing metadata.

Build Pins around pages with a clear purpose. A claimed domain won’t rescue a thin article, a broken mobile layout, or a product page that hides shipping information. Pinterest traffic often arrives on an individual page rather than the homepage, so each destination must make sense without prior context.

The honest caveat is simple: verification produces no guaranteed distribution boost. Pinterest still evaluates the Pin, topic relevance, destination quality, and user response. Treat the claim as infrastructure. For growth, pair that infrastructure with useful content, consistent publishing, and genuine engagement from active accounts.

If you want to grow faster, you can pinterest followers from a real, active-account service and build momentum while you keep posting. For a deeper dive, read our guide on How to Stream on Kick With OBS: A Step-by-Step Setup Guide (2026).

For a deeper dive, read our guide on Pinterest vs Instagram: Which is Best for Your Brand in 2026?.

For a deeper dive, read our guide on Pinterest vs Instagram: Which is Best for Your Brand in 2026?.

• Confirm ownership: Check that the domain appears under Claimed accounts.
• Document the method: Record where the tag, file, or DNS value is stored.
• Test a destination: Publish a Pin linked to a live page on the claimed domain.
• Review analytics: Compare saves and outbound clicks by content or URL.
• Check metadata: Configure Rich Pins separately where they fit the content.
• Keep access secure: Remove former contractors and require strong account authentication.