Google Search Console

Google Search Console is a connector: it links a MeDo app to one Search Console account, so the app can list verified properties, read search performance, inspect a known URL, and list or submit sitemaps after review. Everything the app sees comes from the account you connected.

#What you can build

• A search performance dashboard. List the owner's verified properties and show clicks, impressions, CTR, and average position for an explicit date window.
• A URL inspection tool. Check whether one known page is indexed and show the coverage state.
• A sitemap monitor. List submitted feeds, read a feed's last submitted and downloaded times, and confirm before submitting an existing sitemap.
• A property register (optional). Register a URL-prefix property the owner asked for. Registration is not verification, and this connector cannot delete an unverified leftover.

Search Console fits when the app needs the owner's real search and coverage data. It is not a rank editor, a domain-verification tool, or an Indexing API client — see Limits.

#Build examples

Copy one of these into the prompt box. The first one is the smallest useful starting point.

Use @Google Search Console to build a private SEO dashboard that lists my verified properties and shows last week's clicks, impressions, CTR, and average position.

Use @Google Search Console to build a private URL inspection tool where I paste one page URL and see whether it is indexed.

Use @Google Search Console to build a sitemap monitor that lists submitted feeds for a chosen property and shows last submitted and downloaded times.

Use @Google Search Console to build a private sitemap tool that previews an existing feed path and submits it only after I confirm.

The wording matters: say who the tool is for and what it should do. "A private SEO dashboard for the site owner" produces a different app from "a page that lists sites".

#Prepare and connect

You need a Google account that already owns or can manage the Search Console properties the app should use. No API key, no Google Cloud project, and no billing setup are involved.

1. Open Skills & Connectors in the sidebar and search for Google Search Console.
2. Open the Google Search Console card and click Connect.
3. Sign in to the Google account and approve the access MeDo asks for.
4. The button changes to Connected. That is the success state; you do not need to copy anything back into the app.

If you start building before connecting, MeDo notices and shows a Search Console connection button under its reply. You can connect there instead. If no button appears, use the connector card described above.

#Use it in your app

• The app uses the owner's connected Search Console account, not each visitor's own Google account. Every visitor who reaches a property or analytics view sees the same account. Keep those pages behind your app's own sign-in, and restrict them to the people who should have that access. A page titled "private" is not access control on its own.
• Copy property URLs from the connected account. Use the exact siteUrl Search Console returns. Do not reconstruct sc-domain: or URL-prefix values by hand.
• Analytics need an explicit date window. Use YYYY-MM-DD start and end dates. Empty rows mean no impressions in that range, not that a URL is missing from the index. Data can lag two to three days.
• Keep search query terms off public pages. Query strings can be sensitive. Default dashboards should use property-level totals or other non-query dimensions unless the owner accepts publishing that traffic.
• Sitemap submission and property registration are confirmed first. MeDo previews the property or feed path and waits for an explicit confirm. Do not retry a write when the result is unknown.
• App-owned notes stay in the app. Ranking comments, alert snapshots, and page-level notes belong in your app's own tables, keyed to a real property or page URL. They are not Search Console fields.

#Limits and troubleshooting

"Connection required" appears in the app. The Search Console connection belongs to the app owner. Ask the owner to open the connector card and click Connect, then reload.

Analytics show zeros. That usually means the window has no impressions yet, or the data has not landed. It is not a silent failure. Widen the dates or wait for the two-to-three-day lag before treating it as missing coverage.

A sitemap submit or add-site result is unknown. Do not click again. Read the property or feed list first; a retry can register a second leftover or resubmit the same feed.

Visitors can see search data when they should not. The connection is shared. Add sign-in and server-side restrictions to the app; see Managing access & roles.

#Related

• Connector catalog — the other connectors and what they are for.
• Skills & Connectors — how Skills are called, priced, and limited.
• Managing sign-in & users — give an app its own accounts before exposing connected data.