Sites a developer built

This section is for the developer of a site whose owner uses Joogoos. The owner sends you one message from the app (Business → SEO → A developer built it → Copy the steps for your developer). It holds two values:

Name	What it is
JOOGOOS_FEED_URL	The address of their feed: https://app.joogoos.com/feed/v1/sites/<id>.json. Not secret.
JOOGOOS_FEED_KEY	A secret starting jgf_ that only reads their published articles. Keep it out of the browser and out of git.

Joogoos gets no access to the site, its code, its repository or its host. Your site reads the articles; Joogoos may ring one address you give it.

How it works

Owner approves an article in Joogoos
        │
        ▼
Joogoos adds it to the feed ──── your site reads the feed (with the key)
        │                                   │
        └── rings your build hook ─────────►│ (if your site rebuilds to show new articles)
                                            ▼
                               the article is on your site
        │
Joogoos fetches its address after 5 and 15 minutes and says "Live"

Pick the way that fits the site

Recommended: read the articles when visited

If the site can run a small function or server code (Cloudflare Pages, Netlify or Vercel functions, any server), read the feed when the blog is visited and keep the last good copy. It needs one secret, no build hook and no rebuild, and a new article shows within minutes. See Server-rendered or Cloudflare Pages. Rebuilding on every publish (below) works too, but needs more settings and build minutes.

The site	New articles appear by	Build hook	Page
Built on Netlify	a rebuild	Netlify build hook	Netlify
Built on Vercel	a rebuild	Vercel deploy hook	Vercel
Cloudflare Pages connected to Git	a rebuild	Pages deploy hook	Cloudflare Pages
Built by GitHub Actions (or Cloudflare Pages uploaded from CI)	a workflow run	a small endpoint you add	GitHub Actions
Rendered on a server (Next.js server, PHP, Rails, a Worker)	reading the feed when visited	none	Server-rendered

Before anything is published

Add ?sample=1 to the feed address: the feed then holds one made-up article (frontmatter.sample is true) to build and style the blog with. Remove it before going live.

curl -H "Authorization: Bearer $JOOGOOS_FEED_KEY" "$JOOGOOS_FEED_URL?sample=1"

What to build, whatever the way

• A page per entry at its path: title as the H1, body (Markdown, from H2 down) under it, then faq, with description as the meta description and jsonLd as-is in one <script type="application/ld+json">.
• A blog index at the blog path (and per language prefix), newest first.
• Every entry in the sitemap; alternates as hreflang links.
• redirects answer 301; gone answers 410.

The full format is in the feed reference.

How the owner knows it works

The card Where they are published in their app turns green when either:

• a build hook is set (and the last ring was accepted), or
• the site has read the feed with the key in the last seven days (sites with no hook).