Static SoundCloud Website Hub

QA page index — frozen backups of SoundCloud marketing sites. Open a link and compare it to the same page on live Webflow.

Production environment — static snapshots that will serve live traffic after cutover. Use Staging for QA, not this host.

Staging: links should behave like production URLs. Partner pages open at the site root (e.g. /ade/).

Staging: Community links open at production-shaped paths (e.g. /company/home/) via a hub script that strips /community/. Stories use /stories/….

Production: at cutover, partner pages serve on partner.soundcloud.com/{slug}/; Community marketing pages on soundcloud.com vanity paths (e.g. /company/…, /getstarted/…, /topic/…); Stories on soundcloud.com/stories/…. There is no live /community/ proxy — soundcloud.com/community is a user profile. On this martech host, /partner/, /community/, and /stories/ are QA prefixes to reach S3.

Partners — live site: partner.soundcloud.com

Marketing and partner campaign pages. Each link below opens the static backup at the same path as production (e.g. /ade/ → compare to partner.soundcloud.com/ade/).

Partner campaign pages. Links below use /partner/ on this host; live partner.soundcloud.com/{slug}/ will serve the same snapshot at cutover.

Community — live site: soundcloud.com (company, get started, topics, etc.)

Links below use the martech /community/ prefix in HTML. On soundcloud-stage.com, a script rewrites them to production paths (e.g. /company/home/) — not soundcloud.com/community, which is a user handle.

Community marketing pages. Live cutover: soundcloud.com/company/…, soundcloud.com/getstarted/…, and similar vanity paths — not soundcloud.com/community (user handle). Links here use /community/ to reach the S3 folder.

Stories / Editorial — live site: soundcloud.com/stories

Blog posts, tags, and editorial landing pages. /stories/… on this host = soundcloud.com/stories/… on live.

Stories pages. Links use /stories/ here; live soundcloud.com/stories/{path}/ will map at cutover.