Connect Google Search Console to SiteOps

0 of 8 done

1. 1Open Search Console and sign inGo to search.google.com/search-console and sign in with your Google account. If this account has never used Search Console, you land straight on a welcome screen that asks you to add a property. If it already has properties, open the property picker at the top left and look for an option to add a property.Use the Google account you plan to connect to SiteOps later. It keeps things simple — the account that verifies is automatically allowed to read.
2. 2Choose the property type: Domain or URL prefixGoogle offers two ways to add a site. A Domain property covers everything at once — www and non-www, http and https, and all subdomains — and verifies only through DNS. A URL-prefix property covers one exact address, such as https://www.example.com, and offers more verification methods: an HTML file, an HTML tag, Google Analytics or Google Tag Manager. If you can edit DNS, pick Domain — it is the one-and-done option. If DNS is out of reach, pick URL prefix and type the exact address of your site, including https and www if you use them.With URL prefix, the address must match exactly. If your site lives at https://www.example.com and you verify https://example.com, the reports stay empty.
3. 3For a Domain property: copy the DNS TXT recordAfter you enter your domain, Google shows a TXT record — a line of text that starts with google-site-verification=. Copy it. Then open your DNS host in another tab — that is wherever your domain's DNS lives: your registrar, Cloudflare, or your hosting panel. Find the section for managing DNS records and add a new record with type TXT, host or name set to @ (meaning the bare domain), and the copied text as the value. Save it. If you chose URL prefix instead, skip to the next step.

   Your DNS hostDNS records

   typehostvaluestatus

   TXT@google-site-verification=abc123…propagating

   Host @ means the bare domain — not www, not a subdomain. Paste the value whole, with no spaces around it.

   Leave the Search Console tab open while you do this — you will come back to it to press Verify.

4. 4For a URL-prefix property: upload the HTML file or add the tagGoogle recommends an HTML file: download the small file it offers and upload it to the root folder of your site, so it opens at yoursite.com/google...html. If you cannot upload files, expand the other methods and pick HTML tag: copy the meta tag and paste it into the head section of your home page — most site builders and CMSes have a spot for custom head code or verification tags in their settings. If your site already runs Google Analytics or Tag Manager under the same Google account, those methods can verify with no changes at all.The file or tag must stay in place permanently. If it is removed later, verification eventually lapses and the connection can break.
5. 5Press Verify and wait if neededBack in Search Console, press Verify. File and tag methods usually confirm within seconds. DNS can take longer — new TXT records typically show up within an hour, but some DNS hosts take up to a day. If Google says it cannot find the record yet, that is normal: wait and press Verify again later. Search Console keeps the pending property, so nothing is lost.If it still fails after a day, check the record for typos, and make sure it was added to the bare domain, not to a subdomain like www.
6. 6Confirm data is flowing in Search ConsoleOnce verification is green, look for the Performance section in the left-hand menu of Search Console. A brand new property starts empty — Google needs a day or two to backfill search data after verification. An older site that was just verified gets months of history filled in shortly. You do not need to wait for this to connect SiteOps, but seeing numbers here first makes the next steps easier to trust.
   1. Search Console
   2. Performance
7. 7Connect in SiteOpsIn SiteOps, open Settings, find Google Search Console under Search, and press Connect. A Google window opens asking you to choose an account and allow read-only access to Search Console data. Pick the account that verified the property, or an account that was added as a user on it, and allow.

   SiteOpsConnect Googleno password asked here

   you're sent to Google

   Google asksas the account that verified the property

   • view your Search Console data

   Allow

   a token comes back

   SiteOpsConnectedaccess token••••••••••••••••revocable on Google, anytime

   If the Google window lists several accounts, pick carefully — choosing an account with no access to the property is the most common reason the connection succeeds but stays empty.

   1. Settings
   2. Search
   3. Google Search Console
8. 8Pick the property and check the project pageIf the account has more than one Search Console property, SiteOps asks which one belongs to this project — pick the one you just verified. Then open your project page. The search card should show clicks, impressions and average position, and the keywords table starts filling with the queries your site ranks for.Search Console data always runs about two days behind — that is Google's delay, not SiteOps. Do not expect today's clicks to appear today.