Verification problems
PageNora must read your one-time code on your website before it checks anything. You create the code and start the check in the setup guide (Start setup or Finish setup), or under Settings › Websites & setup, Verify your website. The guide looks for the code by itself while it is open (press Check now to look at once), and the website shows Verified when PageNora has read it. If it cannot find your code, work through this list in order. Almost every case is one of the first five.
The checklist
- The code is old. A code is valid for 48 hours after you create it. Press Show my code again to refresh it: you get the same code for the same website, with a fresh 48 hours.
- The published code is not the current one. If you pressed Make a new code, the old code stopped working. Replace what you published with the new code.
- The code was copied wrongly. It is case sensitive and can contain hyphens, underscores and a dot. Use the Copy button; do not retype it. No spaces before or after.
- The page is not public. Open the page address in a private window. A draft, password-protected, private, “coming soon” or members-only page cannot be read.
- The address is not exact. The page method works at
/pagenora-verification/with or without the trailing slash, including a redirect between the two on the same address. The file method needs exactly/.well-known/pagenora-verification.txt. The website name you typed must be the one visitors end up on. - The title is not exact (page method). It must read
PageNora verification: YOURCODE. Your site name may follow it after a separator, but nothing may come before it. - The address redirects. PageNora must receive the page directly from the address it checks. If
example.comredirects towww.example.com, publish the proof on, and give us, the finalwwwaddress. If your website sends PageNora from one to the other, the setup guide names the address it was sent to and offers to use that address instead. Nothing is verified until the code is found there. - HTTPS is broken. Only https addresses are read, so an expired or mismatched certificate stops verification.
- A firewall or security plugin blocks the request. Bot protection such as Cloudflare’s can turn automated visitors away. See “My security plugin or firewall blocks the checks” in Troubleshooting.
- A cache is serving the old page. Clear your site and CDN caches after publishing.
Which method works on which platform
- WordPress (including WordPress.com): the page method is easiest. WordPress.com sites cannot serve a custom file from the
.well-knownfolder, so use the page. - Squarespace and Wix: the page method works on any plan. The file method is generally not possible. The tag method needs a place to add code to every page’s head, which depends on your plan.
- A site you or a developer host yourself: the file method is the cleanest; the tag method also works.
Menu names on these platforms change from time to time. If you cannot find a setting, search that platform’s help for the words in quotes.
Monitoring stopped after it was working
PageNora re-reads your proof about once a day. If the page, file or tag is gone, it stops checking your site and does not guess. Typical causes: the verification page was deleted or set back to draft, a theme change removed the tag, or a site migration dropped the file. Publish it again (press Show my code to see your code), then press Check my code now. If your site was simply down when PageNora looked, your authorization is kept and re-read within about 15 minutes. An outage does not switch monitoring off.
I removed a website and want it back
Remove website (under Settings › Websites & setup) un-verifies the website, so it needs verifying again. Add it again in the same section, press Show my code (you get the same code as before), make sure the proof is still published, and press Check my code now. Its pages come back paused with their history, and you can resume them with Resume monitoring. If you only want checks to stop for a while, use Pause all pages (also under Websites & setup) instead, which keeps the website verified.
Another PageNora account already uses this website
If you see “This website is already verified in another PageNora account”, your proof was found, but the website is proved by a different PageNora account. A website can be verified in one PageNora account at a time. Your proof can sit beside theirs (the page title and the text file can each hold several codes, one after another), so the other account has to remove the website first (Settings › Websites & setup) before you can verify it. If you think this is a mistake, use the contact form.
The domain is already claimed
Asking for a code does not claim a domain. Ownership is shown only by publishing the proof on the site itself, which only someone controlling the site can do. So nobody can lock you out by requesting your domain first. If something odd happens, write to support.
Is it safe to leave the verification page up?
Yes. The code is useless to anyone else: only a one-way fingerprint of it is stored on our side, it proves nothing about your accounts and it gives no access to anything. Keep the page up for as long as you want monitoring. It can be hidden from search engines and from your menu.