Google Search Console icon

Google Search Console

Connect to Google Search Console API

Actions4

Site → Compare Page Insights

AI-generated

Overview

The node connects to the Google Search Console API to compare search analytics data between two date ranges for a specified site. It allows users to analyze and compare metrics such as clicks, impressions, CTR, and position across different dimensions like page, query, and date. This is useful for SEO professionals and webmasters to track performance changes over time, identify trends, and optimize their website content accordingly.

Use Case Examples

  1. Compare search performance of a website between the last 28 days and the previous period to identify growth or decline.
  2. Analyze the impact of a marketing campaign by comparing search analytics data from the campaign period to the same period last year.
  3. Filter and compare page insights for specific queries or pages to understand which content is performing better.

Properties

Name Meaning
Filters Add one or more filters to refine the search analytics data, similar to the Search Console UI. Each filter group is ANDed together, and within groups, filters can be combined with OR or AND logic.
Site URL Mode Choose how to specify the site URL: either pick from verified sites or enter manually.
Site Name or ID The site URL or ID to query, selected from verified sites or specified manually.
Date Range A The date range for the first period to compare, with presets or custom start and end dates.
Compare Mode The mode to determine the second date range for comparison: previous period, previous year, or custom.
Date Range B The date range for the second period to compare, used only if Compare Mode is custom.
Row Limit (Per Range) The maximum number of rows to retrieve per date range, between 1 and 25000.
Search Type The type of search to query, such as Web, Image, Video, or News.
Dimensions The dimensions to include in the query, such as Date, Page, or Query.

Output

JSON

  • keys - Array of dimension values for the data row, e.g., page URL, query, or date.
  • clicks_a - Number of clicks in the first date range.
  • clicks_b - Number of clicks in the second date range.
  • clicks_diff - Difference in clicks between the two date ranges.
  • impr_a - Number of impressions in the first date range.
  • impr_b - Number of impressions in the second date range.
  • impr_diff - Difference in impressions between the two date ranges.
  • ctr_a - Click-through rate in the first date range.
  • ctr_b - Click-through rate in the second date range.
  • ctr_diff - Difference in click-through rate between the two date ranges.
  • pos_a - Average position in search results in the first date range.
  • pos_b - Average position in search results in the second date range.
  • pos_diff - Difference in average position between the two date ranges.
  • range_a
    • startDate - Start date of the first date range.
    • endDate - End date of the first date range.
  • range_b
    • startDate - Start date of the second date range.
    • endDate - End date of the second date range.
  • compare_mode - The comparison mode used (previous period, previous year, or custom).

Dependencies

  • Google Search Console API with OAuth2 authentication

Troubleshooting

  • Ensure the site URL is verified in Google Search Console and correctly formatted (must start with http(s):// or sc-domain:).
  • At least one dimension must be selected for comparison; otherwise, the node throws an error.
  • Row limit must be between 1 and 25000; exceeding this may cause API errors or incomplete data.
  • OAuth2 credentials must have appropriate permissions to access the Search Console API.
  • Common error: 'No site selected' indicates the site URL parameter is missing or invalid.
  • Common error: 'Inspection URL must start with http(s)://' indicates the URL format is incorrect.

Links

Discussion