Pick the property type first
Search Console has two property types. A Domain property (example.com) covers every subdomain and both http and https, and includes www automatically. It must be verified with a DNS record. A URL-prefix property (for example the https version of www.example.com) covers only URLs that start with that exact prefix, treats http and https separately, and accepts several verification methods. [1]
That choice decides the rest. If you own a custom domain, a Domain property is usually the better choice, because it still works if you later change from www to the bare domain or move to another builder. If your site lives on a builder subdomain you don't control, such as a free Carrd or Framer address, you can't add DNS records, so a URL-prefix property with the HTML tag is the only route.
This guide summarises Google, Carrd, Framer and systeme.io documentation read on 30 October 2026. It is research, not a record of us verifying these sites ourselves.
Google's methods and what keeps them working
Google notes that manually added DNS records can take up to two or three days to be served. If verification later fails, you are notified, and permissions expire after a grace period. The homepage must not require a login for the HTML tag method. [2]
| Method | Property types | Keep in place? |
|---|---|---|
| DNS record at your domain provider | Domain (required); also URL-prefix | Yes. Google says not to remove the record even after verification succeeds. |
| HTML tag (meta tag in the homepage head) | URL-prefix only | Yes. Search Console checks for the tag periodically. |
| HTML file upload | URL-prefix only | Yes. The file must sit in the site root under the exact name Search Console gives; none of the Carrd, Framer or systeme.io pages we read describe a way to do that. |
| Google Analytics or Tag Manager snippet | URL-prefix only | Yes, unmodified, and you need the right permissions on the Analytics or Tag Manager account. |
What each builder lets you edit
The DNS route is the same everywhere because it happens at your domain registrar, not in the builder. That makes it the most portable choice for anyone who expects to change platforms.
| Builder | HTML tag route | DNS route | Plan note |
|---|---|---|---|
| Carrd | Publish, Settings, Meta Tags. Enter the tag in name=content form: google-site-verification=your-code. | Add a TXT record at your domain registrar. | Meta tags and custom domains both need Pro Standard ($19/year) or higher. [3][4][5] |
| Framer | Paste the meta tag at the end of the head code in the site's General settings, save and republish. | Add the DNS record Google gives you at your registrar. Framer's guide mentions DNS verification only in passing and gives no steps. | Framer's guide does not state a plan. A custom domain needs a paid plan from Basic up. [6][7] |
| systeme.io | Not documented for Search Console. Its page tracking code header field places code inside the page head, which is where Google expects the tag; verify after adding it. | Add a TXT record at your domain host. systeme.io does not manage your DNS; you add its CNAME records there yourself. | The help articles we read don't state a plan requirement. [8][9] |
Worked example: a Carrd site on a custom domain
- You have a Pro Standard site published at www.example.com and the domain registered elsewhere.
- In Search Console, add a Domain property for example.com. Google shows a TXT value.
- Add the TXT record at your registrar without deleting the A and CNAME records Carrd needs. Carrd uses an A record for @ and a CNAME pointing www to the bare domain. [5]
- Click Verify. If it fails, wait: Google says new records can take up to two or three days. [2]
- Alternative if DNS access is awkward: add a URL-prefix property for the exact address visitors use (for example the https version of example.com if Carrd forwards www to it) and use Carrd's Meta Tags field. [3][5]
Submit the sitemap
Carrd says all sites include an automatically generated sitemap.xml at /sitemap.xml. Framer also generates one at /sitemap.xml; its guide has you enter sitemap.xml in the Sitemaps report and press Submit. [4][6]
Google calls a sitemap "merely a hint": submitting it doesn't guarantee crawling. A single sitemap is limited to 50MB uncompressed or 50,000 URLs, far above what a small builder site produces. [10]
systeme.io's SEO help mentions that Google uses your sitemap.xml and that pages re-enabled for indexing need a manual indexing request in Search Console. Pages are hidden from search engines by default, so untick "Hide from search engines" on pages you want found before submitting anything. [11]
First-week checks
Google says it can take "a week or so" to start crawling and indexing a new site, and that validating a fix typically takes up to about two weeks. For a new site it recommends requesting indexing of the homepage first. [12]
| When | Check | What a problem looks like |
|---|---|---|
| Day 1 | URL Inspection on the homepage; request indexing | Blocked by robots.txt or marked noindex |
| Day 1 | Sitemaps report shows the sitemap as read | Could not fetch, or zero discovered URLs |
| Days 2 to 7 | Page indexing report | "Discovered - currently not indexed" means Google found the page but rescheduled the crawl; noindex or 404 on pages you want indexed needs fixing |
| Day 7 | Run a site: search for your domain | Nothing yet is common in week one; recheck before changing anything |
Common mistakes
- Verifying the http version of example.com as a URL-prefix property while the site serves the https version of www.example.com. Prefix properties cover only their exact prefix. [1]
- Removing the meta tag or TXT record after the green tick. Both must stay. [2]
- Switching builders and forgetting that a meta tag lived in the old builder. A DNS-verified Domain property keeps working through the move.
- Leaving a page set to noindex during preview and submitting the sitemap anyway.
Questions before you decide
Should I use DNS or the HTML tag to verify a builder site?
Use DNS if you control the domain. Google says a DNS record is the only way to verify a Domain property, which covers www, non-www, http, https and subdomains. Use the HTML tag for a URL-prefix property, such as a free builder subdomain.
Which Carrd plan lets me add the Google verification meta tag?
Carrd's meta tag setting requires Pro Standard or higher. You enter it in name=content format, such as google-site-verification followed by your code.
Can I remove the verification tag after Search Console accepts it?
No. Google checks periodically for the tag or DNS record. If it can no longer confirm the token, you are notified and permissions expire after a grace period.
How long before a new site shows up in Search Console reports?
Google says it can take a week or so to start crawling and indexing a new site. It recommends requesting indexing of the homepage first.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Google Search Console Help: add a website property Accessed 30 Oct 2026
- Google Search Console Help: verify your site ownership Accessed 30 Oct 2026
- Carrd: setting up meta tags Accessed 30 Oct 2026
- Carrd: setting up a sitemap Accessed 30 Oct 2026
- Carrd: using a custom domain Accessed 30 Oct 2026
- Framer Help: connect Google Search Console to your Framer site Accessed 30 Oct 2026
- Framer pricing Accessed 30 Oct 2026
- systeme.io Help: is it possible to insert HTML, CSS or JS code? Accessed 30 Oct 2026
- systeme.io Help: connect your domain to systeme.io Accessed 30 Oct 2026
- Google Search Central: build and submit a sitemap Accessed 30 Oct 2026
- systeme.io Help: the Search Engine Optimization section Accessed 30 Oct 2026
- Google Search Console Help: Page indexing report Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.