Slope

Docs · Quickstart

From signup to first GitHub issue in 5 minutes.

The fastest path from zero to a Slope-shipped opportunity in your repo.

1. Sign up

Visit app.slope.to/signup and create an account with your email. You'll receive a verification code from noreply@slope.to — enter it to confirm. No card required.

On first sign-in, Slope auto-creates a personal organization for you and a default workspace called "Personal". You can rename either later from Settings.

2. Create your first project

Click Projects → New project. Enter the domain you want Slope to operate on (e.g. example.com). The project name defaults to your domain — you can edit it. Optionally add 1-5 competitor domains; Slope uses these for cluster comparisons and AI Visibility tracking.

3. Connect Google (GSC + GA4)

Go to Integrations. Click Connect Google. A single Google consent screen will ask for read access to both Search Console and Analytics. Click Allow.

Slope auto-matches the right Search Console site and GA4 property to your project's domain. If we can't unambiguously match (e.g. you have multiple GSC properties for the domain), a picker appears — choose the one you want.

A first sync job gets queued. Workers tick every 2 minutes, so first GSC data lands within 5 min.

4. Install the GitHub App

Still on the Integrations page, click Install GitHub App. You'll be redirected to GitHub. Choose the org and select either "All repositories" or a specific list. Install.

Slope receives an installation ID (not your personal access token) and stores it. From now on, when you push an opportunity, Slope mints a short-lived token (max 1 hour) for that specific install.

5. Wait for opportunities

After GSC + crawl sync, the opportunity detector runs. First opportunities appear on the Opportunities page within 10-15 minutes of the first connect (assuming we have enough page data to detect against).

Don't want to wait? Go to the project detail page and click Sync now — it immediately enqueues a fresh GSC sync + crawl + detection pass.

6. Push your first issue

On the Opportunities page, find one that looks like a clear win (typically a low-CTR title rewrite is the easiest). Click it to see the evidence + recommended action. Click Approve → Push to GitHub. Pick the destination repo. Done.

You'll see the issue in your GitHub repo within seconds. The body contains the opportunity summary, evidence (page URL, current vs target CTR, last-28d clicks/impressions), and a bulleted recommended-actions list specific enough to ship.

What happens next

  • Your dev team (or your AI coding agent) implements the fix.
  • When the PR merges + the issue closes, Slope auto-marks the opportunity completed.
  • 14 days later, the impact worker queries GSC for clicks/impressions/position delta and writes the result back to the task.
  • You see the actual outcome on the Execution Tasks page.

Optional next steps