v1.5.0 - your site's own Google, its real launch date, and self-host stops getting stuck

Rank checks and keyword research now run in your site's own country and language instead of always asking US Google, DispatchSEO works out when your site really launched instead of assuming it was born at signup, and self-host can finally change which repo a project publishes to.

Full notes: https://dispatchseo.com/changelog#v-1.5.0

New

• Search market setting (Settings > Project, or set_market): rank checks and keyword research target your real country and language, 14 markets. Research used to query the US market no matter what.
• Real launch-date detection: checks Search Console history and the Wayback Machine's first capture, automatically or via the Detect button / detect_site_launch. Drives the Journey timeline, publishing pace and how ambitious research is allowed to be.

Improved

• The dashboard says when it's waiting on you: unmerged install PR banner, and a "building now" badge that shows elapsed time and admits when a build stalled.
• Adding a second site on self-host shows the "setting up" banner with honest wording and follows the install live.
• WordPress / GitHub-repo requirement is stated up front on the landing page, FAQ and signup notice.
• Weekly scans name the fix when a Claude account itself is the problem (usage limit, subscription blocked).
• One broken credential emails you once, then waits three days before reminding you.
• Cursor gets its own dispatcher color (lavender).

Fixed

• Self-host can change which GitHub repo a project publishes to (Settings field + set_github_repo); the install playbook walks the agent through reconnecting.
• A lapsed plan really stops: the site's own GitHub workflows stand down instead of building, merging and alerting on a pipeline nobody pays for.
• Free (GSC-only) projects no longer show the "Running your first ranking checks" banner forever.
• Cursor audit: the step writing Cursor's MCP credentials was a no-op and a quoting slip would have crashed the failure classifier; every shipped workflow script is now bash-parsed as a release gate.

Since 1.2.0 the builders also run on Cursor end to end, and published pages stuck at position 5-20 get refreshed automatically instead of only ever publishing new ones.