> For the complete documentation index, see [llms.txt](https://documentation.pushly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pushly.com/platform/notifications/landing-url-validation.md).

# Landing URL Validation

### Landing URL Validation

The **Landing URL Validation** setting adds an automated health check to the notification save flow. When a notification is saved, Pushly verifies that the Landing URL returns a healthy response before delivery — helping you catch broken or misconfigured URLs before they reach your subscribers.

The check is **advisory, not a hard gate**. If a problem is detected, you are warned before sending but can always choose to proceed.

#### How It Works

When a notification is saved or scheduled, Pushly performs a server-side request against the Landing URL and checks the HTTP response.

If the URL returns a non-200 response, a warning step is added to the **Delivery Confirmations** modal before the notification is sent. The warning includes:

* The specific HTTP status code returned (e.g., **404**)
* A clickable link to the Landing URL so you can verify it directly
* The final destination URL, if the original URL redirected

You can acknowledge the warning and proceed with sending — the check is non-blocking and advisory only.

<figure><img src="/files/JBnEpR2quGYj3fhN8Gl7" alt=""><figcaption></figcaption></figure>

#### Validation Scenarios

The following conditions will trigger a warning:

* **Non-200 HTTP responses** — for example, 404 Not Found or 500 Server Error
* **Unreachable URLs** — DNS failures, connection timeouts, or SSL errors
* **Malformed protocols** — for example, `http:/example.com` instead of `https://example.com`

If a URL uses a short link or redirect, the redirect chain is followed to its final destination, and that destination is validated.

#### Enabling Landing URL Validation

Landing URL Validation is **disabled by default** for all domains. It can be enabled per-domain.

1. Navigate to **Domain Settings → Notifications → General Settings**.
2. Click **Edit** and open the **Delivery** section.
3. Toggle the **Landing URL Validation** switch on.
4. Save your changes.

The current status (**Enabled** or **Disabled**) is shown in the Delivery section of the General Settings well.

#### Benefits

* Catch broken Landing URLs before notifications reach subscribers
* Receive clear, actionable warnings with direct links to verify the URL
* Stay in control — the check is non-blocking, so you decide whether to proceed
* Opt out per domain in cases where the check produces false positives
* Validate short links and redirects correctly, since redirect chains are followed to their final destination


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.pushly.com/platform/notifications/landing-url-validation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.