Weebly and Wix Search Console Verification: Every Method That Actually Works
Neither Weebly nor Wix lets you upload Google's HTML file, and their working routes differ. Every verification method for both builders, step by step.
Hosted builders don't let you touch the server, so Google's default verification method (uploading an HTML file) is off the table on both Weebly and Wix. The routes that work:
- WEEBLY: THE SEO HEADER CODE FIELD: Settings, then SEO, then Header Code. Paste Google's meta tag, save, publish, verify. Publishing is the step people miss; the tag isn't live until you do.
- WIX: THE SEO SETUP CHECKLIST: Wix connects and verifies with one click through its SEO Setup Checklist, if you're on a Premium plan with a custom domain. The meta tag route covers everyone else.
- EITHER: A DNS TXT RECORD: With a custom domain you can verify at the registrar instead, which survives theme changes, plan changes and both builders' quirks.
- THEN THE SITEMAP: Both builders generate /sitemap.xml automatically. Submit it once in Search Console and you're done; there's nothing to install.
Verification is five minutes on either platform. The mistake that costs people a week is forgetting to hit Publish on Weebly.
CrawlRaven works from the Search Console property this guide helps you verify, joining it daily with GA4 and a 200-point crawl. Builder sites earn that join the same as any other: the platforms differ only in where the verification tag goes, which is exactly what this page covers. Try CrawlRaven free: 1 site, no credit card →
Google's recommended verification method is uploading an HTML file to your site's root directory. On Weebly and Wix, you can't. Neither builder exposes the root of your site, so the default instructions every generic guide repeats simply don't apply.
The good news: both platforms have routes that work in about five minutes, and one of them (DNS) is actually stronger than the method you're locked out of. Here is every option, per platform.
How you can verify on Weebly vs Wix
| Verification method | Weebly | Wix |
|---|---|---|
| One-click connect | Not offered | SEO Setup Checklist (Premium + custom domain) |
| HTML meta tag | Settings, then SEO, then Header Code | Yes, via the SEO settings |
| DNS TXT record | With a custom domain, at the registrar | With a custom domain, at the registrar |
| HTML file upload | No root file uploads | No root file uploads |
Why the HTML file method won't work here
Verification is Google asking you to prove control of the site. There are four accepted proofs, and hosted builders support two and a half of them:
- HTML file upload: needs root file access. Not available on either platform, at any plan level.
- HTML meta tag: needs a way to inject code into the site header. Both platforms provide one.
- DNS TXT record: needs control of the domain's DNS. Available whenever you own a custom domain, regardless of builder.
- Google Analytics or Tag Manager: works if the same Google account runs your analytics, but ties verification to that setup surviving.
The meta tag is the pragmatic first choice on both platforms, so that's where the steps below start.
Verify a Weebly site, step by step
- In Search Console, add a property. Choose URL prefix and enter your site's address exactly as it loads.
- Choose the HTML tag method and copy the
google-site-verificationmeta tag. - In Weebly, open Settings → SEO.
- Paste the tag into the Header Code field and save. This field injects into every page's head, which is exactly what Google wants.
- Publish the site. The tag does not go live until you do. This is the single most common failure on Weebly.
- Back in Search Console, click Verify.
Saving updates your draft; publishing updates the site Google sees. A verification tag sitting in a saved-but-unpublished draft fails verification every time, and the error message won't tell you why. When a Weebly verification fails, publish first and ask questions later.
Verify a Wix site, step by step
The one-click route (Premium + custom domain)
- Open Wix's SEO Setup Checklist from your dashboard's Marketing & SEO area.
- Follow the Connect to Google step and sign into the Google account that should own the property.
- Grant the permissions. Wix creates and verifies the Search Console property automatically.
Two requirements gate this route: a Premium plan and a connected custom domain. If either is missing, the checklist won't connect, and the manual route below is your path.
The manual meta tag route
- Add the property in Search Console (URL prefix) and copy the HTML tag, as with Weebly.
- In Wix, open your SEO settings and find the verification / custom meta tags area for your site's head.
- Paste the tag, save, and publish if your plan requires a publish step.
- Click Verify in Search Console.
The DNS route that outlives both builders
If you own a custom domain, consider skipping in-builder verification entirely:
- In Search Console, add a Domain property (the left-hand option) rather than a URL prefix.
- Copy the TXT record Google shows you.
- Add it at your DNS host: your registrar, or the builder's DNS panel if the domain lives there.
- Verify. Propagation can take from minutes to a day; Search Console lets you retry without penalty.
Why bother? Three properties of the DNS route the meta tag can't match:
- It covers everything at once: www and bare domain, http and https, every subdomain, one property.
- Nothing inside the builder can break it: theme changes, plan changes, an overzealous cleanup of the header code field.
- It survives replatforming. Move from Weebly to Wix to anything else, and the verification, the property, and its history come with you.
Submit the sitemap both builders already made
Weebly and Wix each generate an XML sitemap at yourdomain.com/sitemap.xml and keep it current automatically. Wix structures it as a sitemap index with per-content-type subsitemaps; submit the index and Google follows the rest. In Search Console: Sitemaps → enter sitemap.xml → Submit.
Curious what the builder actually put in there? Our sitemap extractor lists every URL, and the sitemap validator checks the file against the protocol before Google reads it.
Search Console setup, start to finish
When verification fails anyway
- Weebly: tag present but verification fails. Publish. Then confirm in the live page source. If the tag renders and Google still balks, retry after a few minutes; the fetch can lag the publish.
- Wix: checklist won't connect. Confirm both gates: Premium plan, custom domain connected. A wixsite.com subdomain can't use the checklist and needs the manual tag.
- DNS record not found. Propagation isn't instant. Check the record actually saved at the host that serves your DNS (registrar vs builder is a common mix-up), then give it up to 24 hours.
- Verified, then lapsed later. Google re-checks proofs periodically. A deleted header tag or DNS record un-verifies the property days later. Restore the proof and the property returns intact.
Once verified, treat the property as the start line. The Page indexing report tells you what Google did with the builder's pages, and the same setup on Squarespace is covered in its own guide if you run sites there too.
Frequently asked questions
How do I verify my Weebly site with Google Search Console?
Use the meta tag method. In Search Console, add your site as a URL-prefix property and choose HTML tag verification. Copy the meta tag, then in Weebly go to Settings, then SEO, and paste it into the Header Code field. Save, publish the site, and click Verify in Search Console. It usually passes within seconds of publishing.
Why won't my Weebly Search Console verification work?
Nine times out of ten: the site wasn't republished after adding the tag. Weebly only pushes Header Code changes live when you click Publish, and Google can only see the published site. Check by viewing your live homepage source and searching for google-site-verification. If it's missing, publish and verify again.
How do I connect Google Search Console to Wix?
The fastest route is Wix's SEO Setup Checklist, which connects and verifies your site with one click once you grant Google permissions. It requires a Premium plan and a connected custom domain. Without those, verify manually instead: add the property in Search Console and place Google's meta tag through Wix's SEO settings.
Can I use Google Search Console on a free Wix or Weebly site?
Yes, with limits. You can verify a free subdomain site (yoursite.wixsite.com or yoursite.weebly.com) using the meta tag method and see its data in Search Console. Wix's one-click checklist route won't be available, and any SEO progress is tied to a subdomain you don't own. Move to a custom domain before investing real effort.
Can I upload Google's HTML verification file to Weebly or Wix?
No. The HTML file method requires uploading a file to your site's root directory, and neither Weebly nor Wix exposes root file access on standard plans. This isn't a problem: the meta tag method proves ownership just as well, and a DNS TXT record at your registrar is stronger than either.
Where is my Weebly or Wix sitemap?
At yourdomain.com/sitemap.xml on both platforms, generated and updated automatically. Wix organizes it as a sitemap index with subsitemaps per content type (pages, blog posts, products), which Search Console handles fine: submit the index URL and Google reads the rest. On Weebly, submit the single sitemap.xml.
How long until Search Console shows data for my Weebly or Wix site?
Expect roughly 2 to 3 days before the first Performance data appears on a newly verified property, sometimes up to a week. The property collects from verification onward and never backfills. Indexing data in the Pages report typically shows up before query data does. Empty reports in week one are normal, not broken.
Does Wix's SEO Setup Checklist replace Google Search Console?
No. The checklist is a guided setup layer: it verifies your site, submits basics to Google, and walks you through metadata. The actual reports (queries, indexing, Core Web Vitals, manual actions) live in Search Console itself. Treat the checklist as the on-ramp and Search Console as the destination.
Should I verify with the meta tag or a DNS record?
If you have a custom domain, DNS is the more durable choice: it survives theme edits, plan changes, and anything that happens inside the builder, and it verifies every subdomain and protocol variant at once as a Domain property. The meta tag is faster and fine for a first setup; DNS is what you graduate to.
I moved from Weebly or Wix to another platform. Does verification carry over?
Meta tag verification breaks the moment the old site stops serving the tag, since Google re-checks it periodically. DNS verification survives a platform move untouched, because the record lives at your registrar, not on the site. That's the strongest argument for doing DNS verification before a migration, not after.
15+ years of growing SaaS websites through SEO | Author, 200-Point Audit Checklist
Aditi has spent 15+ years helping SaaS companies scale organic traffic through technical SEO and content strategy. She is the author of the CrawlRaven 200-Point Audit checklist used by agencies and in-house teams to systematically improve search performance.