SEOKit sign-in and access problems: what to check
Most sign-in problems come from an expired sign-in link, the wrong Google account or a permission you have not granted yet. This page maps every message you can see to its cause and the fix.
✓ Checked against the SEOKit code and Google documentation · October 2026
Most sign-in problems come from an expired sign-in link, the wrong Google account or a permission you have not granted yet. The first thing to try is to sign in again with the same Google account that owns, or has been added to, the Search Console property. If a property is missing, that account has no access to it in Search Console, and SEOKit cannot grant access that Google has not given (managing owners, users and permissions).
What each sign-in message means
When sign-in fails, the address carries a short code, and each one has a plain cause. invalid_state means the sign-in link expired, was used already or was opened in another browser; start again from SEOKit in a single tab. access_denied means Google reported that the request was cancelled or refused, for example because you pressed Cancel or the account was not allowed; try again and approve the permissions. no_code means Google redirected back without an authorization code; retry, and if it repeats, clear the cookies for seokit.biz and sign in again.
token_exchange_failed means SEOKit could not exchange the code for a token with Google, which is usually brief, so retry after a minute. identity_unavailable means Google did not return your profile, so SEOKit cannot tell who signed in; retry with the same account. credential_storage_failed means SEOKit could not save the encrypted connection; retry, and if it persists, write to the contact address in the privacy policy. In every case, begin from the sign-in button so that a fresh link is issued, rather than retrying the same expired one.
After you are signed in
“Google session expired. Sign in again.” means the saved token is no longer valid, for example because you removed SEOKit from your Google Account; sign in again, and do not remove SEOKit from your account merely to refresh it, since that revokes the permission and ends the connection until your next sign-in. If a property you own is missing, the signed-in account does not have access to it in Search Console, so switch account or ask an owner to add you. When a tool asks for more access, that is expected: Google Analytics 4 and write actions need their own permission, which you approve when prompted, and ordinary reports do not need it.
If a teammate sees nothing, they must sign in with the email you invited, accept the invitation within seven days and have the property shared with them. If a shared property cannot be changed, the access level is read or the member has no write permission, so ask the owner for full access. Never share your Google password with a colleague; invite them from the team page and they sign in with their own account.
Why Google shows a warning screen
A sign-in that requests sensitive permissions can show Google’s “app not verified” notice while an app’s verification is incomplete (unverified apps). SEOKit asks for identity only at sign-in and requests Search Console or Analytics access when you open a tool that needs it. Read what each permission allows before you continue; the article on what SEOKit stores lists them one by one.
Switching accounts
If you sign in with a different Google account, SEOKit clears the previous account’s saved properties, filters and workspace state, so one person’s data is never shown to another. Sign out first when you share a computer. To cut off access entirely, remove SEOKit from the list of third-party apps in your Google Account (third-party apps with access to your account).
Go further
Billing and privacy: What SEOKit stores and how tokens are protected. Getting started: How to log in to Google Search Console.