Add Google Search Console plugin#63
Conversation
🧩 Plugin PR Summary📦 Modified Plugins
📋 Results
🔍 Validation Details✅
|
|
@claude review |
| Country: row.keys?.[0], | ||
| Clicks: row.clicks, | ||
| Impressions: row.impressions, | ||
| CTR: Number((row.ctr * 100).toFixed(2)), |
There was a problem hiding this comment.
Could you clarify the intent here? You're rounding/stringifying and then converting back to a number which might lose some precision.
| Date: new Date(row.keys?.[0]), | ||
| Clicks: row.clicks, | ||
| Impressions: row.impressions, | ||
| CTR: Number((row.ctr * 100).toFixed(2)), |
| Page: row.keys?.[0], | ||
| Clicks: row.clicks, | ||
| Impressions: row.impressions, | ||
| CTR: Number((row.ctr * 100).toFixed(2)), |
| { | ||
| "name": "pageUrLs", | ||
| "displayName": "Page URLs", | ||
| "description": "Returns a list off URLs with impressions in the last year", |
There was a problem hiding this comment.
This doesn't look quite right - the timeframe is 'now -> whatever end date selected in SquaredUp'
| "dimensions": [ | ||
| "page" | ||
| ], | ||
| "rowLimit": 25 |
There was a problem hiding this comment.
Do this or other streams need paging configured?
| "getArgs": [], | ||
| "headers": [], | ||
| "postBody": { | ||
| "startDate": "{{new Date(new Date(timeframe.start).getTime() - (new Date(timeframe.end).getTime() - new Date(timeframe.start).getTime()) - 86400000).toISOString().split('T')[0]}}", |
There was a problem hiding this comment.
Can't quite get my head around what happens if selected yearly ranges or something here - do we need to restrict the available timeframes?
| @@ -0,0 +1,59 @@ | |||
| { | |||
| "name": "previousPeriodQueriesByPage", | |||
There was a problem hiding this comment.
Given we have data/time selection in SquaredUp - do we need these 'previous period' streams, or can the user effectively create them by setting the date appropriately on two tiles?
| "rowLimit": 25000, | ||
| "dataState": "final" | ||
| }, | ||
| "postRequestScript": "postRequest/script2.js", |
There was a problem hiding this comment.
Worth renaming this script name (and script1) to be more identifiable
What does this change do?
Adds a new Google Search Console plugin that enables users to connect a GSC property via OAuth 2.0 and visualize search performance data directly within SquaredUp.
The plugin includes the following data streams. along with default dashboards for both site-level and page-level SEO analysis:
Why is it useful?
Google Search Console contains valuable SEO data and is one of the most widely used tools in the industry. It is also currently a gap in the SquaredUp plugin catalog.
This plugin allows users to:
The included dashboards provide an out-of-the-box SEO reporting experience with minimal configuration required.
Testing performed
Validation
Manual testing
Tested against a live Google Search Console property. A Google Pages test site was created and populated with content, with impressions and clicks generated over several weeks to produce representative Search Console data:
https://danielchodgson.github.io/gsc-lcp-test-site/index.html
Verified:
Screenshots
Known limitations / follow-ups