SEO

Google Search Console for an online store: sitemap, indexing, reports

Google Search Console for an online store: verify with a meta tag, submit the sitemap, fix "Discovered, not indexed" and read the weekly reports.

The CloudCart team15 min read
A dashboard with a clicks and impressions chart above an online storefront, thin lines running from it to a sitemap and a list of indexed pages
In this article · 12 sections
  1. What Google Search Console is and why your store needs it
  2. How to add your online store to Search Console
  3. How to submit your sitemap in Search Console
  4. How to check whether a page is indexed
  5. Why a page is not indexed: the reasons in the Pages report
  6. How to remove a page from Google fast
  7. How to see which searches find you: the Performance report
  8. The reports that drive growth: what to check every week
  9. Search Console and an AI assistant: Google's numbers next to your orders
  10. Search Console when you change platform
  11. 7 Search Console mistakes that cost traffic
  12. Frequently asked questions

In short: Google Search Console is Google's tool that shows which searches your store appears for, how many clicks each page gets and which products are not indexed. Connecting an online store takes about 15 minutes: add the domain, verify it with a meta tag, submit sitemap.xml and see the first data within a few days.

This guide is by the CloudCart team for stores selling in or from Bulgaria and across the EU, including stores with a Bulgarian and an English version. The CloudCart facts come from the platform documentation and the SEO and blog page; Search Console is described from Google's own help center.

What Google Search Console is and why your store needs it

Search Console is the dashboard where Google tells a site owner what it sees: which pages are indexed, which searches they show up for, how often people click and which errors get in the way. The data comes from Google itself, and the Performance report keeps the last 16 months (Google Search Console Help: Performance report).

For a store it does three jobs: it shows which products and categories are not indexed (and get no search visitors at all), which keywords sit on page two and could reach the top 3 with a better title, and which problems pull the whole site down, such as a blocked robots.txt, manual actions or a slow mobile version.

ToolAnswers the questionTypical numbers
Google Search ConsoleHow people find me in GoogleImpressions, clicks, CTR, position, indexed pages
Google Analytics 4What visitors do in the storeSessions by channel, events, conversions
CloudCart AnalyticsHow much I sold and from where36 reports: sales, orders, conversion, landing pages by sales, abandoned carts

How to add your online store to Search Console

Add the store as a "URL prefix" property and verify it with an HTML meta tag placed in CloudCart. A "Domain" property can only be verified with a DNS record (Google: Add a website property), and the CloudCart app works with the meta tag, so that is the shortest route. A URL prefix covers one exact address: https://yourstore.bg and https://www.yourstore.bg are two properties. Use the main domain from Settings → Domains, because CloudCart builds canonical URLs and the sitemap address from it.

  1. Open Search Console. Sign in at search.google.com/search-console with a company Google account, not the personal one of an employee who might leave.
  2. Add a property. Choose "URL prefix" and enter the exact main address.
  3. Pick the "HTML tag" method. Copy the whole line <meta name="google-site-verification" content="…" />.
  4. Paste it into CloudCart. Admin → Apps → Google Search Console (install it if needed) → Settings. Paste the full tag into the verification code field and save.
  5. Verify. Back in Search Console, click "Verify". The store puts the tag in the <head> of every page, so the check passes at once.
  6. Add colleagues. Settings → Users and permissions: "Full" for whoever does SEO, "Restricted" for people who only look.

Important: paste the whole meta tag, not only the code after content=, or verification fails. Keep the app active: if you switch it off, the tag disappears and Google drops the verification on its next crawl.

If verification passes and the store still does not show in Google, check the plan. A store on a trial or expired plan returns Disallow: / in /robots.txt whatever you wrote in Marketing → SEO, with no warning in the admin. Once the plan is paid, the block lifts by itself.

How to submit your sitemap in Search Console

A sitemap is an XML list of every public URL, so Google finds new products without waiting for links. CloudCart builds it at https://your-domain/sitemap.xml; you submit it once.

  1. Copy the address. Admin → Marketing → SEO → Sitemap card; one click copies it.
  2. Submit it. Search Console → Indexing → Sitemaps → paste → "Submit".
  3. Check the status. It should read "Success" with a count of discovered URLs. "Couldn't fetch" on a new store usually means a trial plan blocking crawlers.
  4. Add it to robots.txt. Marketing → SEO → Robots.txt → add Sitemap: https://your-domain/sitemap.xml. The line is not added for you, and it helps Bing and other crawlers.

The CloudCart sitemap is an index of separate maps for products, categories, brands, pages and posts, up to 1,000 URLs each: a store with 60,000 products has 60 product files. Products carry their main 600 × 600 image for Google Images, and noindex pages (cart, checkout, account) stay out. A new product appears within an hour. You do not resubmit after changes, because Google rereads the address by itself (Google: Sitemaps report), and "discovered" is not the same as indexed.

How to check whether a page is indexed

Paste a product URL into URL Inspection in the top bar of Search Console. Google tells you whether the page is indexed, when it was last crawled, which canonical it chose and whether it found product data (Google: URL Inspection tool).

  • "URL is on Google". Indexed. If it does not rank, work on the text and title.
  • "URL is not on Google". The reason is shown below, the same as in the Pages report.
  • "Test live URL". Checks the page now; use it after a fix.
  • "Request indexing". Adds the page to the crawl queue. Requests per day are limited, so keep them for a new category, a campaign product or a fixed page.

Crawling can take a few days to a few weeks, and repeated requests do not speed it up (Google Search Central: Ask Google to recrawl).

Why a page is not indexed: the reasons in the Pages report

Indexing → Pages groups every URL outside the index by reason (Google: Page indexing report). Filtered category variants, the cart and redirected old URLs should be out. It is a problem when products and categories that sell are on the list.

Reason in Search ConsoleMeaningWhat to do in CloudCart
Discovered, currently not indexedKnown, not crawled yetOn a new store wait 2 to 4 weeks; link the product from its category and the home page
Crawled, currently not indexedRead and judged not worth keepingYour own description instead of the supplier's, specifications, photos, reviews; merge near-identical products into variants
Blocked by robots.txtCrawler not allowed inCheck the plan and Marketing → SEO → Robots.txt
Excluded by "noindex" tagThe page asks not to be indexedNormal for filters, cart and account. The filter threshold never affects products; to index filtered categories, raise it (0 to 5) in Marketing → SEO → Deindex Filtered and Sorted pages
Duplicate without user-selected canonicalSame content, no canonicalCheck Marketing → SEO → Canonical tag is on (default)
Not found (404)The URL does not exist301 to a new model or the category in Marketing → SEO → 301 Redirects
Soft 404Exists but looks emptyEmpty categories: fill, hide or redirect them

What "Discovered, currently not indexed" means

Google has found the URL, usually in sitemap.xml, and postponed the crawl so as not to overload the site. On a new store with thousands of products this is expected and the number falls over a few weeks. If it does not, Google sees the pages as unimportant: internal links from categories and the home page, links from other sites and unique texts help. "Crawled, currently not indexed" is more serious and in stores almost always means the manufacturer's text, copied on many other sites. How to write descriptions Google keeps is in the ecommerce SEO checklist.

How to remove a page from Google fast

The Removals tool hides a URL within hours, but only for about 6 months (Google: Removals tool), so make the permanent fix in the store the same day: hide or delete a test product, set a 301 for a discontinued one, and let the filter threshold keep sorting and filter URLs out. Do not block such a page in robots.txt: the crawler then cannot read noindex and the URL stays in Google without a description (Google Search Central: Block indexing with noindex).

How to see which searches find you: the Performance report

Search Console → Performance → Search results → Queries shows impressions, clicks, CTR (clicks divided by impressions) and average position for every query. A low CTR at a good position points to a weak meta title or description. Impressions in AI Overviews and AI Mode are counted here too, under the "Web" search type, with no separate filter (Google Search Central: AI features and your website). For AI assistants, a CloudCart store also publishes /llms.txt, which you write in Marketing → SEO → Llms.txt file.

How to find the keywords that reach the top 3 fastest

  1. Pick 3 months. A week is too short for a store with modest traffic.
  2. Turn on all four metric cards so they show as columns.
  3. Sort by position. Look at queries from 5 to 15 with at least 100 impressions: Google already finds the page relevant.
  4. Check the Pages tab for the query. Two of your pages for one query compete with each other.
  5. Improve the page. Keyword at the start of the meta title and in the H1, a paragraph that answers the question, 2 or 3 internal links.
  6. Compare after 4 weeks with Date → Compare. Daily numbers mislead.

Type your store name into the query filter and choose "Queries not containing": what is left is people who do not know you yet, the real growth from SEO.

A store with a Bulgarian and an English version

Open the Countries tab in Performance and compare Bulgaria with Romania, Greece, Germany and the other markets you ship to: the same English page can rank in one country and barely show in another. With the Multilang app each language version is its own site on its own domain or subdomain, such as en.yourstore.bg, with hreflang generated automatically and the main store as x-default. Add each domain as a separate property and submit each sitemap.xml. How the versions work together is in the guide to multilanguage, multicurrency and multistore.

The reports that drive growth: what to check every week

Twenty minutes a week is enough, in this order:

ReportWhat you look atActionHow often
Performance → QueriesPositions 5 to 15, CTR below averageNew meta title and description, category textWeekly
Performance → PagesPages with falling clicksCheck stock and priceWeekly
Indexing → PagesNew 404s, "Crawled, not indexed"301s, your own descriptionsWeekly
Sitemaps"Success", discovered countA sharp drop: check robots.txt and domainMonthly
Core Web VitalsMobile URLs in "Poor"Lighter images and bannersMonthly
Product snippets, Merchant listingsPrice, availability, review errorsComplete product data; if missing, check the themeMonthly
Security and Manual actionsPenalties, hacked contentWrite to support@cloudcart.com at onceGoogle emails you

Why the mobile version decides rankings

Google indexes and ranks by the mobile version (Google Search Central: Mobile-first indexing), so text, specifications and reviews missing on the phone are missing for Google. Good thresholds are LCP up to 2.5 s, INP up to 200 ms and CLS up to 0.1 (web.dev: Web Vitals); a common cause of "Poor" is a heavy banner or video at the top of the home page. More in the guide to your store's mobile version. Product data reports appear only if the theme outputs Product structured data: test one product in the Rich Results Test.

Search Console and an AI assistant: Google's numbers next to your orders

The Google Search Console app in CloudCart only verifies the store; it does not pull queries or clicks into the admin. The fastest way to tie keywords to sales is an AI assistant connected to the store, which reads orders and products through the CloudCart API while you hand it the Search Console export.

  1. Export. Performance → "Export" → CSV or Google Sheets, 3 months.
  2. Create a read-only key. Settings → PAT Tokens → Read Only with an expiry date, optionally limited by IP. For saving meta titles or redirects later, create a separate key with write rights.
  3. Connect. Paste the sentence from the AI assistant for CloudCart page into Claude Code, ChatGPT Codex, Gemini CLI, Cursor or VS Code. It talks to you in English.
  4. Ask. "Here is the Search Console export. Match pages with orders from the last 90 days and show me categories with many impressions and few sales."

Which metrics to tie to sales

MetricWhereWhat it decides
Non-brand clicksSearch Console, "Queries not containing" the store nameWhether SEO brings new customers
Sales by landing pageCloudCart → Analytics → Landing pages by salesWhich entry page brings orders
Sales by traffic sourceCloudCart → Analytics → Sales by traffic sourceOrganic search revenue against Google Ads, Meta Ads, TikTok Ads and email

That report splits organic Google from paid traffic by itself: gclid goes to Google Ads, fbclid to Meta Ads, ttclid to TikTok Ads, and UTM-tagged email visits to email. The order is credited to the first visit, excluding shipping, so the google.com row is your SEO revenue. A page with good sales at position 8 is the quickest win. Tables in the interface stop at 1,000 rows, while one Search Analytics API request returns up to 25,000 (Google: Search Analytics query), so an assistant you give API access to sees the long searches by model, size and color too.

Search Console when you change platform

Moving from WooCommerce, Shopify, Magento or OpenCart, Search Console shows whether rankings held. Every old URL gets a 301 to its new match, and the property stays if the domain stays.

  1. Export the old URLs first. Performance → Pages, 16 months: each one with clicks needs a 301.
  2. Import the redirects. Marketing → SEO → 301 Redirects → import from CSV.
  3. Move the verification tag into Apps → Google Search Console before the domain switches.
  4. Submit the new sitemap.xml and remove the old one.
  5. Watch for two weeks for new 404s and falling clicks; every 404 with old clicks gets a 301.

A renamed product or category in CloudCart redirects from its old URL for 30 days; after that, add a permanent 301. The full plan is in the guide to migrating from WooCommerce without losing SEO.

7 Search Console mistakes that cost traffic

  1. The wrong address. http:// or no www while the store answers elsewhere: almost no data.
  2. Only the code pasted instead of the whole <meta> line.
  3. A trial plan. Robots.txt blocks everything until the plan is paid.
  4. Disallow: / in robots.txt. Hides the whole store.
  5. Sold-out products deleted without a 301. Years of rankings gone.
  6. An indexing request for every product. The quota runs out; the sitemap and internal links do this job.
  7. Judging by one day. Compare 28 days with the previous 28.

Frequently asked questions

Add a "URL prefix" property with the exact main domain, choose "HTML tag" and copy the whole meta tag. Paste it into Apps → Google Search Console → Settings in CloudCart, save, click "Verify" and submit sitemap.xml.

In Search Console open Indexing → Sitemaps, paste https://your-domain/sitemap.xml and click "Submit". You do it once; Google rereads it on its own.

URL Inspection and Indexing → Pages show the reason. For stores the usual ones are: not crawled yet, thin or copied content, robots.txt on a trial plan, noindex, or a deleted product returning 404. Request indexing only after the fix.

Google knows the URL but has not visited it yet. On a new store it clears within a few weeks; if not, add internal links and unique descriptions.

From a few days to a few weeks, according to Google. A new CloudCart product enters sitemap.xml within an hour; internal links speed up the crawl more than repeated requests.

No. The app only places the verification tag. To tie the data to orders, export the Performance report and give it to an AI assistant connected with a read-only PAT token.

Questions about Search Console and SEO for your CloudCart store? Write to support@cloudcart.com.

Sources

  1. Google Search Console Help: Performance reportsupport.google.com
  2. Google: Add a website propertysupport.google.com
  3. search.google.com/search-consolesearch.google.com
  4. Google: Sitemaps reportsupport.google.com
  5. Google: URL Inspection toolsupport.google.com
  6. Google Search Central: Ask Google to recrawldevelopers.google.com
  7. Google: Page indexing reportsupport.google.com
  8. Google: Removals toolsupport.google.com
  9. Google Search Central: Block indexing with noindexdevelopers.google.com
  10. Google Search Central: AI features and your websitedevelopers.google.com
  11. Google Search Central: Mobile-first indexingdevelopers.google.com
  12. web.dev: Web Vitalsweb.dev
  13. Rich Results Testsearch.google.com
  14. Google: Search Analytics querydevelopers.google.com
The CloudCart teamChecked against the platform documentation. Questions: support@cloudcart.com

Build your online store

The first 3 months on every plan are €1/month. Questions: support@cloudcart.com

Create a store for €1