Connecting Google Search Console to your app

Connect Google Search Console to your app to access search performance and indexing data.

Connect your app to Google Search Console to access search performance data, sitemaps, URL inspection, and indexing status for your sites, either from one Search Console account for the whole app or from each person’s own account.

You need a Builder plan or higher to use connectors in your app.

Track your own app on Google

Get your own Base44 app into Google Search.

---

What you can do

Use your site’s search data to monitor performance and indexing.

Track search performance

Pull clicks, impressions, CTR, and average position into dashboards and reports inside your app.

Check indexing status

Inspect URLs to see whether pages are indexed, and surface coverage issues as they appear.

Manage sitemaps

List and submit sitemaps for your verified sites so Google can discover your pages faster.

Example prompts

Describe the site, which search data to pull, and any dynamic fields in the AI chat. For example:

Sync search performance data from Google Search Console into my app.

Show top queries and pages from Search Console in a dashboard.

Check indexing status for URLs and surface issues.

List and manage sitemaps for my verified sites.

Export search analytics (clicks, impressions, CTR) to my app.

---

Connecting Google Search Console

Connect Search Console so your app can read search performance data.

Shared connector

You connect one account once, and everyone who uses your app shares that connection and its data.

To add a shared Search Console connector:

1. Click Connectors in your workspace sidebar.
2. Click Add connector.
3. Search for Google Search Console and click it.
4. Select Shared connector, then click Next.
5. Enter a Connection name.
6. Choose where the connection can be used in Who can access. The default is Apps and Super agent.
7. Click Add connector, then sign in with the Google account that has access to the properties you want.

App user connector

Each person connects their own Google account, so your app can work with the Search Console properties they can access.

Before you begin: Only workspace owners and admins can set up an app user connector, and you need your own OAuth client. See Using your own OAuth client.

To add an app user Search Console connector:

1. Click Connectors in your workspace sidebar.
2. Click Add connector.
3. Search for Google Search Console and click it.
4. Select App user connector, then click Next.
5. Enter a Connector name.
6. Enter the Client ID and Client Secret from your Google OAuth app.
7. Select what your app needs under Scopes. See Scopes and permissions.
8. Click Add Connector.
9. Open your app in the app editor.
10. Ask the AI chat to add a way for people to connect their own Google account.

---

Scopes and permissions

Scopes control what your app can do with your Search Console data.

1. Base44 adds

   • email: Identifies the Google account. It’s always included, so it shows as a locked scope under Scopes.
2. You configure

   Under Scopes, select what your app needs. Search Console scope names start with https://www.googleapis.com/auth/:

   • webmasters: View and manage data, including sitemaps
   • webmasters.readonly: View data without making changes

Access: Your app sees the Search Console properties the connected Google account can access.

If you need a scope that isn’t listed here, share your feedback with us.

---

Using Google Search Console in a backend function

Once Google Search Console is connected, your backend functions can retrieve an access token and call the Search Console API directly. Base44 handles the OAuth flow and token storage.

• For a shared connection, use getConnection() to retrieve the token.
• For an app user connection, use getCurrentAppUserConnection() so each request uses the signed-in person’s token.

// Shared connection: one account the whole app uses
const connection = await base44.asServiceRole.connectors.getConnection("google_search_console");
// Use the connection's access token to call the Search Console API.

Shared connectors

Configure, deploy, and call a shared connection from a backend function.

App user connectors

Retrieve a per-user token and call the API as the signed-in person.

---

Troubleshooting

Check account access and property setup if your search data is missing. If people can’t connect their own Google account, see Troubleshooting on the Google Workspace connectors page.

My Search Console data isn't showing up

Check the following.

• The connection is listed in your app’s Integrations page under App connections and shows as connected.
• The Google account you used has access to the Search Console property you want to query.
• The property you want to query is verified in Search Console.

If the issue continues, reconnect the connector.

The connector returns an empty result for a site

Search Console returns data for properties the connected account has permission to access, and new properties can take a few days to collect data. Confirm that account has access to the property, then check the same date range directly in Search Console.

---

FAQs

Which Google account should I use to connect?

Use the Google account that has owner or full access to the Search Console property you want to query. If you aren’t sure which account has access, check the users list in Search Console under Settings > Users and permissions.

Can I connect more than one Search Console property?

Yes. If you manage multiple properties under the same Google account, the AI chat can query data across them when you specify which property you want.

Where is my app's sitemap?

Base44 generates your sitemap at /sitemap.xml. When you describe sitemap tasks in the AI chat, you can reference this path directly.