Run
Site verification
Prove the site is yours to Google, Bing, Meta, and others, with their tags or files.
Search engines, ad platforms, and social networks ask you to prove a site is yours before they show you its data or let it run ads. Most give you a <meta> tag to put in your home page's <head>; some give you a file to host. Mockly adds the tags to every published page from Site settings, and hosts the files from public/.
Adding a tag#
Open Site settings in the editor's sidebar, and under Site verification, click Add a tag…. Pick the service, and its card asks for its code:
- Paste the whole tag the service gives you, such as
<meta name="google-site-verification" content="…" />. Mockly reads the code from it, and the card says Read from the tag you pasted. - Or type the code alone, the tag's
content.
The ⓘ beside the field says where the service shows its tag, and the card's ⋯ menu links to the service's own help. A code that isn't the service's says so under the field, with what one looks like, and another service's tag says whose it is.
Changes save as you make them, and reach the live site with your next publish: publish before you click Verify in the service. Each version keeps its tags, so History shows when they changed, and restoring a version brings its tags back.
To remove a tag, open its card's ⋯ menu and choose Remove. Some services check again later, so keep a tag while you use the service.
The services#
| Service | Its tag | What to choose in the service |
|---|---|---|
| Google Search Console | google-site-verification | Add the site as a URL prefix property, then Other verification methods › HTML tag |
| Bing Webmaster Tools | msvalidate.01 | Add the site manually, then Meta tag authentication |
| Yandex Webmaster | yandex-verification | Meta tag on the home page |
| Meta | facebook-domain-verification | Meta Business Suite, Settings › Brand safety › Domains, then Add a meta-tag |
p:domain_verify | Link to Pinterest, Claim beside Websites, then Add HTML tag | |
| X account | twitter:site | Your username, acme, @acme, or your profile's address: cards of links shared on X credit it |
Other tags#
For a service that isn't on the list, such as Baidu, Naver, or Ahrefs, choose Other tag. Paste the whole <meta> tag into either field, and its Name and Content are both read from it. A site can have up to 10.
An other tag is a <meta> tag with a name and content, and nothing else: no scripts, no http-equiv. Some names can't be used, because Mockly writes those tags itself:
description,viewport,theme-color,color-scheme, andreferrer, which pages write.robots,googlebot, and the like: whether search engines index the site follows Search engines in Site settings, and each page'snoindex.og:andtwitter:tags, which pages write from their title, description, and image. Fortwitter:site, add the X account.
A second person verifying with the same service, such as a colleague's Google account, adds their tag as an other tag with the service's name.
Verifying with a file#
Some services offer a file instead. Mockly hosts three, from public/, where each service reads it. Upload them in the Files panel:
| File | Where it's served | What it must be |
|---|---|---|
Google's HTML file, google….html | /google….html | As Google gives it: only google-site-verification: google….html |
security.txt (RFC 9116) | /.well-known/security.txt | Text with a Contact and an Expires field |
Apple Pay's apple-developer-merchantid-domain-association | /.well-known/apple-developer-merchantid-domain-association | The text file your payment provider or Apple gives you |
Uploaded by name, security.txt and Apple Pay's file go in .well-known/ by themselves. A file that isn't what its service reads is refused, saying why.
Where they work#
Tags are in the <head> of every published page, the not-found page too, and never in the editor's preview. Files are served at your site's address.
A site's address is a path, such as /s/acme/launch. Services that verify a whole domain, such as Meta, Apple Pay, and security.txt, read the domain's own home page and /.well-known/ folder, so they need the site at its domain's root. Google Search Console's URL prefix properties, and Pinterest, can verify a site at a path. If you take payments with Stripe, register your domain in Stripe's dashboard instead: it handles Apple Pay's verification itself.