Repository navigation
Growth: detect stale live VPS acquisition pages every morning - #10
Merged
Merged
Conversation
8 of 17 tasks
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.
Why
The new app catalog, four SEO guides, support Play CTAs, and analytics were merged into GitHub but the apex appdevelopsk.com is served from a separate VPS, not GitHub main/Pages. Source-only QA passing can mask a broken acquisition launch for days. An actual live page check was required manually in issue #8.
Changes
scripts/check_app_discovery_live.shagainst the real production HTTPS origin, including homepage, catalog search, four guides, two enhanced support CTAs, unavailable Face Battle alternatives, robots and sitemap. Github's scheduler may delay execution.Release boundary: until an operator runs the already-provided VPS deployment, this new production smoke may intentionally fail. This does not prove installs; analyze post-deploy GA4->Play acquisitions with mature cohorts. No duplicate scheduled ChatGPT audit task is created.