SEM

If you are still exporting CSVs from Google Search Console every Monday morning, opening them in Excel, manually comparing this week’s impressions against last week’s, copying numbers into a client report template, and sending it before your 9am call — you are spending three to five hours a week on a process that a 60-line Python script can run in 45 seconds, automatically, on a schedule, and deliver to a Looker Studio dashboard, a Slack channel, or a formatted PDF without any human involvement whatsoever. This is not a post about learning Python from scratch. It is a post about the specific, practical intersection between Python and the Google Search Console API that transforms SEO reporting from a manual, error-prone, agency-hours-consuming obligation into an automated intelligence layer that runs invisibly in the background and surfaces the right information at the right time. The methodology here is used by SEO professionals at UK agencies and in-house marketing teams at British brands that cannot afford to have skilled analysts spending their Thursday afternoons copy-pasting data. It is accessible to anyone who can follow a set of instructions, install a library, and run a script — no prior Python experience required to get the foundational setup working. Why Manual Search Console Reporting Is Costing UK Businesses More Than They Realise The cost of manual SEO reporting is not just the time it takes to produce. It is the analytical quality that gets sacrificed when the production process is so burdensome that the analyst is focused on completing the report rather than interpreting it. When a report takes three hours to produce, the last thing anyone wants to do is spend another hour interrogating the data. The numbers get inserted, the template gets filled, the email gets sent. Insights that would have been visible to a fresh analyst looking at the data with genuine curiosity get buried under the fatigue of the production process. Automated reporting inverts this entirely. When data extraction and formatting takes 45 seconds instead of three hours, the analyst’s entire cognitive budget is available for interpretation — for spotting the anomaly in impressions that started six weeks ago and correlates with a specific Google algorithm update, for identifying the keyword cluster that has quietly doubled its average position over the past month without anyone noticing, for catching the client’s most valuable page dropping from position three to position eleven before the client notices it themselves. Beyond analytical quality, there is a competitive positioning argument. UK agencies that deliver automated, real-time SEO dashboards with alert-based anomaly detection are providing a fundamentally different service from agencies delivering manually assembled monthly PDF reports. The former demonstrates operational sophistication that justifies premium retainer pricing. The latter is increasingly commoditised. The investment in building the automated reporting infrastructure — a day or two of setup, largely following the steps in this guide — pays back within the first month of operation for any agency or in-house team reporting on more than three client or site domains. Understanding the Google Search Console API The Google Search Console API is Google’s official programmatic interface for accessing the same performance data available in the Search Console UI — queries, pages, countries, devices, impressions, clicks, average position, and CTR — but without the limitations of the UI and with full programmable control over how the data is queried, filtered, and exported. The key advantages of the API over the manual UI export: Date range flexibility — The Search Console UI limits data exports to 1,000 rows per export and has a fixed 16-month data retention window. The API allows you to pull data across any date range within that window in a single programmatic request, and to store the results in your own database for indefinite retention. Dimension combinations — The UI allows you to view data by one dimension at a time: queries, pages, countries, devices, or search type. The API allows you to combine up to five dimensions in a single query — for example, pulling query + page + device + country + date in one request, giving you the granular breakdown needed for sophisticated segmentation analysis. Automation and scheduling — API requests can be triggered on a schedule via Python scripts running locally, via cloud functions (Google Cloud Functions, AWS Lambda), or via scheduled notebooks in Google Colab. The data flows automatically on whatever cadence you define. Volume — Each API request returns up to 25,000 rows. Multiple requests can be paginated to pull complete datasets for large sites without the row limits that cap UI exports. The API uses OAuth 2.0 for authentication, meaning your Python script authenticates as your Google account and accesses only the Search Console properties you own or have been given access to. It is secure, auditable, and fully aligned with Google’s terms of service. Step 1: Setting Up Your Google Cloud Project and API Credentials Before writing a single line of Python, you need to configure the Google Cloud project that will authenticate your API requests. Create a Google Cloud Project: Navigate to console.cloud.google.com. If you do not have a Google Cloud account, create one — it is free and does not require payment details for the services used here. Click “New Project,” give it a descriptive name (“SEO Reporting Automation” works), and create it. Enable the Google Search Console API: In your new project, navigate to “APIs & Services” → “Library.” Search for “Google Search Console API” and enable it. This takes about 30 seconds. Create OAuth 2.0 Credentials: Navigate to “APIs & Services” → “Credentials.” Click “Create Credentials” → “OAuth client ID.” If prompted, configure the OAuth consent screen first: select “External” as the user type, fill in the application name and your email address, and add your Google account email as a test user. Back in Credentials, select “Desktop application” as the application type. Download the resulting JSON credentials file and save it as client_secrets.json in the directory where your Python scripts will live. This