How to Connect Google Search Console to ScreamingCAT

Stop crawling in the dark. This guide details the ScreamingCAT Search Console integration, showing you how to overlay performance data onto your crawl reports for truly actionable SEO insights.

Why Bother With the ScreamingCAT Search Console Integration?

Crawl data in a vacuum is just a list of URLs. It’s a map of your website’s structure, which is useful, but it’s a map without traffic lights, road signs, or any indication of which roads people actually use. The ScreamingCAT Search Console integration adds that critical context.

It overlays Google’s performance data—clicks, impressions, click-through rate (CTR), and average position—directly onto your technical crawl data. This transforms your audit from a sterile checklist of technical issues into a prioritized, data-driven action plan.

Instead of asking, “Which of these 500 redirect chains should I fix first?” you can ask, “Which redirect chain is costing me the most clicks?” Stop guessing which pages matter. Let Google’s data tell you.

Prerequisites: What You Need Before You Begin

Let’s not waste anyone’s time. Before you dive into the API settings, make sure you have the basics covered. This process is simple, but it assumes you’ve done the prep work.

First, you need a working installation of ScreamingCAT. If you’re just getting started and haven’t run your first crawl yet, our Quick Start guide will get you up and running in minutes.

Second, you need verified access to the Google Search Console property you intend to analyze. This means you must have “Owner” or “Full User” permissions. “Restricted” access won’t cut it, as it doesn’t grant the necessary API permissions.

Finally, you need a stable internet connection. The integration works by making API calls to Google. If your connection is flaky, the process will fail, and you’ll be left wondering why your data is incomplete.

The Step-by-Step ScreamingCAT Search Console Integration

Connecting your account is a one-time setup process that takes about two minutes. Once authenticated, ScreamingCAT securely stores the token for future crawls.

Follow these steps precisely:

• Navigate to API Access: From the top menu bar, go to Configuration > API Access > Google Search Console. This is the central hub for all GSC-related settings.
• Connect Your Account: Click the “Connect to New Account” button. This will trigger an OAuth flow, opening a new browser window where you’ll be prompted to sign in to Google.
• Grant Permissions: Choose the Google account that has the required permissions for your GSC property. Google will ask you to grant ScreamingCAT permission to view your Search Console data. We only request read-only access and only for the data needed for the integration.
• Select Your Account in ScreamingCAT: After successful authentication, return to the ScreamingCAT application. Your newly connected Google account should now appear in the “Account” dropdown menu. Select it.
• Choose the GSC Property: From the “Property” dropdown, select the specific GSC property you want to pull data from. It is critical that this property matches the site you are crawling (e.g., the URL Prefix Property `https://www.example.com/` for a crawl starting at that address).

Configuring GSC API Settings for Maximum Insight

Connecting your account is just the first step. The real power of the ScreamingCAT Search Console integration lies in how you configure the data pull. The default settings are conservative to protect your API quota, but they aren’t always what you need.

Under the “Settings” tab, you can customize the data you retrieve. The most important options are the date range and dimensions.

Date Range: The default is the last 28 days. You can extend this up to the full 16 months of data that GSC stores. For trend analysis or year-over-year comparisons, a longer date range is essential. Just be mindful of the API cost.

Dimensions: By default, ScreamingCAT fetches data by `Page`. You can also add `Query` as a dimension. This is immensely powerful, as it shows you the exact queries driving impressions and clicks to each URL. However, this increases the number of API calls exponentially, as it requests data for every URL-query combination.

Analyzing the Data: Key Reports and Use Cases

You’ve run your crawl with the integration enabled. Now what? The data you’ve collected populates a dedicated “Search Console” tab in the main window and is also available in the “URL Details” pane. This is where analysis begins.

One of the most valuable reports is identifying “Orphan Pages.” In the “Search Console” tab, use the filter dropdown and select “GSC Pages Not In Crawl.” These are URLs that Google has data for (meaning they get impressions) but that the crawler couldn’t find. They are likely missing internal links, on a different subdomain, or are legacy URLs that still have ranking signals.

This integration allows you to ruthlessly prioritize your technical SEO work. Sort your main crawl report by clicks or impressions from GSC. A 404 error on a page with zero impressions is a low priority. A 301 redirect chain on your top-10 most-clicked pages is an immediate, high-priority fix.

Overlaying performance data helps you find content opportunities. Are there pages with high impressions but a low CTR? That’s a clear signal to improve your title tags and meta descriptions. Do you see multiple URLs ranking for the same valuable queries? That’s a cannibalization issue that needs to be addressed with content consolidation or improved internal linking.

The true power comes from combining datasets. Cross-reference GSC data with crawl depth, word count, or PageSpeed Insights data. Are your highest-impression pages buried 5 clicks deep in your site architecture? You can track the impact of your changes over time by saving your GSC-enriched crawls and using our Crawl Comparison feature.

Advanced Automation with the Command-Line Interface

The graphical user interface is perfect for focused, ad-hoc audits. But for true efficiency and scale, automation is key. The ScreamingCAT Search Console integration is fully supported via our command-line interface (CLI).

This allows you to schedule regular, GSC-enriched crawls without ever opening the application. You can set up a weekly cron job to audit your site, pull fresh GSC data, and export a report of any new 404s that have impressions. This moves you from reactive problem-solving to proactive monitoring.

Here is a sample command to run a headless crawl that connects to your GSC account, pulls data for a specific property, and exports only the relevant Search Console tabs to a dated folder. This is the foundation of an automated SEO monitoring system.

screamingcat --crawl https://your-domain.com --headless --google-search-console-property 'sc-domain:your-domain.com' --google-search-console-account '[email protected]' --export-tabs 'Search Console:All,Search Console:GSC Pages Not In Crawl' --output-folder ~/ScreamingCAT/audits/$(date +%Y-%m-%d)

Troubleshooting Common Integration Issues

APIs can be fickle. If your integration isn’t working as expected, it’s likely one of a few common issues. Before you panic, check these potential culprits.

Error: “User does not have sufficient permission for this property.” This one is simple. The Google account you authenticated with does not have “Full” or “Owner” permissions in GSC for the property you’re trying to crawl. Verify your permission level within the Search Console UI and request an upgrade if needed.

Problem: No GSC data is returned for any URLs. First, double-check that the GSC property selected in ScreamingCAT (e.g., `https://www.example.com`) exactly matches the protocol and subdomain of the site you’re crawling. Second, ensure the date range you’ve selected actually contains data; a brand-new site might not have any performance metrics yet.

Error: “Quota exceeded for quota metric ‘Queries’ and limit ‘QueriesPerDayPerUser’.” You’ve hit Google’s daily API quota. The only solutions are to wait 24 hours for it to reset or to reduce the scope of your next crawl. Try a shorter date range, remove the `Query` dimension, or crawl a smaller subsection of your site.

Problem: The connection suddenly stops working. Google’s authentication tokens can expire or be revoked. If the connection fails, the first step is always to go back to `Configuration > API Access > Google Search Console`, disconnect your account, and reconnect it. This re-authenticates and resolves the issue 99% of the time.