Generated tool rendering 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

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

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

The builder offers saved keywords from the selected site's keyword clusters and content plans, excluding off-topic clusters. If no keywords are saved yet, enter one yourself. The optional tool description is tailored to the selected site; leave it blank to design a tool from the keyword and site profile.

Custom tools (manifest v4)

A custom tool is built in stages: SEOGrove writes a specification with inputs, outputs, formulas and worked examples; a second, independent calculation re-checks the worked examples; then the tool's code is written and run in a headless browser, which must reproduce every worked example before the tool reaches your review queue. If any check fails after automatic retries, the generation fails and does not count against your quota. With Build tools automatically turned on, SEOGrove builds one custom tool a week for your best tool-intent keyword, within your plan's monthly tool allowance; each one still waits for your review.

Additional manifest fields

How the code runs

native_html runs program inside a hidden, sandboxed srcdoc iframe (sandbox="allow-scripts" with a default-src 'none' Content-Security-Policy). The tool's code cannot read your page, cookies or storage and cannot make network requests. The page and the sandbox exchange postMessage events; only declared AI steps are forwarded, by the page, to ai_url. If you render the manifest with your own component, run program with the same isolation.

AI steps

Most custom tools are pure calculations. Tools that write open-ended text (a personalised checklist, for example) call POST {ai_url}/{action} with { "inputs": { ... } } and receive { "result": { ... } } or { "error": "..." }. Requests are accepted from your site's domain, limited to 10 per minute per visitor, and capped per site each month by plan (Starter 300, Growth 1000, Pro 2000). When the cap is reached the tool shows a "try again later" message instead of failing silently.

Content-Security-Policy

Like every native tool, custom tools need inline scripts and styles allowed on the tool page. Tools with AI steps also need connect-src https://seogrove.io.

Page copy

Custom tools come with a full page: how to use the tool, how the result is calculated, a worked example and an ## FAQ section. In content.html the tool comes first and the copy follows.