# Deploy hooks and search engine pings

> Have Vercel, Netlify, Cloudflare, or your CI tell LopeBase when a deploy finishes, so GitHub posts go live in minutes and search engines hear at once.

Source: https://lopebase.com/docs/deploy-hooks
Updated: 2026-11-13
Open in the app: https://app.lopebase.com/content

When articles publish to a [GitHub repository](https://lopebase.com/docs/content#github), a post counts as published only once its change is merged and its page loads. LopeBase looks every hour. A deploy hook lets your host tell LopeBase the moment a deploy finishes, so the post is confirmed live within minutes. When a post goes live, by any path, LopeBase also tells search engines about it once.

## Create the deploy hook URL

1. **Open the destination settings:** Open **Grow** > **Content**, then the property's **Content settings**, and edit **Where articles go**. The deploy hook sits under the GitHub settings. [Open Content](https://app.lopebase.com/content)
2. **Create the URL:** Click **Create deploy hook URL** and copy it. The URL is the secret: anyone with it can ask LopeBase to check your site, so keep it out of public code. **Replace URL** makes a new one and stops the old one at once.
3. **Add it to your host:** Pick your host under the URL for its steps, which are also below.

A call is only a nudge. LopeBase does not take the host's word that the post is live: it loads each waiting post's page, as the hourly check does, and marks it published only when the page answers.

## Set it up on Vercel

Vercel sends webhooks from team settings, on the Pro and Enterprise plans.

1. **Create the webhook:** In Vercel, open your team's **Settings**, then **Webhooks**. Choose the **Deployment Succeeded** event and this site's project, and paste the deploy hook URL as the endpoint.
2. **Save the secret in LopeBase:** Vercel shows a secret once. Paste it under **Vercel webhook secret** and save. From then on LopeBase checks the `x-vercel-signature` on each call and refuses one that does not match.

LopeBase acts on production deployments only. Preview deployments, and events other than a success or a promotion, are answered and skipped. On the Hobby plan, which has no webhooks, use the [CI line](#ci) in a GitHub Actions workflow that runs on `deployment_status`.

## Set it up on Netlify

1. **Add a deploy notification:** In Netlify, open **Project configuration**, then **Notifications**, then **Deploy notifications**. Add an **HTTP POST request** for the **Deploy succeeded** event and paste the deploy hook URL.
2. **Sign it:** In LopeBase, click **Generate** next to **JWS secret token**, save it, and paste the same token in Netlify's JWS secret token field. LopeBase then checks the `X-Webhook-Signature` on each call.

Only a ready production deploy starts a check; deploy previews and branch deploys are skipped.

## Set it up on Cloudflare

**Cloudflare Pages** sends deploy events through Cloudflare Notifications, which can deliver to a webhook on every plan.

1. **Create a webhook destination:** In the Cloudflare dashboard, open **Notifications**, then **Destinations**, and create a webhook with the deploy hook URL. In LopeBase, click **Generate** next to **Webhook secret**, save it, and paste the same secret in Cloudflare. Cloudflare sends it in the `cf-webhook-auth` header of every call.
2. **Add the notification:** Add a notification for **Pages**, **Project updates**. Pick the project, the Production environment, and the Deployment success event, and send it to that webhook.

**Workers Builds** has no webhook of its own: its build events go to a Cloudflare Queue through event subscriptions. The simplest route is to add the [CI line](#ci) to the Worker's deploy command in **Settings** > **Build**, for example `npx wrangler deploy && curl -fsS -X POST `. Or subscribe a queue to the `build.succeeded` event and have its consumer Worker post the event to the deploy hook URL; LopeBase reads that event too.

## Call it from any CI

Add one step after your production deploy:

```
curl -fsS -X POST https://your-workspace.lopebase.com/api/content/deploy/...
```

Any POST works, with or without a body. Keep the URL in your CI's secrets. The call answers right away with `202` while LopeBase checks the waiting posts in the background, `200` with `skipped` when the call reports a preview or a failed deploy, and `404` for an unknown or replaced URL.

A plain call like this works only while no host signing secret is saved. Once you save a Vercel, Netlify, or Cloudflare secret, every call must be signed by that host, and an unsigned one gets `401`.

Calls are paced: a post is looked at once a minute at most however many calls arrive, and a burst of more than 20 calls in ten minutes can be refused with `429`.

## How search engines hear about a post

When an article goes live, through a deploy hook, the hourly check, or a destination that publishes at once (hosted, a webhook, a CMS), LopeBase tells search engines once:

- **IndexNow**, which Bing and other engines read, when the destination has an IndexNow key set. An EmDash blog pings IndexNow on its own.
- **Search Console sitemap resubmit**, when the property has a Search Console connection that may write. LopeBase resubmits the sitemaps Search Console already knows for the page's host, or `/sitemap.xml` when it knows none, so Google reads them again soon.

The article's page says what was sent and when, below its live address, and it is never sent twice for the same article. LopeBase does not use Google's Indexing API: Google allows it only for job postings and livestream pages.

> **Note:** Connect with Google asks only to read Search Console, so a property connected that way cannot resubmit sitemaps. LopeBase skips it and says so once, on the first article it skips. Submit your sitemap once in Search Console under **Sitemaps**; Google reads it again on its own. A Search Console connection made with a service account that has full access to the property can resubmit.

## Set it up with an agent

An agent connected to the [LopeBase MCP server](https://lopebase.com/docs/mcp-server) can do the same: `set_content_destination_secret` with kind `deploy_hook` makes or replaces the URL, kind `deploy_signing_secret` saves a host's signing secret, and `get_content_profile` shows the URL and each host's steps under `deploy_hook`. `get_article` shows what search engines were told under `search_engine_pings`.

## If something goes wrong

### My host called the deploy hook but the post still says publishing?

LopeBase loaded the post's page and it did not answer yet, or the pull request is not merged. Check that the page loads at your blog address plus the slug. The hourly check keeps looking, and after six hours a merged post is marked published with a warning.

### The deploy hook answers 401 signature does not match?

The signing secret saved in LopeBase is not the one your host signs with. Paste the host's secret again, or remove it in LopeBase to rely on the URL alone.

### The deploy hook answers 404?

The URL was replaced or mistyped. Copy it again from **Where articles go** in the property's Content settings.

### Why does the article say the sitemap was not submitted?

Either the property has no Search Console connection, the connection can only read, or the post's address is outside the Search Console property. IndexNow still goes out when a key is set.
