What Search Intelligence does
Search Intelligence compares the current WordPress site with selected evidence returned by Google Search Console. The Google connection is read-only. It does not submit URLs for indexing, alter Search Console properties or run Google’s live URL test through the API.
1. Enable the Search Console API
- Open Google Cloud Console and create or select the project you want to use for Site Doctor.
- Enable the Google Search Console API for that project.
2. Configure Google Auth Platform
Set up the OAuth consent configuration for the project. Use your real product or company name, add your site as the application home page, add the privacy-policy and terms pages you actually publish, and add your verified domain where Google requests an authorized domain.
For a new setup, External/Testing is suitable while you validate the connection. Add the Google account that owns or can access the relevant Search Console property as a test user when Google requires it.
3. Use the read-only Search Console scope
Site Doctor requests https://www.googleapis.com/auth/webmasters.readonly. Do not replace it with a broader write scope just to make setup easier.
4. Create the OAuth client
- Create an OAuth client with application type Web application.
- You normally do not need an Authorized JavaScript Origin for this server-side connection.
- In Site Doctor, open Settings or the Search Intelligence connection panel and copy the callback URI shown there.
- Add that exact value to Google Cloud under Authorized redirect URIs.
For the current Pro callback architecture, the URI uses WordPress admin-post and has this form:
https://YOUR-DOMAIN.example/wp-admin/admin-post.php?action=tnsdp_gsc_oauth
Always copy the exact URI displayed by your own Site Doctor installation. A different domain, scheme, path, query parameter, missing slash or older callback format can produce redirect_uri_mismatch.
5. Store the Client ID and Client Secret in WordPress
Copy the OAuth Client ID and Client Secret from Google Cloud into Site Doctor’s Google connection settings and save them. Treat the Client Secret as a credential. Do not send it in an ordinary support email, screenshot or chat message.
6. Connect and choose the correct property
- Open Search Intelligence and choose Connect.
- Sign in to the Google account that has Search Console access and approve the read-only permission.
- After Google returns you to WordPress, choose the Search Console property that matches this WordPress site. Site Doctor marks a matching property as recommended when it can determine one.
How to read the evidence
URL Inspection: Google’s API describes Google’s indexed copy, which may reflect an earlier crawl. Site Doctor displays it beside the live WordPress response, canonical and indexability evidence so a difference can be investigated rather than treated as automatic proof of an error.
Search performance: clicks and impressions are Google Search performance metrics. They are not website visitors or analytics sessions. CTR and average position are descriptive averages and are not ranking guarantees.
Top pages and query candidates: Search Console can omit lower-volume rows when dimensions are requested, so these tables are useful candidates from returned data rather than an exhaustive keyword inventory.
Sitemaps: Site Doctor reports submitted-sitemap metadata such as processing state, errors, warnings, submitted URL counts and Google-reported dates without relying on the deprecated indexed-count field.
If Google shows redirect_uri_mismatch
Open the error details and compare the redirect_uri Google says was sent with the Authorized redirect URI saved in Google Cloud. They must match exactly. Remove obsolete callback URIs only after the current one is confirmed.
If the property is missing
Confirm that the signed-in Google account has access to that exact Search Console property. URL-prefix properties with and without www are separate properties, and a domain property is also distinct from a URL-prefix property.