Google Search Console
Your Search Console, put to work
Search Console already knows what people search for when they find you, and where you’re nearly on page one. Blog AI reads that data, read-only, and turns it into a ranked list of posts to write and fix, a free content audit, and a record of what every post did afterwards.
You connect it per site from the Sites page, in about two minutes.
What Blog AI reads
Only performance data, for the property you pick, going back 16 months on a paid plan (as far as Search Console keeps it) or 3 months on the free plan.
| Data | What it is |
|---|---|
| Pages | For each page, per day: clicks, impressions (times it was shown in results) and average position. |
| Searches (queries) | The searches each page was shown for, with their clicks, impressions and position. This is what the Actions list and ideas are built on. |
| Countries and devices | Site-wide splits, shown on the performance report. |
Blog AI doesn’t read your Search Console settings, users, sitemaps, indexing reports or messages. The permission it asks for doesn’t allow it.
What it powers
Your Actions list
Posts that start from real searches
The free content audit
Per-post performance
Refresh suggestions
Your free AI-visibility snapshot
The five things Blog AI looks for
Blog AI compares your latest 28 days of data with the 28 days before and looks for these patterns. Each finding comes with the numbers behind it, in a sentence.
| Finding | The rule |
|---|---|
| Striking distance | A search where you rank between position 4 and 20 (just off the top of page one) and were shown at least 100 times. The estimate is the clicks you'd get at position 3. |
| Shown but rarely clicked | A page on page one (position 10 or better), shown at least 200 times, whose click-through rate (the share of people who click) is under half what that position usually gets. Usually a title or description problem. |
| Losing traffic | A page that had at least 20 clicks and lost 25% or more of them. |
| Competing with itself | Two or more of your pages each getting at least 10% of a search's impressions, so they split the clicks (sometimes called cannibalisation). |
| Searches you have no post for | A search you were shown for at least 100 times without any post in the top 20. A gap you could fill. |
Connect Search Console
Step 1: Add your site
Sign in to Blog AI with Google and add your WordPress or Strapi site on the Sites page.
Step 2: Click Connect Google
Choose the Google account that has access to your Search Console property. Google shows a consent screen listing read-only access to Search Console and Google Analytics. You can untick Analytics if you only want Search Console.
Step 3: Pick your Search Console property
Blog AI lists the verified properties the account can see, both domain properties (the whole domain) and URL-prefix properties (one address). It marks the ones that cover your site, and won't save one that doesn't.
Step 4: Save and sync
The first sync brings in recent days within minutes, then keeps filling in older history in the background. Your Actions list, audit and performance report fill in as the data arrives.
How the sync works
Blog AI syncs every connected site once a night and fetches the last few days again each time, because Search Console revises its most recent days. Older history is filled in the background, window by window, until it reaches 16 months back (3 on the free plan).
Search Console’s data usually arrives a couple of days after Google Analytics’, and each runs on its own clock. Blog AI shows a “data through” date for each source rather than pretending yesterday is complete. You can also press Sync now on the Sites page (once every 10 minutes per site).
Each page is matched to a post by its address, ignoring http or https and www, and a trailing slash. A page that two posts claim equally isn’t credited to either, so a post never shows another post’s traffic.
If you switch to a different property, Blog AI deletes the data from the old one and syncs the new one, so your charts never mix two sites.
Your data
Your Google access is stored in an encrypted vault and used only by our servers to sync your data. Blog AI uses Google data only to provide the features you see, never for advertising, and never to train general-purpose AI models. When the writer plans a post, the relevant searches are sent to our AI provider for that job. The full detail is in our privacy policy (section 4, Google user data) and on our security page.
What it doesn’t do
- It isn’t a rank tracker: it uses the positions Search Console reports for your own site, not positions for any keyword you type in.
- It doesn’t research keywords you have never appeared for, or analyse competitors’ sites.
- It doesn’t run technical checks such as page speed, broken links or structured data.
- It doesn’t change anything in Search Console.
What it costs
Nothing. Connecting Search Console, syncing, the Actions list, the audit and the performance report are part of the free plan. Credits are used only when you act on a finding, for example by writing or refreshing a post. See pricing.
Questions about Search Console
Can Blog AI change anything in my Search Console?
No. Blog AI asks Google for the read-only Search Console permission (webmasters.readonly). It can read performance data for the properties you choose. It can't submit sitemaps, remove URLs, add users or change settings.
Which Google account should I connect?
Any account that can see the site's property in Search Console. It doesn't have to be the account you sign in to Blog AI with, and each site can use a different Google account, which helps agencies whose clients grant access to different addresses.
Why don't my numbers match Search Console exactly?
Blog AI adds up page-level data, like the Pages tab in Search Console. Search Console's overall total counts a search that shows two of your pages as one impression, so our impression totals can be slightly higher. Clicks are nearly identical. Search Console also hides some rare searches for privacy, so the searches listed never add up to total clicks.
My site is new and has almost no Search Console data. Is Blog AI still useful?
Yes, but less so at first. You can still write about your own topics, import your posts, learn your voice and publish. The Actions list and the audit get more useful as Search Console collects data about your site, which for a new site takes weeks.
How do I disconnect?
Disconnect the Google account in Blog AI, which also withdraws our access at Google, or remove Blog AI from the third-party access list in your Google account. Deleting your Blog AI account deletes the synced data and withdraws access too.
What if Google stops giving Blog AI access?
If the access is revoked or expires, for example after a password change, Blog AI shows a reconnect prompt on Home and emails you, at most once a week. Your synced data is kept, and reconnecting the same account resumes the sync.
Start with the data you already have
Sign in with Google, no card needed. The free plan includes a content audit and one free post once Search Console has synced and you've set your voice. Plans from $49/month.