Search data
Google Search Console for ecommerce stores
Search Console is the only place a store sees what Google actually did with its catalog: which queries brought clicks, which product URLs are indexed, which are not and why, and whether product markup was read. In most stores it is opened when traffic falls rather than used as the working record of an SEO program.
Google Search Console
Search data · by Google. A text wordmark, not a logo: we are not affiliated with the vendor and make no claim to its trademarks.
What we do with it
The work inside Google Search Console
Properties that match how the store is built
A domain property covers every subdomain and protocol, which is what most stores need. We add prefix properties for the sections that deserve their own numbers, such as a blog subfolder or a separate market, and give each country or language site its own view so a decline in one market is visible rather than averaged away.
Query and page data read by template
Individual product URLs rarely tell you much on their own. Grouping performance by template answers the useful questions: are collection pages winning category terms, are product pages only appearing for brand and model numbers, and is the blog attracting queries that never lead to a product.
Indexing as a catalog problem
For a store with thousands of URLs, the page indexing report is the main diagnostic. Variants treated as duplicates, filtered URLs crawled and discarded, out of stock pages dropped, and pages Google found but chose not to crawl each point to a different fix in the site structure rather than a content problem.
Product structured data checked at scale
The enhancement reports show whether product markup was parsed and where it raised errors or warnings across the catalog. That is faster than testing pages one at a time, and it is where a bad price format or a missing availability value on a whole template becomes obvious.
Page experience and field data
The Core Web Vitals report is based on real visits rather than a lab test, grouped into similar pages. It tells you whether a slow product template is affecting many URLs or a few, which is the difference between a theme fix and a single image someone uploaded at full size.
When it fits
Google Search Console is the right tool when
Every store doing organic work of any kind
There is no substitute source. Third-party tools estimate; this reports what Google recorded for your property, including the queries no keyword tool knows about because nobody else ranks for them.
Large catalogs where indexing is the constraint
When a store has more URLs than Google chooses to crawl, growth comes from fixing which pages get attention, and this is where that decision becomes visible.
Stores relying on product rich results
Price, availability and review markup change how a listing appears. The enhancement reports show whether Google could read them across the catalog rather than on the one page you tested.
What to watch
Where accounts drift
Facts about defaults and costs, not criticism. These are the settings we check on every account.
History is finite unless it is exported
Performance data is retained for a rolling window measured in months, not years. Without an export set up in advance, the comparison a store wants during next year's planning simply does not exist.
Filtered totals will not add up
Rare queries are withheld for privacy, and clicks are counted per query and property in ways that do not sum neatly across filters. Read the direction of travel rather than treating any figure as an exact count.
Average position hides more than it shows
One number averages every impression, including appearances far down the results for queries the store never intended to target. Clicks and impressions by page group are a more reliable signal of whether work is landing.
Access outlives the people who set it up
Verification is often held by an agency or a former employee, and losing it during a platform migration is a genuine setback. Ownership should sit with a company account, with access granted from there.
AI surfaces are not a simple filter
How clicks from AI-assisted results are counted is set by Google and has changed over time, so check the current documentation before drawing conclusions. In practice we read the totals here alongside referral and server data rather than assuming a single report explains the change.
How is Search Console different from analytics for an online store?
It reports what happened in Google search before the click: impressions, queries and position. Analytics reports what happened after it. Neither can replace the other, and the handover point between them is where most confusion about traffic changes comes from.
Why do clicks here not match sessions in our analytics?
They measure different events with different rules. A click is counted when someone leaves the results page; a session depends on tracking, consent and how the visit is grouped. A steady gap is normal. A gap that suddenly changes usually means a tracking change rather than a traffic change.
Should a store with several markets use one property or several?
Several, plus a domain property for the whole picture. Market-level views are what let you see that one country is growing while another is flat, and they make it obvious when a hreflang or indexing problem is confined to a single region.
What does the indexing report tell a store with a large catalog?
Where crawl attention is going. Large counts of pages found but not crawled, or crawled and not indexed, usually point at faceted URLs, thin variant pages or an internal linking structure that buries most of the catalog. Those are architecture fixes, not copywriting fixes.
Delivered through
Works alongside
Find the leak.
A free Growth Analysis ranks what your store should fix first, by revenue at stake.