Verify the result

Read a public page back as Markdown, check what a visitor will see, and confirm the page is actually published.

The page as text

curl https://anna-bakes.tapmy.link/page.md
# same thing:
curl "https://anna-bakes.tapmy.link/?format=md"
curl -H "Accept: text/markdown" https://anna-bakes.tapmy.link/

# Anna Bakes

Sourdough, croissants and Saturday markets in Lisbon.

- Address: https://anna-bakes.tapmy.link
- Template: Editorial · layout: list
- Language: en
- Photo: yes

## Blocks

1. **Order this week’s bread** — https://annabakes.example/order (featured)
2. Social row: Instagram <https://instagram.com/annabakes>, TikTok <https://tiktok.com/@annabakes>
3. Messenger button: whatsapp +351912345678 — "Ask about an order"
4. Heading: Where to find me
5. **Saturday market, Campo de Ourique** — https://maps.example/campo — _9:00–14:00_

_5 visible blocks. Rendered from the same data as the page itself._

This is produced from the same document the templates render, with the same rules: hidden blocks and blocks outside their date window are absent, adult destinations are withheld. If a block is missing here, it is missing on the page.

Is it published?

An unpublished page answers 404 on the subdomain and on page.md. GET /api/profiles/{id} with the key shows isPublished either way. POST /api/agent/pages publishes by default; set "publish": false to hand over a draft.

What to check before handing over

The name, bio and photo are the person's own words and picture, not placeholders.
Every URL opens — you sent it, you can fetch it. A dead link on a fresh page is the most common defect.
Adult links carry adult: true.
The socialRow uses real profile URLs, not the platform homepage.
The template suits the content (photos → photo/showcase; words → editorial/whisper).

The HTML

You can also fetch the page itself; it is server-rendered and readable without JavaScript. page.md is simply less to parse.