Google Search Console Access for Dealerships
If Search Console was set up by a website vendor or former team member, you may not have your own login yet. That is common on franchise rooftops. You do not need the old Gmail account. With DNS access (or a ticket to your website partner), you can verify a Domain property, add your dealership as an owner, and start seeing indexing, rankings, and Generative AI performance in one place.
Dealerships can set up or reconnect Google Search Console without the old agency Gmail. Add a Domain property for the root domain (example.com), publish the google-site-verification TXT record at the authoritative DNS zone (@ or blank host), click Verify, and keep the record permanently. DNS propagation can take up to 2-3 days. After verification, review Users and permissions so your store holds at least one Owner, and remove unused ownership tokens when partners change. When the website vendor manages DNS, send a support ticket with the exact TXT value. URL-prefix verification via HTML tag, GA4, or GTM works as an interim option until DNS is in place.
Domain properties cover http/https, www, and subdomains in one Search Console view.
DNS TXT verification does not require the old Google account login.
Never delete the verification TXT record; Google periodically re-checks it.
After removing an owner, also review Unused ownership tokens on the same settings page.
Website vendors often manage DNS; a support ticket with the exact TXT string is usually enough.
Allow up to 2-3 days for DNS propagation before retrying verification.
After access: link GA4, export history before vendor switches, run the AI visibility playbook.
Why Your Dealership Needs Its Own Access
Google Search Console is the first-party source for how Google crawls, indexes, and ranks your site. With it, you can see which pages earn impressions, which queries drive clicks, whether new content is indexed, and how you appear in Google's Generative AI performance report.
Many dealerships rely on a website vendor or agency to hold the Search Console property. That arrangement works until someone changes roles or vendors. The fix is straightforward: verify the domain on an account your store controls. Google's DNS verification method does not require the old login. Any Google account your dealership owns, plus one TXT record at your domain, makes you a verified owner.
Domain Property vs URL-Prefix
For dealerships, default to a Domain property ( yourdealership.com). It rolls up http and https, www and non-www, and all subdomains in one view. That is the scope you want when you are auditing inventory pages, blog content, and service landing pages together.
A URL-prefix property ( https://www.yourdealership.com/) only covers that exact protocol and path prefix. It can be verified faster with an HTML tag or Google Analytics, but it covers a narrower slice of your site. Use URL-prefix as a temporary option when DNS access is not available yet.
Domain properties require DNS verification (TXT or CNAME). URL-prefix properties support HTML file, meta tag, Google Analytics, and Google Tag Manager. See Google's property types guide for the full comparison.
Find Who Controls DNS
Before you open Search Console, figure out where DNS records are edited. That is not always the company that sold you the domain.
Run a WHOIS lookup on your root domain. Note the registrar (GoDaddy, Namecheap, etc.) and the nameservers.
If nameservers point to a website vendor (DealerOn, Dealer.com, Dealer Inspire, Dealer Teamwork, or similar), the TXT record must be added in their DNS panel, not necessarily at the registrar.
Log into whichever system manages the active zone. If you only have registrar login but nameservers are delegated elsewhere, registrar DNS edits will not work.
The Four-Step Setup Path
01
Find who controls DNS
Use WHOIS to identify your registrar. If nameservers point to a website vendor, you will need a support ticket, not registrar login.
02
Add a Domain property
In Search Console, choose Add property, select Domain, and enter your root domain (example.com, no https or www).
03
Publish the TXT record
Copy the google-site-verification string, add a TXT record at @ (or leave Host blank), save, and do not delete it after verification.
04
Verify and review access
Click Verify (allow up to 2-3 days for DNS propagation). Then open Users and permissions to confirm the right dealership accounts have access.
Add the Site in Search Console
Sign in to Google Search Console with any active Google account your dealership controls (a group alias works if it is a real Google Account).
Open the property selector (top left) and choose Add property.
Select the Domain card on the left. Enter your root domain only (e.g.
smithford.com), withouthttps://orwww.Click Continue. Search Console displays your verification record. Keep this tab open.
UI reference: Add a website property to Search Console
Add the DNS TXT Record
Copy the verification string Search Console provides. It looks like this:
google-site-verification=AbCdEfGhIjKlMnOpQrStUvWxYz1234567890
Open your DNS provider's record editor (registrar or website vendor).
Create a new record: Type TXT, Host/Name @ (or leave blank), Value = paste the full string, TTL = default.
Save the record. Do not modify the string. Do not add quotes unless your provider requires them.
Never delete the TXT record after verification. Google periodically re-checks it. If the record is removed later, access can lapse even after a successful verify.
Most sites use TXT. If Search Console offers CNAME instead, follow Google's CNAME instructions only when the Admin Toolbox shows an existing CNAME chain. When unsure, use TXT. Provider-specific steps: Google Workspace DNS documentation by provider.
| Provider | Host field | Notes |
|---|---|---|
| GoDaddy | @ | DNS Management > Add Record > TXT. Host @ maps to the root domain. |
| Namecheap | @ or blank | Advanced DNS tab. Some accounts accept a blank Host field instead of @. |
| Cloudflare | @ | DNS only (gray cloud). Proxying does not block TXT lookup, but edit the authoritative zone Cloudflare serves. |
| Amazon Route 53 | blank | Leave the record name empty for the apex domain in the hosted zone. |
| Google Domains / Squarespace | @ | Custom records under DNS settings. TTL default is fine. |
Verify and Troubleshoot
Return to Search Console and click Verify. If it fails immediately, wait. Google states manually installed DNS records can take up to 2-3 days to propagate. Retry after 24-48 hours.
Before you retry, confirm the record is live with the Google Admin Toolbox: enter your apex domain, select TXT, and look for your google-site-verification= string in the results.
| Error message | Likely cause | Fix |
|---|---|---|
| Your verification DNS TXT record was not found | DNS has not propagated yet, or the record is in the wrong zone. | Wait 24-72 hours. Confirm the TXT record appears in Google Admin Toolbox dig lookup for your apex domain. |
| Your verification record did not match | Wrong string pasted, extra spaces, or record on www instead of apex. | Copy the exact value from Search Console. Host should be @ or blank for a Domain property, not www. |
| We could not find your domain | Typo in the property name or domain not resolving. | Enter example.com only. Confirm the domain resolves in a browser. |
| Nameserver mismatch | TXT added at registrar while the live zone is at the website vendor. | Find active nameservers via WHOIS. Add the record where those nameservers are managed. |
Review Users and Permissions
Once verified, open Settings > Users and permissions. Confirm your dealership has at least one Owner on an account you control. From there, add partners who need reporting access and remove accounts that no longer need entry after vendor or staff changes.
Removing someone from the user list does not always remove their verification token. After an owner leaves the account, open Unused ownership tokens on the same page and remove any tokens tied to accounts that should no longer hold owner access. See Google's permissions guide.
| Role | Capabilities | Dealer use case |
|---|---|---|
| Owner (verified) | Full control, add/remove users, link GA4 and Ads, all reports. | Dealership principal email or marketing director. At least one verified owner required. |
| Owner (delegated) | Same as verified owner, granted by an existing owner without a DNS token. | Agency account when a dealer owner adds them. Can be revoked without DNS changes. |
| Full user | View all data, submit sitemaps, URL inspection, most tools. | Minimum for SEO vendors and content platforms reporting on your behalf. |
| Restricted user | Limited view rights on most reports. | Usually enough for reporting partners. Owner is only needed for linking GA4/Ads or full admin. |
Website Vendor Ticket Template
Most franchise dealers work with a website vendor or OEM IT partner for DNS. That is normal. Send the ticket below to your website support contact and CC your marketing lead so everyone stays aligned.
Subject: Add Google Search Console DNS verification TXT record Please add the following DNS TXT record to our root domain ([YOURDOMAIN.com]): Type: TXT Host/Name: @ (or leave blank for root domain) Value: [PASTE google-site-verification=... STRING FROM SEARCH CONSOLE] TTL: Default (3600 is fine) Important: Do not remove this record after verification. Google re-checks it periodically. Please confirm when the record is saved so we can click Verify in Search Console.
When sharing access with partners, Full user is usually enough for reporting. Reserve Owner for dealership-controlled accounts, or when GA4 or Google Ads linking requires it.
When DNS Verification Is Impossible
If DNS changes have to go through your website partner and take longer than expected, you can add a URL-prefix property in the meantime. Verification options per Google's verification methods:
HTML meta tag on the public homepage (requires template access).
Google Analytics (same Google account with Edit rights in GA4; gtag in
<head>).Google Tag Manager (Publish or Admin permission; container snippet immediately after opening
<body>).
These methods are easier to set up quickly, but they cover less ground than a Domain property. Plan to move to DNS verification when your partner can add the TXT record.
Multi-Rooftop and Subdomain Notes
One Domain property per rooftop domain. A Chevy store and a Ford store in the same group need separate properties if they use separate domains.
Buying Centers and trade-in microsites on subdomains (e.g.
buyingcenter.dealer.com) may need their own property if they live on a different hostname. Verifying the parent domain covers all subdomains; verifying only a subdomain does not cover the parent.Use a dealership-owned Google account as a verified owner. A shared agency Gmail can work short term, but a store-controlled account (or Google Group) makes handoffs easier when vendors or staff change.
After You Are In
Link Google Analytics 4 under Settings > Associations for unified reporting.
Export historical performance before any vendor switch (16 months of queries and pages is a useful baseline).
Run the AI visibility measurement playbook using GSC Generative AI performance, branded search filters, and GA4 AI referrers.
If pages are not indexing, read why Google won't index your website before reviewing whether the issue is content quality or technical indexing.
If you get stuck, note your DNS provider name and the exact error message from Search Console. Those two details determine the fix path.
Questions Dealer Teams Ask
Do I need the old agency’s Google login to recover Search Console?
No, if you can add a DNS TXT record at the authoritative zone for your domain. DNS verification grants you verified owner status without access to any prior Gmail account. You only need the old login if you are trying to recover a URL-prefix property verified exclusively through HTML or a tag you cannot edit.
Will verifying kick out my website vendor?
No. You add yourself as an additional verified owner. Existing users keep access until permissions are updated under Settings > Users and permissions. Many dealers add their own owner account first, then adjust partner access once reporting is working.
How long until Search Console data appears?
Google begins collecting data when anyone adds the property, even before verification. After you verify, reports typically populate within a few days. Historical data only exists from the date the property was first added to any Search Console account.
My vendor says they already have Search Console. What should I ask for?
Ask for the exact property name (Domain vs URL-prefix), your permission level, and addition of a dealership-controlled Google account as Owner or Full user. If access cannot be granted that way, DNS verification on a Domain property is a straightforward path that only requires a DNS change from whoever manages your domain.
Verification failed: record not found. What now?
Wait 24-72 hours for propagation. Confirm you edited the zone that matches your live nameservers (WHOIS). Use Google Admin Toolbox to look up TXT records on your apex domain. If the record is missing there, Google cannot see it either.
Can I use GA4 to verify instead of DNS?
Only for a URL-prefix property (https://www.example.com/), not a Domain property. You must use the same Google account that has Edit permission in GA4, and the gtag snippet must be in the head of your public homepage. Domain properties require DNS verification.
Should I remove the TXT record after we are verified?
No. Google periodically re-checks verification tokens. Removing the TXT record can cause you to lose owner access. Keep it permanently, even after verification succeeds.
From Access to Measurement
Search Console access is the prerequisite. These pages cover what to do once you can see the data.
Direct Search Console Access Makes Everything Else Measurable.
Once your property is connected, Hrizn can report against GSC-matched content paths: impressions, clicks, and indexing proof tied to the pages we publish. This guide gets you there.
That advantage grows every month.
See the PlatformWe Rise Together.