{"title":"Analyze search performance","slug":"measure-search-performance","url":"https://support.storeconnect.com/articles/measure-search-performance","url_markdown":"https://support.storeconnect.com/articles/measure-search-performance.md","subtitle":null,"summary":"Verify your store with Google Search Console, submit your sitemap, and read the reports that show which queries bring shoppers to your store and which pages search engines could not index.","type":"Help_Documentation","video_url":"","keywords":"google search console, search console, bing webmaster tools, site verification, submit sitemap, indexing, coverage report, search queries, seo measurement, crawl errors, store not appearing in google, site discoverability","last_modified":"2026-08-21T07:12:35+0000","body_markdown":"Google Search Console is a free tool from Google that reports how your store performs in\nsearch results: which queries showed your store, which pages are indexed, and which pages\nGoogle tried to read and could not.\n\nUse this process to verify your store with Search Console, submit your sitemap, and read\nthe reports it produces. It also covers what to check when your store is not appearing in\nsearch results at all.\n\nSet Search Console up early, before you need it. Search data is not backfilled, so\nverifying today is what gives you something to compare against in three months.\n\n## Before you begin\n\nYou need:\n\n-   A Google account.\n-   Your store's live domain, on a store that has been released. A store in\n    [Stealth Mode](stealth-mode) cannot be indexed.\n-   Access to either your DNS records or the store's head content block.\n\n## Verify your store\n\nVerification proves to Google that you own the site. Two of Google's methods suit a\nStoreConnect store, and you only need one of them.\n\nUse **DNS verification** if you can edit your domain's DNS records. It covers every store\non the domain at once, including subdomains, and it survives theme changes. Use **HTML\ntag verification** for a single store when you cannot reach the DNS records.\n\n:::warning\n\nLeave the verification record or tag in place permanently. Removing it unverifies the\nproperty, and you lose access to the reports and their history.\n\n:::\n\n### Verify with a DNS record\n\n1.  Open [Google Search Console](https://search.google.com/search-console/about) and add\n    a **Domain** property, entering your domain.\n2.  Copy the TXT record Google provides.\n3.  Add the TXT record to your domain's DNS with your registrar or DNS host.\n4.  Return to Search Console and select **Verify**. DNS changes can take a few hours to\n    propagate, so retry later if it fails the first time.\n5.  Confirm the property now appears in your Search Console property list.\n\n### Verify with an HTML tag\n\n1.  Open [Google Search Console](https://search.google.com/search-console/about) and add\n    a **URL prefix** property, entering your store URL.\n2.  Choose the **HTML tag** method and copy the `\u003cmeta\u003e` tag Google provides.\n3.  Add the tag to your store's head content block. See\n    [Adding custom JavaScript, CSS and head content](adding-custom-javascript-css-and-head-content).\n4.  Publish the change, then view the page source of your live storefront and confirm the\n    tag is there.\n5.  Return to Search Console and select **Verify**.\n\n## Submit your sitemap\n\nStoreConnect generates a sitemap for each store automatically and refreshes it daily.\nSubmitting it tells Google where to find every page you want indexed.\n\n1.  Open `your-store.com/sitemap.xml` in a browser and confirm it loads.\n2.  In Search Console, open **Sitemaps** and submit `sitemap.xml`.\n3.  Check back after a day or two. Search Console reports how many URLs it discovered and\n    any it could not read.\n\nEach store on a multi-store domain has its own sitemap, so submit each one against its\nown property. See [Manage the sitemap for your store](sitemap-file) for what qualifies a\nrecord to appear in it.\n\n:::note\n\nStores in [Stealth Mode](stealth-mode) have no sitemap, and `/sitemap.xml` returns a 404.\nThat is expected while a store is unreleased, and it also means the store cannot be\nindexed yet.\n\n:::\n\n## Which reports to read\n\n| Report | What it answers | Worth checking |\n|---|---|---|\n| **Performance** | Which queries showed your store, and which were clicked | Monthly |\n| **Pages** (indexing) | Which pages are indexed, and why others are not | Monthly |\n| **Sitemaps** | Whether your sitemap was read, and how many URLs were found | After launch, then quarterly |\n| **Page experience** | Loading speed and layout stability on real visits | Quarterly |\n\nTwo patterns in the **Performance** report repay attention:\n\n-   **Many impressions, few clicks** — your **Meta Title** and **Meta Description** are\n    not persuasive enough to earn the click. Both are a quick fix on the record itself.\n    See [SEO and site data](seo-and-site-data).\n-   **Queries you rank for but never targeted** — content opportunities, in the shopper's\n    own words. This is the most reliable keyword research available to you, because it\n    comes from your actual customers rather than an industry average.\n\n## When your store is not appearing\n\nWork through these in order before assuming something is broken.\n\n1.  **Give it time.** A new store or page is not indexed immediately. Days to weeks is\n    normal, and nothing you do speeds this up reliably.\n2.  **Check the store is not in Stealth Mode.** A stealth store is deliberately\n    unavailable to search engines. See [Stealth Mode](stealth-mode).\n3.  **Check `robots.txt`** is not disallowing the pages. See\n    [Edit robots.txt to prevent search engine indexing](robots-txt).\n4.  **Check for a stray noindex tag**, particularly if the page was once a staging or test\n    page. See\n    [How to implement 'noindex' tags on specific pages using Liquid](how-to-implement-noindex-tags-on-specific-pages-using-liquid).\n5.  **Check the page is in your sitemap.** If it is not, it has not met the conditions in\n    [Manage the sitemap for your store](sitemap-file).\n6.  **Check something links to the page** from elsewhere on your store. A page nothing\n    links to, and that is absent from the sitemap, has no route in.\n7.  **Run the URL Inspection tool** in Search Console on the specific page. It reports\n    what Google saw on its last visit, and why the page was or was not indexed.\n\n:::tip\n\nSearching for your own store in Google is a poor test, because results are personalized\nand cached. The **Pages** report and **URL Inspection** tell you what is actually indexed.\n\n:::\n\n## Other search engines\n\nBing Webmaster Tools works the same way and can import your Search Console settings\nrather than repeating the verification. It is worth doing once, since Bing results also\nfeed several AI answer engines.\n\nSearch Console does not report on whether AI tools cite your store. See\n[Answer engine and generative engine optimization (AEO/GEO)](answer-engine-optimization)\nfor how to check that separately."}