Documentation
Connecting Search Console
Sign in, then give AutoPSEO read-only access to Search Console in a separate Google consent. Every property that account can read is imported at once.
AutoPSEO asks Google for two separate consents. The first signs you in and shares only your name, email address and profile picture. The second, which you start from inside the app, lets AutoPSEO read Search Console, and it stays read-only unless you ask for more. As soon as it is granted, every property that Google account can read is imported, so there is nothing to add by hand.
Step 1: sign in
Open the app and choose Continue with Google; your account is created the first time you do. Once it exists, the sign-in page can also email you a one-time link (it works once and expires after 20 minutes), and after you set a password in Account settings, Sign in with email instead works too.
Your first sign-in starts the 7-day trial, with no card required. To look before you connect anything, Explore the demo property opens sc-domain:demo.autopseo.app with sample data.
Step 2: grant Search Console access
While no linked Google account can read Search Console, My Sites shows a short setup card. Its first step, the Add properties button in Dashboard Management and in the property switcher, and Connect Account on the Account page all open the same choice:
| Option | Google scope | What it unlocks |
|---|---|---|
| Read-only | webmasters.readonly | Every dashboard, report and export, and the analysis tools over MCP |
| Full access | webmasters | All of that, plus URL inspection, the Index Tracker and submitting sitemaps from the Sitemaps report |
Google's consent screen then shows the permission you picked. Choose the Google account that can see your properties; it does not need to be the account you signed in with. AutoPSEO keeps an encrypted refresh token for it and never sees your password. At either level, AutoPSEO changes nothing in Search Console beyond the actions listed above, and only when you start one.
What gets imported
Every property the account can read appears in AutoPSEO, labelled with the permission level Google reports for you: Owner, Full User, Restricted or Unverified. Your plan decides how many arrive switched on for My Sites: 10 during the trial and on Starter, 50 on Pro and 500 on Business. The others are imported switched off. Choose which ones you see in Dashboard Management, and press Refresh from Google there after adding or verifying a property in Search Console.
If the account cannot read a single property, My Sites tells you and shows the demo property in the meantime. Verify the site in Search Console, then refresh.
Domain and URL-prefix properties
Both property types appear exactly as Search Console holds them, each with a badge. Google draws the line like this:
- A Domain property (
sc-domain:example.com) "aggregates data for all subdomains, protocols, and subpaths", and the only way to verify one is a DNS record. - A URL-prefix property (
https://www.example.com/) holds only URLs that start with that prefix.httpandhttpsneed a property each, and subdomains such asm.example.comare left out.
They are different properties with different data, so one site can be listed twice. Google explains both in Add a website property, and our FAQ compares them in Domain property vs URL prefix.
Linking more than one Google account
Choose Connect Account again and pick another Google account. The Account page lists every linked account with the permissions it holds. When two linked accounts can read the same property, AutoPSEO keeps it as one property with one set of settings.
Unlink account removes a connection. Its properties stay in AutoPSEO but lose their data source, and full storage is switched off for them, so their reports fail until you reconnect an account that can read them or remove them with Clean up inaccessible in Dashboard Management.
Changing or revoking access
- Enable full access beside a linked account adds the wider permission when you need URL inspection or sitemap submission.
- Grant Google Analytics access is a separate, read-only consent for the GA4 reports; afterwards you pair a GA4 property with each site, as described in Connecting GA4.
- Connecting an account again with Read-only replaces its grant. Full access or Google Analytics access granted before then has to be granted again.
- A Re-authorization required badge means Google no longer accepts the stored token. Choose Re-authorize.
- To withdraw access completely, remove AutoPSEO under Google account permissions. Do the same if Google reports that it returned no refresh token, then connect again.
Live data and full storage
By default, reports read live from the Search Console API, and Google keeps the last 16 months (Google's note). Switching on full storage for a property copies those 16 months into AutoPSEO and adds each new day, so long ranges load quickly and the history keeps growing past Google's window. Your plan sets how many properties you can store; see Dashboard Management.
Next steps
Enter your brand terms under Property Setup → Branded Keywords so reports can separate branded from non-branded searches, open the dashboard, and when you are ready, set up the content engine.