How Blogo works
How the Search Console connection works
Blogo connects to Google Search Console with one read-only permission. It can read your search performance data and ask Google about the indexing state of a page. It cannot change anything in Search Console or on your site. Connecting is optional; without it, planning uses your site and public search data only.
One consent screen, one permission
Connecting Search Console is a separate step from signing in to Blogo. Signing in with Google does not give Blogo any Search Console access. When you press “Connect Search Console”, Google shows a consent screen that asks for a single permission: view Search Console data for your verified sites. That is Google’s read-only scope, and it is the only one Blogo requests.
The connection link is signed and expires after ten minutes. When Google sends you back, Blogo checks that the browser is still signed in as the same Blogo user who started the connection before it accepts anything.
Google returns an access token and a refresh token. Both are encrypted before they are stored. If the server has no encryption key configured, Blogo refuses the connection instead of storing a token in plain text.
Which property Blogo reads
A Google account often holds several verified properties. Blogo reads the one that matches the site you added, either its URL-prefix property or its domain property, and no other. If nothing matches exactly, it does not fall back to the first property in the list or to a parent domain. It tells you that no verified property matches this site, and you verify the site in Search Console first.
Rows whose page address does not belong to the matched property are dropped before anything is saved.
What is pulled, and when
Blogo asks for search performance broken down by page and query. The window is the last 16 months, ending three days before today because Google’s figures lag by a few days. A sync is capped at 25,000 rows.
- For each page and query pair: clicks, impressions, click-through rate and average position.
- A sync runs once when you connect, and again whenever you press “Sync now” in settings. There is no background sync.
- Each sync replaces the previous snapshot for the site rather than adding to it, so the same query is never counted twice.
What the plan does with it
The data answers two planning questions that public search data cannot.
First, which existing pages are worth refreshing. Blogo looks at pages with a meaningful number of impressions and pays particular attention to pages whose average position sits between 8 and 20, because those already appear for the query but are rarely clicked. Second, which queries your site already appears for without a page that clearly answers them. Those become candidates for a new article.
Blogo keeps the impressions, click-through rate and average position with each suggestion built from this data, as the evidence for it.
The connection is also what makes the indexing follow-up possible: once an article is live, Blogo can ask Google whether it is showing that page.
What Blogo cannot see or do
The permission is read-only and limited to Search Console.
- It cannot submit a sitemap, request indexing, remove a URL or change any Search Console setting.
- It does not give access to Google Analytics, Google Ads, Gmail, Drive or anything else in your Google account.
- It cannot see who searched. Search Console reports totals for queries and pages, not people.
- It does not read properties that do not match the site you added.
- It only knows what the last sync returned. If you have not synced recently, the plan is working from older figures.
Questions
Do I have to connect Search Console to use Blogo?
How do I remove Blogo’s access?
It says no verified property matches my site. What now?
How fresh is the data?
Plan from your own search data
Add your site, connect Search Console and see the first suggestions. Blogo is in a free, invite-only pilot.