Google Search Console Insights gives you a quick view of content performance and traffic changes. It is useful when you need to decide where to investigate next without starting with a large export.
Back to the Google Search Console guide
What the Insights report shows
Open Insights and select a date range. Depending on the data and features available for your property, cards can show clicks, impressions, leading content, rising or falling pages, queries, countries and additional Google traffic sources.
Trending items reflect changes in clicks compared with the previous period. Similar queries may be grouped on sites with enough data. Click an item to investigate it in the more detailed Performance report.
Some cards are unavailable for smaller sites or during feature rollouts. Branded-query classification can be imperfect, and experimental social-channel insights are not available to everyone. Do not build your entire reporting process around a card you may not have.
A ten-minute content review
- Choose a consistent period. Make each review comparable instead of changing the date range to find a more attractive result.
- Pick one rising page. Read it and ask whether the next useful answer is missing.
- Pick one declining page. Investigate the underlying queries before deciding it needs a rewrite.
- Check relevance. A traffic change on a core service guide may matter more than a larger change on an unrelated post.
- Write one action for each. Include the URL, evidence, proposed change and review date.
Example of a rising page
Imagine a WordPress article about missing images begins attracting more clicks. Before writing three similar posts, review which searches are increasing. If readers want to diagnose a specific error, add a clear diagnostic step and link to the appropriate existing guide.
If the article already answers those questions, the best action may be a better next step: link to a related troubleshooting resource or explain when professional help is appropriate. More content is not automatically the right response to rising traffic.
Example of a declining page
Suppose an annual event article loses clicks after the event ends. That is different from a permanent service page losing relevant searches after a redesign. Check the page, timing and query mix before making changes.
For the redesigned service page, compare its old and new purpose, title, internal links and accessibility. If it no longer loads correctly, investigate the technical problem first. Use URL Inspection when the evidence suggests a crawl or indexing issue.
Turn observations into an editorial queue
Keep a Google Sheets queue with URL, trend, likely reader need, evidence, recommended action and review date. Use explicit actions such as “add the missing troubleshooting step” or “update obsolete instructions.” Avoid vague tasks such as “optimize this page.”
Give each task a reason that another person could understand without opening five reports. For example: “The article discusses the error but never explains where to find the relevant WordPress setting.” That is a reviewable content gap.
Before creating a new post, search your existing site. Updating an established guide and linking it clearly may serve readers better than publishing another page that answers the same question.
Check the detailed report before deciding
Insights is your shortlist. The Performance report is where you compare queries, pages, devices and countries. Use both when a change deserves substantial development or editorial time.
Also check business outcomes separately. Search clicks do not prove that a page generated qualified enquiries. A smaller amount of relevant traffic may be more valuable than a large increase in unrelated searches.
Frequently asked questions
Is this the old standalone Search Console Insights?
Google documents the integrated Insights report as the replacement for the earlier standalone beta. Follow the report available within your Search Console property.
What if my site has very little data?
Use a longer comparable period when practical and avoid treating tiny changes as established trends. Continue improving useful pages and check their indexing instead of manufacturing conclusions from a handful of clicks.
Reference: Google’s Insights documentation.
