Map your stack & establish ownership
Know where each change belongs before changing anything.
A domain registrar, DNS provider, website builder and analytics account can be four different systems. DNS proves ownership; it does not install tracking. A staging site lets you test without changing the public experience.
Your implementation route
In Domains, identify whether Wix actually manages your DNS. If it does: Domain actions → Manage DNS records → add the Search Console TXT value. If not, add it at your authoritative DNS provider. Keep existing mail and verification records.
Platform boundaries & account requirements
Use Wix's native integrations and SEO & GEO tools. Backend examples belong in a supported Wix backend module or an external service, never in a page embed.
Open Wix ↗Domain/DNS access, website administrator access and a Google account owned by the business.
Follow the steps
Check only after completingWrite a one-page system inventory
Record the production URL, primary hostname, registrar, authoritative DNS provider, website platform, repository (if any), CDN, forms/checkout provider and named owner. Record account names, not passwords.
Create a recovery point
Export current DNS records and SEO/analytics settings. Back up code and database where applicable. Create a staging copy or theme preview and record exactly how to restore the previous release.
Verify Search Console
Add a Domain property, copy its TXT verification value and add a new TXT record at the authoritative DNS host. Leave other TXT records intact. Verify and retain the record. URL-prefix verification is a narrower alternative when DNS access is unavailable.
Record the starting measurements
Choose five revenue pages. Save their status, index state, mobile performance and conversion path. Record today's qualified leads/orders and organic sessions using consistent definitions. New properties may have no historical data.
Implementation recipes
Expand · choose · copy</>Inspect a public responseOpen recipe
Run locally. Replace example.com with your domain. These commands do not change the site.
# Inspect the final public response and headers.
$response = Invoke-WebRequest -Uri 'https://example.com/' -Method Get
$response.StatusCode
$response.Headers
# Also inspect redirects in your browser's Network panel.
# A 200 status does not prove that useful content was rendered.Open the public HTTPS domain, verify ownership in Search Console, and find the saved recovery instructions. Confirm that another authorized business owner can access the key accounts.
Remove only a mistaken new DNS record, restore the specific saved value, or revert the preview/release. Do not reset nameservers or delete unrelated verification records.
Read the primary instructions
Guidance checked October 7, 2026. “2027” describes this prototype’s visual concept, not a prediction of platform rules.