From ba4949ba2dc08e95c6c33a8f0e262ec1266292a0 Mon Sep 17 00:00:00 2001 From: Dan H Date: Tue, 21 Jul 2026 15:39:34 +0100 Subject: [PATCH 1/2] Clarify Search Console property types (URL-prefix and Domain) Update the property field label/help and docs to explain that both URL-prefix (https://example.com/) and Domain (sc-domain:example.com) properties are accepted, and add a troubleshooting note for the 403 "insufficient permission" error caused by using the wrong property type. Bump version to 1.0.1. Co-Authored-By: Claude Opus 4.8 --- plugins/GoogleSearchConsole/v1/docs/README.md | 18 ++++++++++++++---- plugins/GoogleSearchConsole/v1/metadata.json | 2 +- plugins/GoogleSearchConsole/v1/ui.json | 6 +++--- 3 files changed, 18 insertions(+), 8 deletions(-) diff --git a/plugins/GoogleSearchConsole/v1/docs/README.md b/plugins/GoogleSearchConsole/v1/docs/README.md index d8ff804c..091cb303 100644 --- a/plugins/GoogleSearchConsole/v1/docs/README.md +++ b/plugins/GoogleSearchConsole/v1/docs/README.md @@ -3,7 +3,7 @@ ## Prerequisites - A Google account with access to Google Search Console -- A verified URL-prefix property in Google Search Console +- A verified Search Console property (URL-prefix or Domain) - A Google Cloud Project ## Enabling the Google Search Console API @@ -61,13 +61,22 @@ 8. Copy the **Client ID** and **Client Secret** that are displayed, save these somewhere secure as you won't be able to view the client secret again +## Which property value to use + +Search Console has two property types, entered differently: + +- **URL-prefix** — shown as a full `https://…` URL. Use the exact URL **including the trailing slash**: `https://example.com/`. Protocol and subdomain must match exactly. +- **Domain** — shown with a 🌐 globe icon and a bare domain (DNS-verified). Use the `sc-domain:` form with **no protocol or slash**: `sc-domain:example.com`. + +Not sure which you have? Check the property selector in Search Console, or call the API's `sites.list` to see the exact string for your account. + ## Configuring the plugin Populate the following fields when configuring the plugin: | Field | Description | |---------|---------| -| Search Console property URL | The exact URL-prefix property from Google Search Console (for example, `https://example.com/`) | +| Search Console property | Your property as it appears in Search Console. URL-prefix: full URL with trailing slash (e.g. `https://example.com/`). Domain: the `sc-domain:` form, no protocol or slash (e.g. `sc-domain:example.com`) | | Google OAuth client ID | The Client ID created in Google Cloud | | Google OAuth client secret | The Client Secret created in Google Cloud | | Sign in | Click to authenticate using a Google account that has access to the Search Console property | @@ -76,7 +85,7 @@ Populate the following fields when configuring the plugin: | Setting | Example | |---------|---------| -| Search Console property URL | `https://example.com/` | +| Search Console property | `https://example.com/` (URL-prefix) or `sc-domain:example.com` (Domain) | | Google OAuth client ID | `1234567890-example.apps.googleusercontent.com` | | Google OAuth client secret | `GOCSPX-xxxxxxxxxxxxxxxxxxxx` | @@ -100,4 +109,5 @@ Verify that: - The property exists in Google Search Console - The signed-in Google account has access to the property -- The property URL exactly matches the URL entered in the plugin configuration \ No newline at end of file +- The property value exactly matches the identifier in Search Console +- A **403 "insufficient permission"** despite being an owner usually means the property *type* is wrong — e.g. entering `https://example.com/` for a **Domain** property. Use `sc-domain:example.com` instead (and vice versa) \ No newline at end of file diff --git a/plugins/GoogleSearchConsole/v1/metadata.json b/plugins/GoogleSearchConsole/v1/metadata.json index 0df51821..8db39934 100644 --- a/plugins/GoogleSearchConsole/v1/metadata.json +++ b/plugins/GoogleSearchConsole/v1/metadata.json @@ -1,7 +1,7 @@ { "name": "google-search-console", "displayName": "Google Search Console", - "version": "1.0.0", + "version": "1.0.1", "author": { "name": "@Daniel-Hodgson-SquaredUp", "type": "community" diff --git a/plugins/GoogleSearchConsole/v1/ui.json b/plugins/GoogleSearchConsole/v1/ui.json index e178056d..d96b66be 100644 --- a/plugins/GoogleSearchConsole/v1/ui.json +++ b/plugins/GoogleSearchConsole/v1/ui.json @@ -2,9 +2,9 @@ { "name": "siteUrl", "type": "text", - "label": "Search Console property URL", - "help": "Enter the exact URL-prefix property from Google Search Console. Example: https://example.com/", - "placeholder": "https://example.com/", + "label": "Search Console property", + "help": "Enter your property exactly as it appears in Search Console. URL-prefix: the full URL including the trailing slash (e.g. https://example.com/). Domain: the sc-domain: form, no protocol or slash (e.g. sc-domain:example.com).", + "placeholder": "https://example.com/ or sc-domain:example.com", "validation": { "required": true } From 2ccfca8e4bba9ee41d947b1a0653e0f94d97049d Mon Sep 17 00:00:00 2001 From: Dan H Date: Wed, 22 Jul 2026 14:35:38 +0100 Subject: [PATCH 2/2] Add trailing newline to GSC README (MD047) Co-Authored-By: Claude Opus 4.8 --- plugins/GoogleSearchConsole/v1/docs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/GoogleSearchConsole/v1/docs/README.md b/plugins/GoogleSearchConsole/v1/docs/README.md index 091cb303..c9a8f871 100644 --- a/plugins/GoogleSearchConsole/v1/docs/README.md +++ b/plugins/GoogleSearchConsole/v1/docs/README.md @@ -110,4 +110,4 @@ Verify that: - The property exists in Google Search Console - The signed-in Google account has access to the property - The property value exactly matches the identifier in Search Console -- A **403 "insufficient permission"** despite being an owner usually means the property *type* is wrong — e.g. entering `https://example.com/` for a **Domain** property. Use `sc-domain:example.com` instead (and vice versa) \ No newline at end of file +- A **403 "insufficient permission"** despite being an owner usually means the property *type* is wrong — e.g. entering `https://example.com/` for a **Domain** property. Use `sc-domain:example.com` instead (and vice versa)