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 ->

Per-site XML sitemap for tool pages

SEOGrove generates a Sitemap Protocol XML file for all published tools on your site. Reference it from your main sitemap or submit it directly to Google Search Console so crawlers discover new tool pages immediately.

Sitemap endpoint

GET /sites/your-site.com/tools/sitemap

Available from your site's Tools builder panel as "Sitemap XML". Requires authentication. Reference the absolute URL from your main sitemap as a <sitemap> entry.

Example XML

sitemap.xml

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:image="http://www.google.com/schemas/sitemap-image/1.1">
  <url>
    <loc>https://your-site.com/tools/roi-calculator</loc>
    <lastmod>2026-05-12</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
    <image:image>
      <image:loc>https://cdn.example.com/featured.webp</image:loc>
      <image:title>ROI Calculator — Your Brand</image:title>
    </image:image>
  </url>
</urlset>

Each <url> entry uses your site's canonical path for the tool, the tool's last-published date as <lastmod>, and includes an image:image extension block when a featured image is attached.

Webhook delivery

The tools_index.updated webhook event also includes the full sitemap XML as sitemap.xml, alongside the tool catalog. This lets you update both the index page and your sitemap entry in a single webhook handler, without polling the sitemap endpoint.

tools_index.updated — sitemap fields

sitemap.xml	Full Sitemap Protocol XML string for all published tools. Write to a file or register with Google.
sitemap.tool_count	Number of `<url>` entries in the sitemap.
sitemap.generated_at	ISO 8601 timestamp when the sitemap was generated.

Tools index event

After every tool publish or deletion, SEOGrove sends a separate tools_index.updated event to the same webhook URL. This lets your CMS keep a /tools index page in sync without extra polling.

Event payload

Field	Description
event	`"tools_index.updated"`
timestamp	ISO 8601 delivery time
site.host	The site's domain
index.tools	Array of all currently published tools with slug, title, archetype, canonical_path, intro, cta, and meta fields
index.count	Total number of published tools
index.html	Complete standalone HTML page for a `/tools` index — self-contained, no JS dependencies

Recommended integration

Listen for tools_index.updated alongside tool.published.
On receipt, upsert your /tools index page using index.html or build from index.tools.
On tool.deleted, SEOGrove automatically re-fires tools_index.updated with the updated catalog — no manual pruning needed.

You can also preview the current index page at any time from your site's Tools builder panel, without waiting for a publish event.

Rebuild existing tools

Every generated tool has a Rebuild tool copy panel on its review page. Rebuilds re-generate the title, intro, field labels, SEO metadata, and CTA using the latest AI models — while preserving the slug, archetype, and all run analytics.

Rebuilds are free — they don't consume your monthly tool generation quota.
You can supply optional instructions (e.g. "make the intro shorter") or leave them blank for an automatic improvement pass.
After a rebuild the tool returns to review status — re-publish when you're happy with the new copy.
The rebuild count and timestamp are stored in the tool's metadata for your records.