Generated tool rendering contract

SEOGrove tools are generated as customer-domain pages. AI customizes copy, labels, metadata, and CTA text; executable behavior comes from a reviewed deterministic runtime.

Current runtime v3 Native first Iframe fallback available

Publishing model

Best

Native renderer

Render content.tool.native_html as trusted first-party HTML from the signed payload.

Advanced

Manifest component

Render content.tool.manifest in your own component or CMS block.

Fallback

Iframe

Use iframe_fallback only when the destination cannot run native assets.

Tool catalog

SEOGrove recommends deterministic archetypes from the site's market. SEO and GEO sites receive content brief, blog outline, LSI keyword, meta description, CTA, readability, snippet/schema, title, keyword density, robots.txt, and slug tools before generic lead-generation templates.

Tool payload fields

Tool payloads are delivered inside the normal webhook envelope as content.tool.

manifest	Portable JSON contract for title, fields, copy, CTA, theme, tracking URLs, and JSON-LD.
native_html	A complete native tool section with scoped CSS, manifest JSON, and deterministic runtime.
iframe_fallback	Compatibility embed for locked-down systems.
json_ld	WebApplication schema object for the published tool page.

Webhook receiver recommendation

Because webhook payloads are signed, a receiver can trust the native tool artifact after HMAC verification. Store the native artifact separately from the surrounding article copy so fallback blocks do not double-render. Runtime v3 renders text outputs in a larger scrollable panel with a built-in copy button for visitors.

Receiver rules

1. Verify X-SEOGrove-Signature against the raw request body.
2. Store content.tool.native_html from tool.published events.
3. Remove .seogrove-native-tool, .seogrove-tool-embed, style, and script nodes from copied body HTML.
4. Render the sanitized body copy.
5. Render native_html as trusted first-party HTML on the tool page.
6. Use iframe_fallback only when native assets are not allowed.

Fallback policy

Iframes are compatibility tools, not the default product experience. Use them for restrictive CMSs, temporary migration windows, or customer sites that cannot safely render signed native assets. For normal customer sites, publish a native page under the customer domain.

Read the webhook contract ->