Troubleshooting Website Verification

If website verification fails, use the checklist for your symptom below. You only need one successful verification method. Copy the exact verification code from the relevant listing in your Publisher account. For setup instructions, see How to Verify Your Website on Posticy.

First check the website and its status

Open My Websites in your Publisher dashboard and check the exact website you added. Confirm whether it uses the main domain or a subdomain and whether verification has already changed its status to Wait for Admin.

Wait for Admin means the technical verification check succeeded. The next step is Posticy’s review. Repeating verification will not replace that review or automatically make the website available in the Marketplace.

The meta tag is not detected

1. Copy the current tag from Posticy without changing its verification code.
2. Check that the verifyWebsite meta tag is inside the homepage’s <head> section.
3. Open View Page Source on the public homepage and search for verifyWebsite. The tag must be present in the HTML returned by the server, rather than inserted only after JavaScript runs.
4. Clear the relevant website or CDN cache after adding the tag, then check the public source again.
5. If a security challenge prevents automated access, try DNS TXT Record verification.

The HTML verification file cannot be found

• Use the original filename and contents supplied by Posticy.
• Upload it to the website root, rather than a subfolder.
• Open its exact URL without being signed in to your hosting or website account.
• The verification URL must return HTTP 200 OK directly, with no redirect, login page or security challenge.

If your hosted platform does not allow root-file uploads, use the meta tag or DNS method instead.

The DNS TXT record is not detected

1. Add the record at the provider that manages your active DNS nameservers.
2. Check that it is a TXT record and copy the complete value exactly from the listing in Posticy, including any prefix and verification code. Do not substitute the HTML meta tag or an example value from this guide.
3. Check the host matches the website being verified. The root-domain host is commonly @; a subdomain needs its own matching host.
4. Allow the record to become publicly visible. Your DNS provider’s propagation and caching can affect timing.
5. Once the correct record is publicly visible, retry verification in Posticy.

Changing a record in an inactive DNS zone will not make it visible. If you are unsure which provider manages the domain, ask your hosting or DNS administrator.

The website opens in my browser, but verification fails

Your browser may pass cookies or JavaScript challenges that an automated verification request cannot. A firewall or anti-bot service can return a blocked response or challenge instead of the actual page.

Use DNS TXT verification for this situation. It does not require Posticy to fetch the website page, so you can verify without disabling your website’s security protections.

Verification succeeded, but the website is not visible

Technical verification and Marketplace approval are separate steps. Check for Wait for Admin and allow Posticy to review the listing. Also remember that your own Publisher websites are excluded from Marketplace searches in your same-account Marketer view. See Why Can’t I See My Own Websites in the Marketplace?.

Ask Support to investigate

If the checks above do not resolve the issue, submit a support ticket with:

• The exact website URL and your Posticy account email.
• The method you tried and the error message.
• When you added or last changed the verification entry.
• Relevant hosting, DNS, caching or security details.
• Evidence such as the meta tag in public page source, the TXT record, the file URL.

Do not include passwords, hosting login credentials or DNS API keys. Posticy may request additional evidence of ownership or authorized control. Manual investigation does not bypass Marketplace review.