Blogizi
Start for $0
Documentation/Features/Google Search Console integration
Documentation

Google Search Console integration

Connect Google Search Console to Blogizi: clicks, impressions and positions compared with the previous period, a ranked list of what to write next, and index status for every post.

Blogizi pulls Search Analytics from Google Search Console into each project's Search tab, and exposes the same data through the Search analytics API and the get_search_performance MCP tool, so your agent can check how posts perform before it writes the next one.

Before you start

  • A Google account with access to the Search Console property (Owner, Full or Restricted user all work for reading)
  • The property verified in Search Console. For hosted blogs (*.app.blogizi.com or a custom subdomain), paste Google's HTML-tag verification token under project Settings → SEO and click Verify in Search Console.

Setup

  1. Connect Google under Dashboard → Account (or from the project Search tab). Blogizi asks for read-only Search Console access (webmasters.readonly). It can't change anything in your Search Console.
  2. Bind a property in the project's Search tab. Blogizi suggests the URL your blog is served from. You can also pick any other property your account can see, including a domain property (sc-domain:yourapp.com) if your blog lives in path mode under your main site.
  3. Blogizi runs the first sync right away. After that it syncs daily.

What you get

DataDetail
OverviewClicks, impressions, CTR and average position compared with the previous period, a daily chart with your published posts marked, rising and falling queries, where your queries rank, countries and devices
OpportunitiesQueries on page 2 ranked by opportunity, each with the page to improve or a new post to write; pages people see but skip; queries new this period; two posts competing for one query
Queries & pagesEvery stored query and page (up to 1,000 each) with changes vs the previous period, filters and CSV export
IndexingIndex status for every published post from Google's URL Inspection API, time to index, and your sitemap status
Ranges7 days, 28 days, 3, 6, 12 or 16 months

Freshness

  • Blogizi syncs every bound project once a day, plus immediately when you bind a property.
  • The API accepts refresh=1 to sync on demand (at most once every 5 minutes per project).
  • Google's own data lags 2–3 days, so the most recent days are always missing or partial.
  • Index status is checked daily for posts published or updated in the last 60 days until Google indexes them, then weekly. Only posts whose URL belongs to the bound property can be checked. Google doesn't let apps request indexing, so each post links to Search Console's own inspection page for that.

Use it from your agent

Ask your agent something like “Use get_search_performance with include opportunities and draft posts for the top three page-2 queries.” See get_search_performance for the arguments and result shape.

Troubleshooting

  • No properties listed: you connected a Google account that doesn't have access to the property. Disconnect and reconnect with the right account, or add that account as a user in Search Console.
  • All zeros: the property is new, or the bound property doesn't match where the blog is served (for example, binding https://blog.yourapp.com/ when the blog is at yourapp.com/blog). Bind the domain property instead.
  • Data looks stale: check lastSyncedAt. Use refresh=1 on the API, or wait for the daily sync.

Separate from visitor analytics

First-party blog analytics tracks visitors on your site. Search Console tracks Google Search. They live in different dashboard tabs on purpose.