Skip to content
AlldleDocs

Verify your domain

Verifying proves the site is yours, so nobody else can list or claim your game. It is also what sends a draft to review. Either method works, and Alldle checks for both each time.

Your token and the exact values are on the game’s Verify page in My games, or from an assistant with get_verification_steps. Each game has its own token.

  1. Paste the tag into the <head> of your game’s page, the one at the address you listed.

    <meta name="alldle-verify" content="your-token">

  2. Deploy the change, and open your page’s source to confirm the tag is there.

  3. Press Verify now.

This works anywhere you control the HTML. Where it goes depends on your setup:

Setup Where the tag goes
Plain HTML, Vite, GitHub Pages index.html, inside <head>
SvelteKit src/app.html, inside <head>
Next.js metadata.other in the root layout: { 'alldle-verify': 'your-token' }
Nuxt app.head.meta in nuxt.config, with server rendering on
Astro Your layout’s <head>
WordPress A header plugin, or your theme’s header.php

What happens next

Section titled “What happens next”

As soon as the check passes on a draft, the game goes to the review queue and you get an email. If it does not pass, nothing changes, and you can try as often as you like.

Leave the tag or record in place afterwards. It does no harm, and it saves you doing this again if you ever need to.

When the check fails

Section titled “When the check fails”

The message is always the same: Neither the HTML meta tag nor the DNS TXT record was found. These are the usual reasons.

The tag is added by JavaScript

Section titled “The tag is added by JavaScript”

Alldle reads the HTML your server sends, and it does not run scripts. In a single-page app, or with a tag added by a component at runtime, the tag is not in that HTML.

To see what Alldle sees, run this and look for alldle-verify:

Terminal window
curl -s https://your-game.example | grep alldle-verify

If nothing comes back, put the tag in your static index.html or your server-rendered template, or use the DNS method.

The tag is on a different page

Section titled “The tag is on a different page”

The check reads the exact address you listed. If your game is at example.com/play, the tag has to be on /play, not only on your home page.

Your site blocks bots

Section titled “Your site blocks bots”

A bot challenge, or a firewall rule, can answer the check with something other than your page. The check also gives up after 5 seconds. Use the DNS method, which never touches your site.

The DNS name uses the wrong host

Section titled “The DNS name uses the wrong host”

The record belongs to the host in your game’s address, including any subdomain:

Game address Record name
https://example.com _alldle.example.com
https://www.example.com _alldle.www.example.com
https://play.example.com _alldle.play.example.com

Many providers add your domain by themselves, so in their form the name may be only _alldle or _alldle.www. Check the result with:

Terminal window
dig +short TXT _alldle.your-domain.com @1.1.1.1

Alldle asks the public resolvers 1.1.1.1 and 8.8.8.8, so once they answer, the check will find it.

The value is not exact

Section titled “The value is not exact”

The DNS value has to be exactly alldle-verify=your-token, with the prefix. In the meta tag the content is the token alone, with no prefix. Tokens are per game, so one copied from another game fails.

You cannot edit the HTML or the DNS

Section titled “You cannot edit the HTML or the DNS”

On itch.io or another shared address, the HTML or the domain may not be yours to change. Write to us and we will verify it by hand.

If you move your game

Section titled “If you move your game”