Landinker

Custom domain

By default, your group publishes landings on a Landinker subdomain (your-group.landinker.com). With a custom domain you can serve them on your own domain — for example example.com or www.example.com — with HTTPS.

This feature is available in the Pro and Enterprise plans and is managed by the Owner under Group settings → Custom domain.

Adding a domain

1. Under Group settings → Custom domain, type your domain (e.g. example.com, without http:// or paths) and click Add.
2. The domain enters the Pending status, and we show you the DNS records you need to create at your provider (where you bought the domain).

Configuring DNS

You will see two records to copy:

Create both records with your DNS provider exactly as shown (you can copy them using the copy button).

DNS propagation can take anywhere from a few minutes up to 24-48 hours.

Verifying

Once you've added the records, click Verify. Landinker queries DNS and, if it finds the correct TXT record:

• The domain status updates to Verified.
• Your landings go live on your domain with an SSL certificate (HTTPS).

If the record is not found yet, the domain shows an Error with details; wait for propagation and click Verify again. You can retry as often as needed.

Check DNS (Diagnostics)

If something isn't working and you're unsure why, click Check DNS. Instead of a simple "verified / unverified", it displays the status of each record individually:

We also tell you where to set them up: we query your domain's nameservers — which unambiguously identify who manages your DNS, even if purchased elsewhere — and provide instructions for that provider's control panel, using the exact field names they use. We recognize Vercel, Cloudflare, GoDaddy, Namecheap, Squarespace (formerly Google Domains), Hostinger, and DonWeb; if you use another, we provide general instructions.

The most common mistake: some panels expect a short record name (_landinker) while others expect the full name (_landinker.yourdomain.com). If you enter the full name in a panel expecting the short one, the domain ends up duplicated and never resolves, with no error message. That's why we show both formats, prioritizing the one that matches your provider.

An "older" record that remains valid

Vercel updated its IP range and currently provides two valid values for the A record. If you set up your domain earlier and have the previous IP, diagnostics will mark it as correct with a clarifying note: no need to change it.

"DNS is correct, domain provisioning pending"

This is a specific scenario worth knowing: DNS can be completely correct while the domain still doesn't load, because server provisioning is pending. When this occurs, diagnostics states this explicitly rather than sending you to review records that are already fine. Click Verify for us to retry.

HTTPS certificate

With DNS in order, diagnostics also checks the certificate serving your domain and informs you how long it remains valid. It renews automatically as long as the domain points to Vercel, so normally you will see "valid until…" and nothing more. It warns you if:

• Expired or not valid for your domain: browsers block the site with a security warning, even if DNS is fine.
• Approaching expiration without renewal: still functional, but renewal is delayed. Verify that DNS still points to Vercel, that no CAA record blocks Let's Encrypt, and that the domain does not pass through a proxy (such as Cloudflare's orange cloud).

How many domains you can connect

Your plan determines how many domains you can connect: Pro includes one, and Enterprise has no limit. Beneath the input field you can see how many are currently in use.

Important: the limit counts domains, not addresses. Subdomains of an already connected domain do not consume an extra slot, so with the Pro plan you can have yourdomain.com, www.yourdomain.com, and store.yourdomain.com simultaneously — it is a single domain configured in multiple ways, not three.

Each is added separately (with its own DNS records), but only the first consumes a plan quota.

Always connect www in addition to the root domain. Many visitors type it out of habit, and if not connected they won't reach your site.

Google Search Console

Google discovers your pages automatically: each domain serves its own robots.txt with its sitemap URL. Search Console is optional and allows you to view how Google finds you (queries, clicks, indexed pages) and notify it when publishing new content.

If you want to use it with your custom domain:

1. In Search Console, add your domain. The most comprehensive option is the Domain property, verified with a TXT record in your DNS (the same place where you configured Landinker).
2. If you prefer a URL prefix property, select the HTML Tag method and paste the code in Settings → Integraciones → Google Search Console (you can paste the entire tag). Save and click Verify in Search Console.
3. Submit the sitemap: https://yourdomain.com/sitemap.xml.

Landings served on your Landinker subdomain don't need any of this: Landinker already reports them to Google.

Removing a domain

From the same screen you can delete a domain. Your landings will stop being served there immediately. You can re-add it later (new records are generated).

If you downgrade to a plan without custom domains, your domains stop serving, but you can still view and remove them in settings.