Account and access
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
Start here
Sign in again with the same Google account that owns or has been added to the Search Console property. If a property is missing, the account has no access to it in Search Console; SEOKit cannot grant access that Google has not given.
Search Console access levels are explained in Google’s permissions guide ↗ .
What each sign-in message means
The address shows ?auth_error= followed by a code. Find yours below.
Invalid state
The sign-in link expired, was used already or was opened in another browser. Start sign-in again from SEOKit in a single tab.
Access denied
Google reported that the request was cancelled or refused, for example you pressed Cancel or the account was not allowed. Try again and approve the permissions.
No code returned
Google redirected back without an authorization code. Retry; if it repeats, clear the cookies for seokit.biz and sign in again.
Token exchange failed
SEOKit could not exchange the code for a token with Google. This is usually brief; retry after a minute.
Identity unavailable
Google did not return your profile, so SEOKit cannot tell who signed in. Retry with the same account.
Credential storage failed
SEOKit could not save the encrypted connection. Retry; if it persists, write to the contact address in the privacy policy.
Symptoms after you are signed in
The saved token is no longer valid, for example because you removed SEOKit from your Google Account. Sign in again.
The signed-in Google account does not have access to it in Search Console. Switch account or ask an owner to add you.
Google Analytics 4 and write actions need their own permission. Approve it when prompted; ordinary reports do not need it.
They must sign in with the email you invited, accept the invitation within seven days and have the property shared with them.
The access level is read, or the member has no write permission. Ask the owner for full access.
ACCOUNTS
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. 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.
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 sharing a computer.
What not to do
Do not share your Google password with a colleague
Invite them from the team page instead; they sign in with their own account.
Do not retry the same expired link
Always start from the sign-in button so a fresh link is issued.
Do not remove SEOKit from your Google Account to “refresh”
That revokes the permission and ends the connection until you sign in again.