Investigate an organic traffic trend
Start with clicks and impressions, then isolate the query, page, country, device, search type, and date pattern responsible for the visible movement.
- Sitewide trend
- Affected segment
- Page and query evidence
Google Search Console SEO Dashboard
Connect your site's Search Console property to review Google clicks, impressions, CTR and average position. Investigate queries, pages and audience segments beside crawl evidence, with available keyword research and a path into Rank Tracker.
Connect Google Search Console
Bring your site's Google performance into its Screpy project. The project owner's connected Google account supplies access, so teammates can review the same property without connecting separate accounts.
- Authorize Google with read-only Search Console access.
- Use an accessible domain or URL-prefix property matching the project website.
- The project owner manages the connection and property; expired authorization requires reconnection.
OAuth
Screpy
Screpyexample.comConnected
Read Search Performance Metrics
See whether a change involves visibility, clicks or click-through rate before deciding what to investigate. Select the metric lines you want to see together on the chart.
- Clicks and impressions show recorded Google search activity for the selected scope.
- CTR is total clicks divided by total impressions, rather than an average of row percentages.
- Average position is weighted by impressions and reflects recorded results, not a live keyword check.
- Toggle clicks, impressions, CTR and position independently; a click is not an analytics session or conversion.
- Impressions
- 2,860
- Clicks
- 86
Explore Organic Search Trends
Start with the three-month view, then choose a reporting window that fits the question. Read the timeline alongside date rows to locate the movement before examining its queries or pages.
- Presets include 24 hours, 7 days, 28 days, 3, 6, 12 and 16 months, subject to available property history.
- The 24-hour preset requests yesterday and today, interpreted as Pacific calendar dates, with hourly preliminary data.
- Other windows use finalized Google data and daily, weekly or monthly chart grouping; weekly groups contain seven returned daily rows.
- Recent values can change and requests may reuse data for 15 minutes; the chart is not a real-time alert feed.
Requests
1,860Filter Search Queries and Pages
Separate branded searches, a content folder or a device audience without losing the reporting context. For example, combine a page containing /guides/ with Mobile to examine that folder's mobile performance.
- Combine up to four query, page, country or device filters; every rule must match.
- Choose contains, exact match, their exclusions, or including/excluding regular expressions.
- Use country filters for geographic audiences and Desktop, Mobile or Tablet for device segments.
- Contains matches ignore case; query/page exact matches are case-sensitive and regex follows Google's RE2 syntax.
Keyword linenURL /shop/
/shop/linen-shirtSelected
Analyze Search Reporting Dimensions
Switch between the question's search surface and table breakdown. Google supplies different data for Web, Image, Video, News, Discover and Google News; an empty surface is not evidence of lost traffic everywhere.
- Browse Queries, Pages, Countries, Devices, Search appearance and Dates as separate table views.
- Keep search types separate; Discover and Google News do not provide an equivalent Google search ranking position.
- Search appearance groups the available result categories; it is not an Add Filter option in the dashboard.
- Main tables load 50 rows per page with Previous/Next navigation; CSV and Excel export are not available here.
USCountry24Pages
Clicks186
Connect Search Queries to Pages
Which searches reach a page, and which pages appear for a query? Open either relationship to investigate content fit or overlapping URLs, while keeping the detail window's independent scope in mind.
- Open query details for a page or page details for an exact query, with clicks, impressions, CTR and average position.
- These dialogs use Web data from one month ago through today; they do not inherit the main dashboard's period, search type or country/device filters.
- Each dialog shows the first 50 returned rows, without additional server pages or CSV/Excel export; multiple URLs alone do not prove cannibalization.
linen shirt/shop/linen186Clicks/guides/linen74ClicksAdd Keyword Research Context
The main Queries table places available keyword research beside your actual Google performance. Use those signals to assess demand and intent without mistaking market estimates for the property's recorded results.
- Review available search volume, CPC in USD, organic difficulty, advertising competition and intent; unavailable values remain missing.
- Research follows the project's country and language, rather than a country selected in Search Console filters.
- The estimated result-page column groups average positions in tens; it is not a landing-page URL or an exact Google result layout.
- Visibility is derived from average position: position 1 maps to 100%, 10 to 20% and 20 to 5%. It is not Google's impression or traffic share.
Search volume
2,400Keyword difficulty28 / 100
Track Important Search Queries
Use Search Console to choose an existing query worth monitoring, then open its prefilled Rank Tracker form. Scheduled checks answer a different question from Google's impression-based average position.
- Eligible untracked query rows offer Add to Rank Tracker in the main table and page-query details.
- Review the project, country, language, location and device settings before saving; a Search Console country filter is not copied as the tracking market.
- Tracking starts under Rank Tracker's plan allowance and schedule; adding a query does not recreate historical Google rankings.
linen shirtUS- linen shirt2,400
- linen clothing1,600
- summer linen880
Compare Search Console Data with SEO MCP
Ask a connected AI assistant to query Google performance or compare periods with consistent scope. This comparison is available through SEO MCP; the dashboard itself does not show a side-by-side period report.
- Check the connected property and data availability before requesting an overview or detailed rows.
- Query up to three dimensions together, using supported filters, presets or custom dates, with up to 100 rows per response and cursor pagination.
- Compare totals using the same property, search type and filters; optional dimension changes return up to 100 values from up to 1,000 top rows per period.
- Read retrieval dates, preliminary-data notices and row limits with the result; missing rows and a comparison do not establish a cause.
Before62→After87
Talk about Search Console. With SEO MCP.
Explore connected Google Search Console data through SEO MCP. Compare periods, filter queries or pages and ask your AI assistant to explain changes in clicks, impressions and CTR.
- Screpy: Hello! Let’s look at Search Console for example.com. What would you like to know?
- You: Compare the last 28 days with the previous period. Where did clicks fall?
- Screpy: /collections/linen lost clicks while impressions increased. Review its queries and CTR before assuming a ranking problem; this comparison does not establish the cause. Search Console comparison: Clicks: −12%. Impressions: +8%.
- You: Turn that into a short action plan.
- Screpy: I’ll keep the evidence and recommendations separate. Review the findings, choose one change and check the results afterward. Your next steps: Review: Check the source and date of each finding.. Decide: Choose the first change to make.. Verify: Compare the results after the change..
- You: Can you explain the evidence in plain language?
- Screpy: Yes. Ask about a supported result and I can explain what it shows, where it comes from and what is still uncertain. Missing data stays unavailable; recommendations are not automatic fixes.
Turn a Search Console trend into a focused SEO investigation.
Start with the correct property and reporting scope, narrow the movement to a useful segment, inspect its pages and queries, then use the right second source before assigning work.
-
Connect the matching Search Console property
The project owner authorizes a Google account with read-only Search Console access. Use the accessible property matching the project website, then confirm that it contains the expected data; permitted teammates share that connection.
-
Define the reporting window and search surface
Choose a supported date range and separate Web, Image, Video, News, Discover, or Google News data. Use the chart interval that makes the trend readable without hiding meaningful daily movement.
-
Filter the segment behind the question
Narrow the report by query, page, country, or device. Use exact, contains, exclusion, or regular-expression filters where supported so sitewide averages do not obscure the affected segment.
-
Move from the trend to query and page evidence
Open a page's queries or a query's pages to investigate their relationship. These detail windows independently use last-month-to-today Web data and the first 50 returned rows, not the main report's selected filters. Keyword enrichment appears in the main Queries table.
-
Validate the next action with another source
Use Rank Tracker for selected-keyword SERP monitoring, Website Audit for crawl and on-page evidence, or Quick Wins for defined opportunity reports. Keep the original Search Console range as the baseline.
Use Search Console data to answer a specific search-performance question.
Clicks, impressions, CTR, and average position become more useful when the report is narrowed to the page, query, market, device, and Google surface behind the decision.
Review high-impression, low-CTR demand
Find queries and pages that already appear in Google but attract relatively few clicks, then inspect result intent and snippet fit before rewriting titles or descriptions.
- Impression demand
- Query relevance
- CTR investigation
Connect content with the searches behind it
Open a landing page's query details to check its search intent and content fit. This window uses last-month-to-today Web data, independently of the main report; review keyword research context in the main Queries table.
- Page-to-query drilldown
- Intent and coverage
- Available keyword context
Separate markets, devices, and search surfaces
Compare the evidence inside focused country, device, and search-type segments instead of treating one blended average as the experience of every audience.
- Country filters
- Device filters
- Search type selection
Read Google Search Console metrics with their limits intact.
Screpy preserves the source context instead of presenting aggregated Search Console data as live rankings, complete query demand, or proof that one website change caused a result.
Average position is not a live rank
Google reports an average based on recorded impressions and the topmost result from the property or page. Use it as a trend signal rather than a guaranteed current SERP position.
Recent data can be preliminary
The newest Search Console rows may still change, and reporting is not a real-time analytics feed. Avoid attributing a same-day movement to one release without enough complete data.
Query reporting has privacy and row limits
Google can omit anonymized or low-volume queries and apply reporting limits. A missing query does not prove that the search never produced visibility.
Aggregation changes how totals behave
Property-level charts and page-grouped tables can count impressions, clicks, and position differently, while data is generally assigned to canonical URLs. Compare like with like.
Choose the workflow that matches the question.
Use Search Console for observed Google performance, Rank Tracker for scheduled checks of selected keywords, and Quick Wins for predefined opportunities built from connected evidence.
Inspect Google clicks, impressions, CTR, average position, dimensions, filters, and query-to-page relationships for the connected property.
Monitor selected keywords on a schedule with defined country, language, location, and device settings, independent of Search Console impressions.
Review focused search, content, crawl, and performance opportunities from the data sources available for one Screpy project.
Bring Search Console into the team making the decision.
Query and page evidence becomes more useful when it is connected to the planning, publishing, and release workflow that can act on it.
Use search evidence to prioritize existing pages, prepare campaigns, and explain progress to stakeholders.
Connect landing-page and documentation visibility with the releases that change those routes.
Screpy documentation
Learn how to use Search Console data
Follow the Screpy guide to connect Search Console, review search performance, and interpret queries, pages, and visibility changes.
Related SEO guides
Learn the concepts behind this workflow and apply them with practical SEO guidance.
SEO
Google Search Console MCP: Setup and SEO Analysis
Connect Google Search Console through MCP, run verifiable SEO analysis, and fix date, filter, pagination, and total mismatches using a real example.
Read article SEO
How to Read Average Position in Google Search Console
Average position in Google Search Console: interpret rankings by query and page, account for SERP features, and spot misleading averages vs clicks and CTR.
Read article SEO
How Do I Find Image-Based Search Traffic in Google Search Console?
Find image-based search traffic in Google Search Console with the Web: multimodal filter. Learn what it shows, why it may be empty, and what to check next.
Read article SEO
How to Diagnose CTR Drops in Google Search Console
CTR drops in Google Search Console: compare periods, isolate affected queries/pages, check position, SERP features, snippets, and seasonality then fix titles.
Read articleGoogle Search Console FAQ
Learn how Screpy uses connected Google Search Console data to support search analysis and SEO decisions.
Which date ranges are available?
Choose 24 hours, 7 days, 28 days, or 3, 6, 12 or 16 months, with three months as the default. The 24-hour preset requests yesterday and today as Pacific calendar dates and includes preliminary hourly data. Other windows use finalized data. The dashboard has no custom-date or side-by-side comparison view; SEO MCP supports custom periods and comparisons.
Why connect Search Console to an SEO tool?
Search Console explains how a website performs in Google Search. Viewing that data beside crawls, audits, speed monitoring, and rankings makes it easier to connect search changes with specific pages and website work.
Can Search Console data replace rank tracking?
No. Search Console reports aggregated performance from real Google Search activity, while rank tracking follows selected keywords on a defined schedule, location, and device. The two sources answer different questions and work well together.
Is average position the same as a live Google ranking?
No. Search Console average position is an aggregated metric based on the topmost result recorded across impressions. Use it as a trend signal, and use Rank Tracker when you need scheduled checks for selected keywords, locations, and devices.
Which Google search types can I analyze?
Screpy supports Web, Image, Video, News, Discover, and Google News search types. A type only returns rows when Google Search Console has matching data for the connected property and selected date range.
Is Search Console data real-time or complete?
No. Google can report recent data as preliminary, withhold some queries for privacy, and apply reporting limits or aggregation rules. Screpy presents the data available for the authorized property rather than estimating missing Search Console rows.
Can I filter Search Console performance in Screpy?
Yes. Add up to four query, page, country or device rules, combined with AND. Supported operators include contains, exact match, exclusions and regular expressions. Search appearance is a table grouping, not a dashboard filter option.
What Google Search Console data can I review in Screpy?
You can review clicks, impressions, click-through rate, average position, queries, pages, countries, devices, search appearance, and date rows. Available history and dimensions depend on the performance data Google provides for the connected property and selected search type.