First project

A project is a site: its production domain. Everything PostShip checks afterwards — pages, sitemap, certificate, forms — lives inside that project and must belong to that domain. This page takes you from creating the project to the first green check.

Create the project

1. From your projects list, click “New project”.
2. Give it a name (120 characters at most) and your site's production URL, in https:// — for instance https://acme.fr.
3. Confirm. The project exists, and PostShip pre-fills it right away (see below).

The URL must be public and https. PostShip refuses a local address, a private IP address or an http site: it can monitor nothing it can't reach from the Internet, and it only monitors encrypted sites.

What PostShip adds by itself

A new project isn't empty. From creation, PostShip:

• adds the home page as an HTTP check;
• looks for your pricing (/pricing, /tarifs, /prices) and login (/login, /signin, /auth/login) pages and adds them if they respond — that's the payment pages, with its own checks (the price displays, the login form is there);
• creates the site checks: indexability, AI visibility, security, accessibility, cookies, redirects, email, tags, weight, leaks, exposed files, certificates, third-party scripts. They don't count in your URL quota and only run on deploy.

What's added also depends on what you answered at sign-up: a showcase site without a checkout gets no checkout check. Everything can be corrected afterwards from the URLs page.

Add a URL

From Project → URLs → “Monitor…”, one question per screen:

1. What do you want to monitor? A page, the payment pages, a payment journey, an API, a form or a scheduled task.
2. The address. It must be on the project's domain or one of its subdomains — https://app.acme.fr/login passes for a https://acme.fr project, https://other-site.fr is refused. That's what prevents using PostShip as a scheduled HTTP client against a site you don't own.
3. For a page, what we check:

An API has its contract — the shape of the JSON — and a form its canary.

1. For “The page responds”, the “What we expect from the page” screen lets you change the expected status (200 by default), require or forbid a text (expected content) and send a secret header for a private page.
2. Click “Monitor this page”. The first check runs on the next pass; its result then shows on the URL's line.

The same “Monitor…” button also leads to the payment pages (pricing, login, checkout, in one go), to a scheduled task for a cron or a worker and — from the Pro plan — to a payment journey that chains several pages in order.

The URL quota

The quota is counted over all your projects together, not project by project: Discover 5 URLs, Pro 25, Pro Plus 100. The URLs page shows it under the title — “4/15 on your plan, all projects together”. A journey and a heartbeat each count as one URL; site checks don't count.

What's next

• Connect your host: without it, the site checks have no trigger and the checks only run on the cycle (every 5 min on Discover, 2 on Pro, 1 on Pro Plus, plus the Pro Plus 30-second probe).
• Choose where to be told: email is active by default.
• Read the vocabulary if the words “run”, “incident” or “Ship Score” mean nothing to you yet.

Troubleshooting

Why is adding a URL refused?

3 causes, with a distinct message for each: the URL isn't https, it isn't on the project's domain, or the plan's URL quota is reached. In the last case, the message offers a link to the plans; you can also disable a URL elsewhere to free a slot.

Why does my home page appear twice?

One line is the HTTP check, the other a site check set on the same origin (indexability, for instance). The filter by kind, at the top of the URLs page, tells them apart. Site checks are created by PostShip and take no slot in your quota.

Why is the first check in error?

An error isn't a failure: PostShip couldn't conclude. The URL's detail says why — 12-second timeout exceeded, redirect loop, address that doesn't resolve. Fix it, then “Check now” from the project bar.