A Search Console action plan for this week

Choose one comparison before you open the tables. For a weekly ops habit, last 7 days versus the 7 days before is enough. For a noisier site, use 28 days versus the previous 28. Do not mix a custom range that includes a launch with a “last 28 days” screenshot from Slack.

Write the dates at the top of the list. If someone asks “what to do this week in GSC”, the answer starts with the window, not with a feeling.

In Performance, sort Queries and Pages by click difference. Keep the ten rows that explain most of the change. Ignore the long tail until those ten are classified. Countries and devices are a sanity check, not a second dashboard.

You are looking for four kinds of mover:

• A page or query that lost clicks and still deserves the job.
• A URL with an indexing, redirect, or canonical problem.
• A query that is rising, or ranking well with a weak CTR.
• A change that looks large and is only seasonal or branded noise.

Give each keeper one verb: refresh, fix, double down, or watch. Refresh means the URL is still the right page and the snippet or content is stale. Fix means something is broken — 404, redirect chain, noindex, wrong canonical. Double down means you are already winning and a small title or internal-link pass could take more clicks. Watch means you will not touch it this week.

Cap the active list. Three to five actions is a plan. Fifteen is a backlog. Add an owner and a done-when: “title and intro rewritten”, “redirect restored”, “internal links from the hub page”. If you cannot say done-when, it is not an action yet.

Do not rebuild the information architecture because one query slipped. Do not export every row to a sheet and colour-code it. Do not chase average position as a KPI. Do not start a new tool because the table felt large.

If the drop is still unexplained, use the guide on why Search Console traffic dropped before you add more tasks. If the team wants a chat-style ask instead of filters, use conversational SEO with Search Console.

Next week, look only at the actions you took and the same ten movers. Keep what worked. Drop what was noise. The habit is the product: Search Console in, a short list out.

AskGSC is built for that loop. Connect read-only Search Console, pick a property, and ask what to do this week. You get a ranked plan with evidence from that property — not another chart dump. Free is 1 site and 1 ask per UTC day.

How many Search Console actions should a week include?

Three to five with a clear done-when. More than that usually means the list is still a backlog.

Should I export Search Console to a spreadsheet every week?

Only if you already have a sheet that people use. Exporting is not a plan. Classifying ten movers is.

What is a good “what to do this week” question for GSC?

Name the date window, ask which queries or pages moved, and ask for a short list: refresh, fix, double down, or watch.