SEO Autopilot

Sign in

Sign in with Google. If this is your first visit you will be asked to name a workspace — it holds your sites, your keys and your data, and nobody else’s.

Continue with Google

We ask Google only for your name and email address. Search Console and Analytics are connected later, from your own account, and only if you want them.

PrivacyTerms

Sign in with GitHub and pick a different repository. The current one keeps working until you do.Sign in with GitHub, then pick this site's repository from a list. No token to copy.Shown on your GitHub App's settings page, under About.Generate one under Client secrets on the same page. It lets people sign in so only repositories they can push to are offered.Add a domain you control and prove it with a DNS record.Apply the selected mode. Recorded with your reason; nothing publishes without approval unless you chose autopilot.Authorise Google Analytics 4 for this site through your own Google OAuth client.Authorise Search Console for this site through your own Google OAuth client.Cancel this invitation. The address can no longer join with it.Check DNS now for the TXT record shown above. Safe to retry while it propagates.Conversations, scheduled routines, keyword clusters and content briefs for this site.Create the workspace and make you its owner. You can rename or invite people afterwards.Dry run: reports what the current policy would allow or block on open proposals. Changes nothing.End this session on this browser. Your workspace, keys and sites are untouched.From your own Google Cloud OAuth client. Ends in .apps.googleusercontent.com — not the project number and not an API key.How far this site may go on its own. Observe measures only; recommend drafts proposals for approval; autopilot deploys unattended.How many different people must approve a change before it can deploy. An author can never approve their own.Invite this address into this workspace. They join on their next sign-in and can see everything in it.Issue a fresh verification token. The previous record stops working immediately.Issue a verification token for this domain and show the TXT record to publish.Kill switch. Blocks every automated deployment for this site until an owner lifts it after an incident review.Look up DNS now. Safe to retry — records can take minutes to hours to appear.Open a revert pull request. The change is only undone once someone merges it.Open the pull request that carries this change on your repository. A human still merges it.Record your approval. You cannot approve a change you authored yourself.Register the domain and issue a one-time TXT record proving you control it.Remove this person from the workspace. Their account survives; their access here does not.Replace the token with a fresh one. The old record stops working immediately.Revoke your stored credential and go back to this deployment's shared client. Each Google connection will ask to be reconnected once, because a refresh token cannot be renewed by a different client.Run one mobile Lighthouse sample. Lab data, not real-user Core Web Vitals.Save this approver count. It applies to proposals drafted from now on, not to ones already waiting.Sign in with Google once. Search Console and Analytics are connected for every verified site whose property that account can see.Sign in with your Google account. We ask only for your name and email address.Start a bounded crawl of this site now. Read-only: it gathers evidence and changes nothing on the site.Store an access token for this repository. Prefer the GitHub App when you can install it.Take this proposal off the table. It stops counting toward approvals and cannot deploy.The last part of your GitHub App's public URL.The numeric ID on your GitHub App's settings page.The secret beside that client ID in Google Cloud. Stored encrypted; no page ever reads it back to you.The whole .pem file your GitHub App issued, including the BEGIN and END lines.Turn this opportunity into a reviewable proposal with an exact diff. Publishes nothing.Why you are changing the mode. Required by the API and recorded in the audit trail against your name.