When Google needs reconnecting

Blog AI reads your Search Console and Google Analytics data with a long-lived permission that Google gives it when you connect. Google can withdraw that permission, and when it does, your data stops updating until you reconnect. Nothing is lost: everything already synced stays, and reconnecting picks up where it left off.

How you'll know

• A banner at the top of Home says a Google account can no longer be read, and which sites are not updating.
• The Actions page puts Reconnect Google at the very top, above everything else, because every other number depends on it.
• The Sites card says the Google connection needs reconnecting and "Data for this site has stopped updating".
• An email tells you the same thing. It's sent at most once a week for each Google connection, so you won't get one every day.

Why it happens

Google withdraws an app's access when:

• you, or an admin, removed Blog AI from the Google account's third-party access list (myaccount.google.com/permissions)
• the Google account's password was changed, which can reset access for some apps
• your Google Workspace admin changed the rules on which apps may read company data
• access was only partly granted: someone unticked Search Console or Analytics on Google's consent screen
• during early access, the permission expired: while Google is still verifying Blog AI, it limits how long this kind of permission lasts, so test accounts may need to reconnect after about a week

It isn't anything you did in Blog AI, and it doesn't mean your site has a problem.

Reconnect

1. Click Reconnect. Use Reconnect Google on the banner on Home, Reconnect on the Actions page, or on the site's card on Sites.
2. Pick the same Google account. Blog AI suggests the account that was connected. Choosing the same one brings every site that used it back at once.
3. Allow access and tick every box, as when you first connected.
4. Check the Sites card. It should show the connection as active again. Click Sync now if you'd like the latest data straight away; otherwise the next automatic sync catches up.

Reconnecting doesn't change your chosen Search Console and Analytics properties. If you pick a different Google account instead, you'll be asked to choose properties for it.

What's kept while you're disconnected

• All data synced so far stays: your performance report, post charts, audit and Actions list keep showing the last numbers, with the date they're from.
• Your posts, drafts and voice aren't affected. You can still write, edit, publish and schedule; publishing uses your WordPress or Strapi connection, not Google.
• The gap fills itself. When you reconnect, the next sync fetches the missing days, as far back as your plan keeps history (16 months on a paid plan, 3 on the free plan).

What does stop: new numbers, new opportunities on your Actions page, and anything that needs fresh data, such as the weekly digest's "posts that moved".

If reconnecting doesn't work

Google says access is blocked, or you can't find the property

Your Google Workspace admin may have restricted which apps can access company data. Ask them to allow Blog AI, or connect a personal account that has been added as a user on the Search Console property.

It works, then breaks again a week later

That's the early-access expiry described above. It stops once Google has verified Blog AI.

You no longer have access to the property

If someone removed your account from the Search Console property, reconnecting won't help. Ask for access again, or connect an account that still has it and choose the property again.

Related

• Connect Search Console and Google Analytics covers the first connection and picking properties.
• The weekly email and other notifications lists every email Blog AI sends, including this one.