Google Search Console · Usage guide (SEO & data)
The search-engine view of your store: indexing, queries, errors, and field performance data.
FREE · ESSENTIAL
Why I use it
- Nothing else shows as faithfully what Google has actually indexed, excluded, or queued on your domain.
- Performance reports tie queries and pages to field data (not just a static crawl).
How I use it : mini guide
On every new client I verify the property (DNS or file), then lock in a reading routine.
- Overview & coverage : Start with index status: valid pages, exclusions, server errors, soft 404s. I note recurring patterns before touching the theme.
- Performance (3 months) : Filter by strategic URLs (home, top collections, best-selling PDPs). I look at impressions vs CTR to prioritise titles and snippets.
- Core Web Vitals & experience : Cross-check each URL with PageSpeed and production. GSC vs lab gaps are often the argument that convinces stakeholders.
- After every deploy : Watch crawl stats and new errors for 7–14 days. A theme deploy or app can break canonicals or tags.
I rarely rely on legacy “enhancement” reports when JSON-LD is already clean : I validate with the Rich Results Test on a live URL instead.
Concrete Shopify example
Fashion store: impressions dropped on filtered collections. GSC showed parameterised URLs as “crawled, not indexed”. Fix: strict canonicals + internal links to clean URLs ; traffic recovered over ~4 weeks.
Limits I've identified
- No competitor or global search volume data : that’s Ahrefs or another source.
- Indexing lag can hide a recent bug : I pair with crawl logs when the stack allows.
- CTR in GSC is averaged : for fine behaviour I add GA4 and Clarity.
Alternatives if you don't want to pay
- Bing Webmaster Tools for a complementary Bing view (low friction).