How to Connect Google Search Console to Aegisify SEO
Connecting Google Search Console to WordPress, creating a Google OAuth client, enabling the Search Console API, matching the correct GSC property and submitting XML sitemaps are the key steps required before Aegisify SEO can display Search Console intelligence inside WordPress.
The setup uses Google OAuth 2.0. Your WordPress site does not receive your Google password. Instead, Google asks you to approve specific Search Console access for the OAuth client created in your Google Cloud project.
Verified GSC Property
Create and verify a Domain property or an exact URL-prefix property for the production website.
Google Cloud Project
Use one selected project for the OAuth consent configuration, client credentials and Search Console API.
OAuth Web Client
Create a Web application client with the exact redirect URI required by the Aegisify SEO callback.
Aegisify Connection
Save the client credentials, authorize the correct Google account and select the exact property returned by Google.
Create and Verify the Search Console Property
Open Google Search Console, select Start now and add the website property. Google generally recommends a Domain property when DNS verification is available because it combines supported protocols and subdomains under one property.
Enter only the domain, such as example.com. Do not include https://, www as the root-property prefix, a trailing slash or a path. Domain properties require DNS verification.
Enter the complete prefix, including protocol and final slash, such as https://www.example.com/. Protocol, hostname and path are part of the property definition.
After verification, open Sitemaps in Search Console. In WordPress, open Aegisify SEO → SiteMap, copy each public XML sitemap URL and submit it under the matching Search Console property. Sitemap submission supports discovery and reporting; it does not guarantee crawling, indexing or rankings.
Select or Create the Google Cloud Project
Open the Google Cloud Console. Create a project or select the project that will own the Aegisify SEO OAuth client. Keep the same project selected through the remaining Google Cloud steps.
Do not simply choose the newest project. The OAuth client, consent-screen configuration, test users and Search Console API must belong to the same selected project. Confirm the project name or project ID shown in the Google Cloud header before continuing.
Configure Branding, Audience and Data Access
Open the Google Auth Platform for the selected project and complete the required application information. Add an application name, user-support email and developer contact details. Use accurate organization and domain information.
Choose the audience that matches the deployment:
Use only when the app is limited to users inside an eligible Google Workspace organization.
Use for ordinary Google accounts or users outside the organization. External apps can remain in Testing while setup is validated.
Request only the Search Console scopes the plugin needs. Google documents webmasters.readonly for read-only access and webmasters for read/write access. Aegisify SEO should request the minimum scope required by the current production workflow.
Create the OAuth 2.0 Web Application Client
Open Google Auth Platform → Clients, select Create client and choose Web application.
Under Authorized redirect URIs, paste the exact callback URL shown in Aegisify SEO → Search Console. A typical installation may use:
https://yourdomain.com/wp-admin/admin.php?page=aegisseo&tab=searchUse that example only when it exactly matches the URI displayed by the installed Aegisify SEO version. Google compares redirect URIs exactly, including protocol, hostname, path, query parameters and trailing slash.
Authorized JavaScript origins are required only when client-side JavaScript initiates Google API requests. For a server-side WordPress OAuth flow, the redirect URI is the critical value. Add origins such as https://example.com or https://www.example.com only when the current Aegisify interface specifically requires them.
Create the client, then copy the Client ID and Client Secret. Treat the Client Secret like a password. Store it only in the protected Aegisify SEO configuration and an approved secrets system.
Enable the Google Search Console API
With the same Google Cloud project selected, open APIs & Services → Library, search for Google Search Console API and select Enable. Google’s Search Console API documentation requires OAuth 2.0 for access to private Search Console data.
Add the Google Account as a Test User When Required
Open Google Auth Platform → Audience. When an External app is in Testing, scroll to Test users, select Add users and enter the Google account that will authorize Aegisify SEO.
Test users are not required for an eligible Internal app or when the External app has been moved to In production. Google states that authorizations for test users can expire after seven days when the app requests scopes beyond basic identity information. Reauthorization during testing may therefore be expected.
Final Step: Connect Aegisify SEO to Google
Go to Aegisify SEO → Search Console.
Paste the Client ID and Client Secret.
Use the exact property format expected by the plugin.
Select Connect Google Account and approve the requested access.
Choose the exact property and confirm data loads.
For a Domain property, the user-facing setup value is commonly example.com, while the Search Console API can identify that property as sc-domain:example.com. A URL-prefix property must match the full URL, such as https://www.example.com/. Select the property returned by Google instead of guessing.
Where to View Search Console Intelligence
After the connection succeeds, open Aegisify SEO → SEO Ops Center. Depending on the current build and license, the connected workflow can expose Google Search Console performance summaries, Search Stats, page and query drilldowns, CTR opportunities, comparison windows, winner and loser pages, ranking-volatility context and Schema Intelligence.
Search Console data is delayed and should not be interpreted as real-time analytics. Average position is an aggregated Search Console metric, not a fixed daily rank. A change in clicks, impressions or CTR can reflect demand, seasonality, query mix, SERP presentation or site changes.
Google Search Console Connection FAQ
Why do I receive a redirect_uri_mismatch error?
The redirect URI saved in Google Cloud does not exactly match the callback sent by Aegisify SEO. Copy the current URI directly from the plugin and compare protocol, hostname, path, query string and trailing slash.
Why do I receive “User does not have sufficient permission” or HTTP 403?
Confirm that the authorized Google account has access to the exact property selected in Aegisify SEO. Also confirm that the Search Console API is enabled in the correct project and reauthorize after permission changes.
Should the Property URL include https://?
A Domain property does not include a protocol and is commonly entered as example.com. A URL-prefix property includes the complete protocol and hostname. Follow the exact property type created in Search Console and the field format required by the current Aegisify build.
Why is the connection successful but no data appears?
Confirm the property receives Google Search traffic, check the selected date range, allow for reporting delay and verify that the property is not a different protocol or hostname.
Do I need to publish or verify the OAuth app?
A private test connection can use Testing with approved test users. An app intended for broader external use may require production publishing and Google verification, depending on the scopes and audience.
Does submitting a sitemap guarantee indexing?
No. A sitemap helps Google discover eligible URLs. Google independently decides whether and when to crawl, index or rank each page.
Google and Aegisify Documentation
References include the Aegisify SEO User Guide, Google Search Console property setup, Search Console API authorization, OAuth for web server applications, Google OAuth client management, and Google Auth Platform audience and test-user guidance.