Search Console — Topic Opportunities

What Topic Opportunities finds

The plugin queries your Search Console data for the last 28 days and surfaces searches where your site ranks in positions 5–20 — bottom of page one and page two. Google already half-trusts you for these queries; a dedicated article targeting one head-on is usually what moves it into the top spots. Results are sorted by impressions, so the biggest missed traffic comes first.

On young sites where nothing ranks that high yet, the window automatically widens to positions 5–50 so you still get topic ideas — the screen tells you when the wider window was used.

One-time setup (about 10 minutes)

The connection uses a Google service account — no OAuth consent screens, no app verification, nothing expires. Three steps:

Step 1 — Create a service account & key

1. Go to console.cloud.google.com and create (or pick) a project.
2. Under APIs & Services → Library, enable the Google Search Console API.
3. Under IAM & Admin → Service Accounts, click Create service account. Any name works; you can skip the optional role and access steps.
4. Open the new service account → Keys → Add key → Create new key → JSON. A .json file downloads — that’s the key you’ll paste into the plugin.

Step 2 — Give it read access in Search Console

In Search Console, open your property → Settings → Users and permissions → Add user. Paste the service account’s email address (it looks like name@project-id.iam.gserviceaccount.com — it’s in the JSON file as client_email). Restricted permission is enough. This step is the one people miss — without it, Google returns a permission error.

Step 3 — Paste both into the plugin

On MrNiche Autoblogger Pro → API & Integrations, fill in the Search Console section:

• Property — exactly as Search Console shows it. Domain properties use the form sc-domain:example.com; URL-prefix properties use the full URL, e.g. https://example.com/.
• Service-account key — open the downloaded .json file in a text editor and paste its entire contents. The plugin validates it on save and never displays it back.

From queries to queued articles

Once connected, Manual Posting gains a Topic Opportunities card showing your opportunity queries with clicks, impressions, and average position. Tick the ones worth an article, pick category/style/publish mode as usual, and queue. The plugin writes one title per query — keeping the query’s core words in the title, since that’s the ranking signal being reinforced — and every title still passes the normal duplicate-topic checks before it’s queued.

Troubleshooting

• “Search Console error … 403” — the service-account email hasn’t been added as a user on the property (Step 2). The error message on screen includes the exact email to add.
• “service-account key missing or invalid JSON” — the pasted key is incomplete. Re-open the .json file and paste the whole thing, from { to }.
• “JWT signing failed” — the private_key inside the JSON got mangled (usually by a rich-text editor). Re-paste from the original file using a plain-text editor.
• Empty results on a new site — normal for the first weeks after launch; Search Console needs impressions data to exist before there’s anything to mine. The 5–50 fallback kicks in as soon as anything ranks at all.
• Every failure is also written to MrNiche Autoblogger → Logs with the specific reason.

Version requirements

Search Console integration shipped in v6.4.0; the young-site position fallback in v6.5.0. Your server needs the PHP openssl extension (present on virtually all hosts) to sign the Google auth token.