A weekly Search Console review has five parts: compare the last 7 days with the previous 7 for clicks and impressions, check for pages that dropped, look for new queries with impressions, pick one page to improve, and record the change with its baseline. Then check earlier changes at 7, 14 and 28 days. It takes about thirty minutes and produces one deliberate fix a week.
The thirty-minute agenda
| Minutes | Check | Question |
|---|---|---|
| 5 | Clicks and impressions, last 7 days against the previous 7 | Up, down or flat? Anything sudden? |
| 5 | Pages sorted by change in clicks | Which pages fell, and did position or CTR cause it? |
| 5 | Queries with impressions and few clicks | Any new topic people are finding you for? |
| 5 | Indexing report | Any pages newly excluded or erroring? |
| 5 | Follow-ups on earlier changes | What do the 7, 14 and 28-day numbers say? |
| 5 | Decide | Which one page gets attention this week? |
Seven-day comparisons are noisy on small sites. Use them to spot things, and the 28-day view to judge them.

Choosing the one fix
In rough order of return for effort:
- High impressions, low CTR, position in the top ten. Rewrite the title and description. See the low-CTR guide.
- Position 8 to 20 for a valuable query. Improve the page: answer the query more directly, add what the top results cover, link to it from related pages.
- A page that used to get clicks and is declining. Refresh it: update facts, dates and examples.
- A query with impressions and no page that really answers it. Write that page.
- Indexing errors on pages that matter.
One fix a week is fifty a year. That is more than most small sites manage, and each one is measured.
Keeping a change log
Without a record, every traffic movement is a mystery. For each change, note:
- Date and URL
- What changed, with the old version
- Baseline: clicks, impressions, CTR and position for the prior 28 days
- Why you expected it to help
- Results at 7, 14 and 28 days
- Verdict: keep, revisit or inconclusive
"Inconclusive" is a legitimate verdict. Search results change for reasons that have nothing to do with you.
Spotting drops early
When clicks fall, ask in this order: did impressions fall (demand or ranking), or only CTR (snippet or results-page change)? Is it one page or the whole site? Did it start on the day of a release or a site change? Is it one country or device? Most drops on small sites trace to a specific page change, a lost ranking for one query, or seasonality. Site-wide drops deserve an indexing and technical check first.
For small SaaS and app sites
- Separate brand queries from non-brand. Brand clicks tell you about awareness, not SEO.
- Watch landing pages for each feature or use case separately.
- App landing pages often rank for "alternative to" and "for Mac" queries. Check which of those have impressions.
- Tie the review to releases: a new feature is a reason to refresh its page.
How Rank keeps the loop together
- Daily Briefing opens on the changes and regressions that need attention.
- Opportunities from your Search Console data, with a forecast of the clicks at stake.
- Review and approve each proposed fix before it is published or exported.
- Checkpoints at 7, 14 and 28 days against the stored baseline.
- Change Timeline with publishing, crawls, snapshots and alerts in one history.
- Content Decay Calendar for pages losing clicks.
- Client Mode for approvals and a report, if you do this for others.
- Rank Advisor answers questions about the selected site from your local data.
Free tools, no sign-up: the Search Console opportunity finder, the SERP snippet preview and the meta tag checker. More are in the free tools index. Yuzool's own week-by-week results with Rank are in the public case study.
What Rank is not
- Not a backlink index or keyword database. It does not replace Ahrefs or Semrush for link research or competitor keyword data.
- It needs Search Console data. A brand-new site with no impressions has little to analyse.
- It does not promise rankings. It records what you changed and what happened afterwards, and it is careful not to claim one caused the other.
- Mac only.
Price
Rank is a Mac app, $39 once with no subscription. You connect Google Search Console through Google's own authorisation, which you can revoke at any time. Tokens are kept in the Keychain and synced performance data is cached on your Mac. It is most useful once your site has started collecting impressions. See the demo or start here.
Common questions
Is weekly too often for a small site?
Weekly keeps the habit. Judge results on 28-day data, not week to week.
How much traffic do I need?
Enough impressions to compare pages. A few hundred a month is workable; less than that, focus on publishing.
Can I do this without a tool?
Yes, with Search Console and a spreadsheet for the change log.
Does Rank need my Google password?
No. You authorise through Google, and can revoke access from your Google account.
Where is my Search Console data stored?
Synced performance data is cached on your Mac.
Run this week's review on your Mac: Buy Rank, $39 once.