A weekly Google Search Console review template provides a repeatable framework for surfacing ranking drops, traffic shifts, and indexing issues before they compound. This walkthrough covers what sections to include, how to populate each one from GSC reports, and how to turn the output into prioritized fixes.
Start with a date range section that anchors your review: define the current week versus the previous week, keeping the day-of-week aligned so Monday to Sunday this week compares to Monday to Sunday last week. Add a summary metrics block that pulls total clicks, impressions, average CTR, and average position from the Performance report. Include a query performance table with columns for the query, current-week clicks, prior-week clicks, delta, current position, and prior position. Add a pages performance table with the same structure, swapping queries for URL paths. Include an indexing health section where you note newly excluded pages, validation status of open issues, and any Coverage report warnings. Finally, reserve a section for Core Web Vitals status by URL group and any Mobile Usability errors that surfaced during the week. This skeleton scales whether you manage one site or a portfolio.
In the Performance report, set your date range to the past seven days, then click Queries. Sort by clicks descending and export the top fifty queries as a CSV. Open your template and paste the query names. Switch your GSC date range to the prior seven-day window and export the same query list again. Use a VLOOKUP or INDEX-MATCH formula in your spreadsheet to pull the prior-week clicks and position for each query. Calculate the click delta and position delta in adjacent columns. Sort by click delta descending to surface queries that lost the most traffic. Queries showing a five-plus position drop with significant click volume warrant immediate investigation: check if the page was updated, if competitors published fresher content, or if Google rolled out a ranking update that week. For Canadian sites, filter queries by location in GSC if you serve distinct regional audiences in Toronto, Montreal, or Vancouver and need to catch geo-specific swings.
Repeat the export-and-compare workflow for Pages instead of Queries. Export the top fifty pages by clicks for both weeks, match them in your template, and calculate deltas. Pages losing impressions but holding position often signal declining search demand or query-set shifts; pages losing both impressions and position suggest on-page issues, crawl problems, or freshness decay. Flag any page with a double-digit impression drop and cross-check it in the Coverage report to rule out indexing exclusions. Also note pages with improving impressions but falling CTR, which means the page is ranking but the title or meta description no longer matches searcher intent. Prioritize fixes for pages that already drove revenue or conversions; if you run a bilingual site serving Quebec, check whether French-language pages are behaving differently than English equivalents and adjust content or hreflang tags accordingly.
Navigate to the Coverage or Page Indexing report in GSC and note the count of valid, excluded, and error URLs. Compare the valid count to last week's template entry; a drop of more than a few dozen pages in a stable site signals a problem. Export the list of newly excluded pages and scan for patterns: if multiple product pages moved to noindex, check your CMS deploy log. If blog posts were excluded due to duplicate content, audit your canonical tags and URL parameters. Add any open validation requests to your template with their current status and date submitted, so you can track how long Google takes to re-crawl after a fix. For Canadian e-commerce sites, watch for soft-404 detection on seasonal inventory pages, which can appear excluded even though the products will return; consider using temporary 503 headers instead of removing pages during stockouts.
Open the Core Web Vitals report and note the count of URLs marked poor, needs improvement, and good for both mobile and desktop. Log any URL groups that moved from good to needs improvement this week, and export the affected URLs to investigate layout shifts or slow Largest Contentful Paint. If the report shows a spike in poor URLs after a deploy, roll back or hotfix immediately. Add a column in your template for the primary CWV metric causing the issue so you can track whether the same problem recurs across weeks. Check the Mobile Usability report for new errors like clickable elements too close or viewport not set; even a single new error on a high-traffic page can hurt rankings. Canadian sites targeting local search should prioritize mobile fixes because Google uses mobile-first indexing, and most local queries come from smartphones.
After populating all sections, scan your deltas and flags to build an action queue. Rank items by potential traffic impact: a page losing two hundred clicks per week due to a position drop outweighs fixing a mobile usability error on a page with five weekly impressions. Group related fixes so you can batch work: if three blog posts lost rankings because of stale publish dates, refresh all three in one editorial session. Record every fix you deploy in a separate log tab within the same spreadsheet, noting the date, the specific change, and which GSC issue it addressed. When you run next week's review, cross-reference your fix log to measure whether the intervention restored rankings or traffic. This closed-loop process turns the template from a passive dashboard into an active optimization engine that compounds gains week over week.
If you manage multiple domains, create a master template with one sheet per site or clone the template file for each property. Add a rollup dashboard that summarizes total clicks, critical issues, and pending fixes across all sites so you can allocate time efficiently. Use conditional formatting to highlight any site where total clicks dropped more than a threshold amount or where the count of indexing errors doubled. For agency workflows, embed a client-facing summary section at the top of each template that translates technical findings into business language: instead of position delta negative eight, write expected traffic loss of X percent unless we refresh the content. Export the summary as a PDF or share the live sheet with view-only access. Canadian agencies serving clients in regulated sectors like finance or healthcare should add a compliance check column to flag any pages that lost rankings after algorithm updates targeting E-E-A-T, then coordinate with the client to add author bios or third-party citations.
Compare the most recent complete seven-day window to the prior seven-day window, aligning days of the week. Avoid partial weeks because weekend versus weekday traffic patterns skew deltas. For seasonality context, you can add a year-over-year column, but the primary comparison should always be sequential weeks so you catch fresh issues fast.
Start with the top fifty queries and pages by clicks, which typically captures the bulk of your traffic. If your site has hundreds of thousands of indexed pages, raise the threshold to queries with at least ten clicks per week to keep the dataset manageable. Lower thresholds generate noise from one-off long-tail queries that fluctuate randomly.
Yes, especially if branded queries dominate your click volume. Create separate sections or filter rows so you can isolate non-branded query performance, which better reflects true SEO gains. Branded query swings often stem from offline marketing or seasonality rather than search algorithm changes, so mixing them obscures the signal you need to optimize content.
Google Search Console data typically lags two to three days. Run your weekly review on the same weekday each week, but set the date range to end three days prior to ensure the data is fully populated. For example, if you review every Monday, analyze the period ending the previous Friday so you have complete metrics.
Yes. Use the Google Search Console API with a script in Google Sheets, Python, or a third-party connector like Supermetrics. Automation eliminates copy-paste errors and lets you refresh the template on a schedule. Store your raw API pulls in a separate archive tab so you maintain a historical record even if Google purges older data from the interface.
Flag it as keyword cannibalization. Check which page historically ranked higher and either consolidate the weaker pages into the stronger one, add internal links from the weaker pages to the primary page, or differentiate their target keywords by adjusting titles and headings. Track the cannibalization flag in your template so you can verify whether the fix restored stable rankings in subsequent weeks.