Repository navigation
Simplify local onboarding and Google connections - #33
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New local users can run
pnpm start, add their website, and authorize Search Console and GA4 without creating a Google Cloud project or entering OAuth credentials. First startup prepares private local configuration automatically. Brand settings combine website/Google, Browser, API Key and monitoring; the sidebar preserves SEO and GEO sections and exposes short/brand,/seoand/questionsroutes with BeatGEO branding.The shared Google flow uses PKCE and session-bound state, records only granted scopes, retries busy property discovery, and keeps user grants encrypted locally. The bundled pair belongs to the BeatGEO Desktop installed-app public client in the BeatAPI project; it is intentionally distributable under Google's installed-app model, not a Web application secret. Custom desktop clients require a matching pair; hosted deployments require separate Web credentials. No user tokens, private environment files or raw analytics are included.
Validation:
pnpm lint; web TypeScript check; 94 targeted OAuth/navigation tests; 25 installation/script tests; all 14 isolated SEO browser flows, including adding reviewed questions to GEO through the visible report action. A non-authorizing request using only the bundled pair reaches Google's authorization-code validation. Real Google consent and GSC/GA reads were exercised with the maintainer account; fresh-user/cross-platform acceptance is not claimed. Brand and Analytics scope review has been submitted and remains pending.