Google Search Console Strategies for SEO | Matthew Mellinger
With Matthew Mellinger, Co-founder of SEO Gets · Streamed live · 57 min
What this episode covers
Matthew Mellinger walks through how to use Google Search Console data in practice, covering trends over single numbers, page-level data, content groups, GA4 key events, cannibalization, and striking-distance queries. He also demonstrates the SEO Gets dashboard, annotations, and its MCP connector. The main conclusion is that Search Console data should be read directionally and in business context, not literally.
Key takeaways
- ✦Read Search Console data as directional trends and check page-level data, since query data is anonymized.
- ✦Group pages into content groups by funnel stage so commercial pages are tracked separately from top-of-funnel traffic.
- ✦Set up GA4 key events and treat conversion-driving pages as more important than clicks alone.
- ✦Start with decaying pages and cannibalization fixes before creating new content.
- ✦Log site changes as annotations and review their impact roughly 30 days later.
Key moments
- 15:46Why Search Console Data Is Directional
“data as a whole is supposed to be directional. Unless you're looking at revenue or leads”
- 20:11Finding Decaying Pages First
“I'd rather fix issues that already exist than create new problems”
- 26:02Cannibalization and Striking Distance
“Google just danks it because it doesn't know which one to serve”
- 31:24Connecting Search Console via MCP
“it's a one-click setup. You can actually we're in the cloud connector library”
- 39:16Annotations and Monthly Review Cycle
“I tend to look at things about 30 days after I do them”
- 42:13Content Groups and Priority Stars
“I will see these stars for pages and queries that are attached to those prioritized contents”
Quotes are from the episode transcript, lightly cleaned of auto-caption errors.
Questions answered in this episode
- Why should SEOs look at page-level data instead of only queries in Search Console?
- Queries are anonymized in Search Console, so page-level data is closer to 100% of the data needed. The two data tables pull differently, so page data gives a more complete picture.
- How should you decide which pages to fix first?
- Filter by priority content groups, then check decaying pages and find out why they are losing queries. Refreshing content, adding internal links, and fixing cannibalization are usually the easiest wins because the pages already rank close.
- How long should you wait before judging an SEO change?
- It depends on the change. Site migrations need daily watching, new content can show results within days once indexed, and Matthew generally reviews changes about 30 days after making them.
More episodes on Technical SEO

SEO Audit Checklist: Technical and On-Page Checks | Luke Hill
Luke Hill

Technical SEO: Crawling, Rendering and Authority | John Chung
John Chung

SEO Automation: Embedding Clusters and Link Checks | Samantha Torres
Samantha Torres

llms.txt: Guiding AI Models to Your Key Content | Jordan Pearce
Jordan Pearce

SEO Audit After a Google Update | Kristine Schachinger
Kristine Schachinger

Cloud Stacking for SEO: Advanced Tactics | Massimiliano Geraci
Massimiliano Geraci