Check property scope and authority
Publish only the token offered for the authorised Search Console property, after checking whether a Domain property covers other owners' subdomains.
Verify only through an authorised Google account and DNS owner. A Search Console Domain property covers subdomains and protocols, so check who else uses them before publishing a token. Verification grants property access, not hosting administration or indexing. Use the exact method and value offered for this property.
Before editing, identify the current authoritative DNS provider. A hosting panel can display a zone that is not live. Record the existing records at the required owner name, especially SPF, mail, CAA and any other Search Console owner tokens. Preserve them.
Copy the exact offered TXT or CNAME pair
In Search Console’s verification flow, choose the DNS record type the flow offers and copy its exact host/name and value or target. Google documents both TXT and CNAME DNS methods. A TXT value is not an SPF policy even though both use the TXT type. Add a separate TXT record; do not edit an existing v=spf1 string or remove another owner’s verification value. For CNAME, the offered record has its own name and target. A CNAME cannot coexist with other data at that same owner name, so stop and use another supported method or ask the DNS owner if there is a conflict.
Read the DNS provider’s field preview. Some panels append the zone automatically, and entering a full name in such a field can create a doubled hostname. Use the exact owner name Search Console specifies, not a guessed apex or www location.
Add the record only at the active authority
At the provider named by the domain’s delegated nameservers, create the offered record without replacing unrelated entries. Save the previous zone view and the new record’s owner, type and value. If the registrar, DNS host and Novasean account are different organisations, the person with DNS authority makes this change. A customer login to Novasean does not itself grant editing rights at an external DNS provider.
Query the authoritative nameserver for the exact record type and owner after saving. Compare its answer with the Search Console token privately. If the authority has the value but a recursive resolver does not, allow for the old answer’s TTL or negative cache; avoid changing the record repeatedly while caches expire.
Complete verification and keep the token
Return to the same Search Console verification prompt and choose Verify. If it fails, first check the property and Google account, exact owner name, record type, target/value and authoritative response. A provider can take time to begin serving a new record; a panel’s Saved message is not proof that the public DNS answer has changed. Google’s troubleshooting view can also show whether its tool sees the offered TXT or CNAME.
A useful check compares Google's offered token with the authoritative TXT or CNAME at the exact owner name; a successful DNS answer still requires Search Console's own Verify result.
Once verification succeeds, keep the required DNS record. Google says removing a manually installed DNS record can lose verification. If an agency handover changes ownership, coordinate token changes with every legitimate owner instead of deleting other tokens on sight. Verification is an access check, not a promise of crawling or search visibility.
Restore an accidental DNS change
If mail or another service fails immediately after the edit, compare the saved zone with the current authoritative answer. Restore any SPF, MX or other record you accidentally replaced, while keeping the new verification record separate where possible. If the CNAME conflicts with existing data, remove only the new failed CNAME after documenting it and choose a supported alternative with the owner. Ask the DNS provider or Novasean support for the exact record and query results, never the Google login or account password.
Frequently asked questions
Must I use TXT? No. Follow the method Search Console offers for the property and DNS configuration; Google also documents CNAME where appropriate.
Can I delete the token after Google says Verified? Keep it unless Google’s current account guidance and all property owners confirm a replacement verification path.
Does verification put my site in results? No. It establishes control of the property, not eligibility or inclusion.
Does DNS verification give website-hosting access? No. It can grant Search Console ownership for the Domain property, including its subdomains; check the intended account and scope.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.