Check whether search growth is seasonal
A month of growth can reflect seasonality, new content, or a change in demand. Check enough history before choosing an explanation.
Choose a fair comparison
Check Store coverage for the current and year-earlier windows. Use complete periods and one search type. Google's available history may be too short for a reliable annual pattern on a new Site.
Run the growth Report
gscdump report growth --site example.com --period 90d --vs yoy --jsonThe growth Report defaults to a year-over-year comparison. --vs yoy makes it visible in the command. It combines newly observed search queries, queries per page, shared-word groups, and long-tail Sections. It needs enough stored data for its required Analyzers. Read Section coverage and meta.degraded before comparing. See Reports.
Check seasonality
gscdump analyze seasonality --site example.com --period 365d --json
gscdump analyze trends --site example.com --period 365d --jsonUse the Analyzer reference to check source support. A seasonal pattern needs repeated periods. Missing months and partial months should stay visible, not become zero values.
Find contributing pages
gscdump query --site example.com --type web \
--dimensions date,page --limit 100 --format csv --output page-trend.csvSet the same dates as the Report. Check which pages account for the change. A top-row export may miss long-tail changes; inspect the row limit and source metadata. The query guide covers exports.
Set a monitoring window
Record the comparison dates, Site, search type, and pages to revisit. If growth concentrates in brand queries, use Brand traffic. If one device moves differently, use Device gaps. Other questions: Investigate traffic.