Before you can list a website on Posticy, you need to verify that you own or control it.
Website verification helps us make sure that websites are added by legitimate owners, publishers, or authorized representatives.
Once your website is successfully verified, its status will change to Wait for Admin. The Posticy team will then review the website before approving it for the marketplace.
Posticy supports three website verification methods:
You only need to complete one of these methods.
For most websites, we recommend starting with the HTML Meta Tag method.
If your website uses Cloudflare, strong bot protection, or another security service that may block automated requests, DNS TXT verification is usually the most reliable option.
If you have direct access to your website's files, you can also use the HTML File Upload method.
Add the verification meta tag provided by Posticy inside the <head> section of your homepage. Copy the complete tag from your listing; the code is specific to that listing. The example below is a placeholder, not a working verification code.
For example:
<meta name="verifyWebsite" content="YOUR_VERIFICATION_CODE">After adding the tag, return to Posticy and start the verification.
The tag must appear inside the <head> section of your homepage.
Most WordPress websites and other CMS platforms allow you to add custom code to the website header through a theme, plugin, or site settings.
Open your homepage and select View Page Source in your browser. You can usually do this with Ctrl+U on Windows.
Search for:
verifyWebsite
You should see the verification tag and your verification code.
Do not rely only on the browser's developer tools. If JavaScript adds the tag after the page loads, you may see it in DevTools even though the Posticy verification system cannot see it.
The tag should be present directly in the HTML returned by your server.
Common reasons include:
If everything looks correct but verification still fails, try clearing your website/CDN cache or use the DNS TXT Record method instead.
Download the verification file provided by Posticy and upload it to the root directory of your website.
The file should be accessible directly through a URL similar to:
https://example.com/verification.html
Use the exact filename and file contents provided by Posticy. The URL above is illustrative; do not rename the downloaded file to match it.
Open the URL in your browser before attempting verification to make sure the file is publicly accessible.
The verification URL must return HTTP 200 OK directly.
If the URL redirects somewhere else first, automated verification may fail even if the file eventually opens in your browser.
The file should also be uploaded to the root of the website rather than a subfolder.
This method works well if you have direct access through:
Some hosted platforms, including Wix, Squarespace, and Shopify, may not allow you to upload files directly to the website root. In that case, use the Meta Tag or DNS method instead.
DNS verification is particularly useful for websites protected by Cloudflare, firewalls, anti-bot systems, or other security services.
Add the TXT record provided by Posticy to your domain's DNS settings. Copy the complete value exactly as displayed for this listing, including any prefix and verification code. Do not use the HTML meta tag as the TXT value.
It will look similar to:
Type: TXT
Host: @
Value: COPY_THE_COMPLETE_TXT_VALUE_FROM_POSTICY
TTL: 3600After saving the record, wait for the DNS changes to propagate and try verification again.
Add it wherever your domain's DNS is currently managed.
For example, if your nameservers point to Cloudflare, the TXT record should be added in Cloudflare rather than at the registrar where you purchased the domain.
For the main domain, the host is normally:
@
For a subdomain, the DNS record needs to be added for that subdomain.
DNS changes are often visible within 5 to 30 minutes, although propagation can sometimes take longer depending on your DNS provider.
You can check whether the record is publicly available with:
dig TXT example.com +shortYour Posticy verification value should appear in the result.
DNS verification does not require Posticy to access your website.
This means services such as Cloudflare, Wordfence, Imunify360, or hosting firewalls cannot block the verification request.
You also do not need to temporarily disable your website security.
Sometimes everything appears correct in your browser, but automated verification still fails.
This is commonly caused by website security systems.
Posticy's verification system needs to access your website automatically. Some security services identify automated requests as bots and block or challenge them.
Examples include:
Depending on the configuration, the Posticy request may receive a 403 Forbidden, 503 Service Unavailable, or a challenge page instead of your actual website.
Caching can also cause problems. For example, Posticy may receive an older cached version of your homepage that does not yet contain the verification tag.
A website loading correctly in your browser does not necessarily mean automated systems can access it.
Your browser may pass security checks, cookies, or JavaScript challenges that an automated verification request cannot.
If your website uses strong bot protection, try DNS TXT verification. Because DNS verification does not access the website itself, it is not affected by website firewalls.
If you have access to a terminal, these commands can help identify common problems.
curl -sL https://example.com/ | grep verifyWebsiteIf the verification tag is returned, it is visible in the website's HTML.
curl -sI https://example.com/verification.htmlThe response should return 200 OK without requiring a redirect.
dig TXT example.com +shortYour Posticy verification record should appear in the response.
If your website returns 403, 503, or a security challenge, your firewall or anti-bot system may be blocking verification.
Successful ownership verification does not automatically publish the website on the Posticy marketplace.
After verification, the website status changes to Wait for Admin.
The Posticy team will then review the website. Once approved, it can become available on the marketplace.
If you have tried the available verification methods and your website still cannot be verified, contact Posticy Support.
Go to:
Help → Submit a Ticket
Use a subject such as:
Manual verification - example.com
Please include:
Proof can include a screenshot of the meta tag in View Page Source, your DNS TXT record, or the verification file URL.
Our team can check the website using different networks and investigate why automated verification is failing.
If necessary, we may request additional evidence that you control the website.
No. You only need to successfully complete one verification method.
For most websites, the HTML Meta Tag method is the easiest.
If your website uses Cloudflare or strong bot protection, DNS TXT verification is usually more reliable.
Yes. We recommend using the DNS TXT Record method because it does not require Posticy to access your website.
The tag may be inserted by JavaScript, Posticy may be receiving a cached version of the page, or your security system may be blocking automated requests.
Check View Page Source rather than only using DevTools.
Yes. Redirects are particularly important for the HTML File Upload method. The verification file should return 200 OK directly.
Yes. Make sure you verify the exact subdomain added to Posticy. For DNS verification, add the TXT record for that subdomain.
Usually, no.
Try DNS verification first. If you choose another verification method, you can temporarily adjust security settings if necessary and restore them immediately afterward.
You should not permanently weaken your website's security just to complete verification.
Most DNS records become visible within 5 to 30 minutes, but in some cases propagation can take longer.
A successful verification check does not automatically establish ownership in every case. Posticy still needs to review the evidence and approve the listing.
After successful verification, check whether its status has changed to Wait for Admin.
If automated verification continues to fail, submit a support ticket with evidence showing that you control the website. The Posticy team can investigate the verification issue and may request additional proof if required.
For a manual verification investigation, submit a support ticket and include the domain, methods tried, error, and evidence of control. Successful ownership verification still requires Posticy’s review before Marketplace approval.
Adding Your Website to Posticy Marketplace
If a tag, file or DNS record is not detected, use Troubleshooting Website Verification to work through the checks for your symptom.