Dashboard settings

Setting	What it is	Notes
Site address	Your public domain, as a bare host name	Published verbatim inside your structured data, so it is validated hard: a port, an @, an IP literal or anything that is not a host name is refused at the field rather than stored
Ownership	The verification token, and the check	Until it passes, every artifact endpoint returns 404. Changing your site address clears it — you re-verify on the new domain
Site key	hs_live_…, minted for you	Goes in GEOFFY_SITE_KEY. Public: it addresses content, it does not authorise anything
Revalidate secret	Minted by Geoffy; you copy it into your environment	Goes in GEOFFY_REVALIDATE_SECRET. Rotating shows you the new value once. We never send the secret itself — requests carry an HMAC of the body
Product URL patterns	How your product URLs are shaped, e.g. /products/:handle	Only for a site with no commerce platform. Geoffy proposes these from your sitemap; the captured segment becomes each product's handle

Two things there is no setting for

The revalidate URL is derived, not typed

Geoffy calls https://{your domain}/api/geoffy/revalidate, built from your verified domain. There is no field to fill in, and a route file at any other path is simply never called. Earlier documentation described a "Faster updates" URL field; it no longer exists.

There is no deploy hook, and no build-mode setting

A fully static site has no accelerated path: its content appears at its next build. That is the truth about a static site rather than something a build credential we hold on your behalf would change. Earlier documentation described a "How your pages are built" setting and a deploy-hook field; both were removed.

What the dashboard shows you

• Whether ownership is verified, and the exact URL the token must be served at.
• Whether the /apps/geoffy namespace is mounted, and if not, which of not_mounted, wrong_site or unreachable it is.
• Per product, whether it is confirmed on your live pages, and the pending reason if not.
• For a site with no commerce platform, the handle recorded for each crawled product and the canonical URL its page declared.

Which of these reach your code

Setting	Where it goes in an Astro app
Site key	GEOFFY_SITE_KEY, read as import.meta.env.GEOFFY_SITE_KEY and passed to every helper
Site address	Nothing in your code
Product URL patterns	Nothing in your code. They decide the handle you pass

The revalidate secret does not apply to Astro

It exists on every site, but only a Next.js app has a route to verify it with. Astro has no tag-based cache invalidation, so there is nothing to call — see how updates arrive. You can ignore that field.