SEARCH CONSOLE / WEEKLY SEO LOOP
Turn Search Console data into the next SEO action.
The most useful SEO work often starts with pages Google already understands. Use Search Console to find the pages leaking clicks, the topics that overlap and the content that is quietly decaying.
1. Find page-one pages with weak click-through
Filter pages with a position in the top ten, meaningful impressions and a low CTR. Rewrite the title and introduction around the query’s actual intent before creating another page. Start with the highest-impression pages so the work has a measurable ceiling.
2. Find wasted impressions
Group pages with substantial impressions but no clicks by section. Inspect whether the page answers the query, whether the title is specific enough and whether another page is a better home for the intent. Improve, consolidate or redirect deliberately; do not leave a large set of dead pages competing with useful ones.
3. Check overlap before publishing
Compare queries and pages that rank for the same intent. If two pages promise the same answer, choose a primary page and link the supporting page to it. A clear semantic silo is easier for people and crawlers to navigate than a pile of loosely related posts.
For Shift Helper, that means connecting free tools, practical guides, industry workflows and the team-size directory.
4. Queue content refreshes by decay
Compare a recent period with the previous period. Prioritize pages whose impressions, clicks or positions are falling and that previously brought relevant visitors. Refresh facts, examples, internal links and the call to action; preserve what already matches search intent.
5. Detect cannibalisation before consolidating
Group your export by query and look for multiple URLs receiving impressions for the same search. That is a review signal, not an automatic penalty: the pages may serve different intents, or one may need to become the primary page. Choose the clearest home, link the supporting page to it, and only redirect or merge when the content genuinely overlaps.
6. Run a full site audit
Run npm run seo:audit locally. It checks route metadata, canonical tags, H1 counts, internal-link targets, sitemap coverage and AI-reference coverage, then writes tmp/seo-site-audit.json. Fix structural issues before spending time on new content.
7. Make the workflow repeatable
Save the filters and review them weekly. The local scripts/seo-workflows.mjs helper reads a Search Console CSV export and writes a prioritized JSON queue for low-CTR, zero-click, refresh and cannibalisation candidates.
Use the free scheduling tools and resource hub as the destination for useful traffic, then measure whether visitors move into the product workflow.
A practical weekly checklist
- Run the technical audit.
- Review top-ten pages with low CTR.
- Review high-impression pages with zero clicks.
- Check overlapping queries before adding a URL.
- Refresh the strongest decaying pages and record the change.