RankAscend

Deploy Hooks

RankAscend has a two-way deploy hook system. After publishing content, it can trigger a rebuild of your site. When that rebuild completes, your hosting provider can notify RankAscend so it automatically submits the new page to Google Search Console for fast indexing.

Neither hook is required, but together they close the loop from keyword to live-and-indexed page without any manual steps.

Outbound: trigger a redeploy

Configure an outbound hook at Settings → Integrations → Deploy Hook → Trigger a deploy.

Paste the deploy hook URL from your hosting provider. RankAscend sends an empty POST request to this URL immediately after every successful publish job.

  • Name
    Hook URL
    Type
    string
    Description

    The webhook URL provided by your hosting platform. RankAscend POSTs to this URL after every successful publish. The request body is empty, platforms use the request itself as the trigger signal.

If the POST to your hook URL fails, RankAscend logs a warning but does not fail the publish job. Content is already committed to GitHub, the hook failure only means the deploy trigger was missed for that publish.

You can test the hook at any time with the Trigger Deploy button in Settings. This fires an immediate POST without publishing any new content.

Getting your hook URL

Vercel

  1. Open your project → Settings → Git → Deploy Hooks
  2. Give the hook a name (e.g. RankAscend) and select a branch
  3. Click Create Hook and copy the URL

Netlify

  1. Open your site → Site configuration → Build & deploy → Build hooks
  2. Click Add build hook, name it, and select a branch
  3. Save and copy the URL

Cloudflare Pages

  1. Open your Pages project → Settings → Build & deployments → Deploy hooks
  2. Click Add deploy hook, name it, and copy the URL

What RankAscend sends

POST https://api.vercel.com/v1/integrations/deploy/...

# No body, no special headers.
# The POST itself triggers the build.

Inbound: deploy notifications

Configure an inbound hook at Settings → Integrations → Deploy Hook → Deploy notifications.

Your hosting provider calls RankAscend's webhook endpoint after a successful deploy. RankAscend then:

  1. Finds the most recently published content piece for your site
  2. Submits your sitemap to Google Search Console
  3. Notifies Google to crawl the new page directly

Inbound notifications require a connected Google Search Console integration. If GSC is not connected, RankAscend accepts the webhook (returning 200 OK) but skips the indexing steps silently.

Your webhook URL

RankAscend generates a unique webhook URL per site:

https://app.rankascend.online/api/webhooks/deploy-success/{siteId}

Copy this URL from Settings and paste it into your hosting provider.

Setting up the inbound hook

Netlify

  1. Site → Site configuration → Notifications → Emails and webhooks
  2. Click Add notification → HTTP POST request
  3. Set event to Deploy succeeded
  4. Paste your RankAscend webhook URL and save

Vercel (Pro/Enterprise only)

  1. Team Settings → Webhooks → Add
  2. Paste your webhook URL
  3. Enable the deployment.succeeded event
  4. Save

Cloudflare Pages

  1. Notifications → Destinations → Create (Webhooks)
  2. Name it and paste your webhook URL, save
  3. Notifications → Add notification
  4. Product: Pages, event: Deployment success
  5. Select your Pages project and the webhook destination

How automatic indexing works

When RankAscend receives a deploy notification it runs two GSC actions in sequence:

  • Name
    Sitemap submission
    Type
    automatic
    Description

    Submits your sitemap URL to the GSC Search Console API so Google re-crawls your full URL inventory.

  • Name
    URL inspection notify
    Type
    automatic
    Description

    Calls the GSC URL Inspection API for the most recently published page, asking Google to crawl that specific URL immediately. This is faster than waiting for a sitemap recrawl.

Both actions use the OAuth access token from your connected GSC account. Tokens refresh automatically.

Error handling

ScenarioWhat happens
Deploy hook POST failsWarning logged; publish job is still marked successful
GSC not connectedInbound webhook returns 200 OK; no indexing actions run
Sitemap submission failsWarning logged; URL notification still attempted
URL notification failsWarning logged; no user-visible error
Webhook fires for unknown site IDReturns 200 OK silently

RankAscend always returns 200 OK to inbound webhooks, regardless of outcome. This prevents your hosting provider from retrying indefinitely.

Was this page helpful?