DRAFT — preview. GTMRun is in preview: the check below is real, sign-in is invite-only and prices are not decided yet.
GTMRun

For founders who market their own product

The week's marketing work, drafted and ready to approve.

Start with a free check of your site against Google's own guidance: email authentication, HTTPS, crawl files, soft 404s, conversion basics. Every finding links to a fix guide. Then let GTMRun draft the fixes, the posts and the replies — you approve, it ships.

Free · no sign-up · about 20 seconds · results stay 90 days. Also an MCP tool for agents.

gtmrun.co12 of 13 measured checks pass
  • PassSPF, DKIM and DMARC published for the sending domain
  • PassHTTPS, redirect, real robots.txt and sitemap
  • FixHSTS header missing — guide: one CloudFront setting
  • FixMissing pages answer 200 (soft 404s) — guide: real 404.html
  • FixNo canonical URL — measured on the rendered page by serp
  • Not measuredPricing page, call to action, analytics: the raw HTML is an app shell
The real result of checking the legacy gtmrun.co on 2026-11-12 — including the three things it got wrong. How scoring works.

What you get

Three kinds of cards, every week. You approve; GTMRun does the work.

The check is live today. The cards are the product behind "Get the fixes drafted" and arrive with the next milestone — this page says so plainly rather than selling them early.

Fix

Findings become fixes you can read before you apply.

  • Measured, never guessed. Every row is pass, fail or not measured. There is no AI score that moves between runs.
  • A guide for every check. What it is, why it matters, exactly how we check it, how to fix it on your host, and the Google documentation behind it.
  • Re-check in seconds. After a fix, the deterministic re-check confirms the row flipped — no third-party calls, no waiting.
Fix · HSTS header missing · 2 pts · GTMRun heuristic
How we check it  HEAD https://acme.com → Strict-Transport-Security
How to fix       CloudFront → Response headers policy →
                 SecurityHeadersPolicy (managed) — one setting
Verify           curl -sI https://acme.com | grep -i strict
Re-check → pass

Write

Posts drafted from what only you know, delivered as pull requests.

  • First-hand or not at all. A draft is built on a real product detail, a real customer situation, your position or your own data — or it asks you a question instead of writing filler.
  • No word-count targets, no keyword pages. Google's guidance is the rule: people-first content, one page per real reader need.
  • A pull request to your own site. Your blog stays on your domain and in your repo; GTMRun opens the PR, you merge.
Write · "What 40 soft-404 sites had in common"
First-hand   original_data — our own check results, this week
Opens        the answer in two paragraphs, then the evidence
Delivery     PR #12 → acme/site: content/posts/soft-404s.md
Approve → PR opened   Request changes → asks you first

Show up

Replies drafted where your buyers already ask — you post them.

  • You are always the one speaking. GTMRun drafts a helpful answer with a link only where it genuinely helps; you read it, edit it, post it from your own account.
  • Never cold outreach, never scraped leads. Those were parked for good. Honest daily reps compound; growth hacks decay.
  • A weekly recap of what shipped and what changed in your checks — one e-mail, only if you want it.
Show up · thread: "how do I stop my cold emails landing in spam?"
Draft   Check SPF, DKIM and DMARC first — Gmail requires SPF or
        DKIM on every message. Free check with the exact records: …
Where   r/startups · posted by you, from your account
Approve → copied to clipboard

How it works

Check. Approve. Ship.

  1. 01

    Check

    Paste your address. In about 20 seconds you get every finding with its guide: DNS, HTTP and HTML facts, plus a rendered-page audit, an image budget and link-graph authority from our own tools — each labelled with its source.

  2. 02

    Approve

    Sign in and GTMRun turns the findings into the week's cards: fixes to apply, posts to publish, replies to post. Each one is a draft until you say so. Sign-in is invite-only during the preview.

  3. 03

    Ship

    Approved fixes and posts land as pull requests to your repo; replies go out from your account. Re-check any time and watch the rows flip.

Pricing

The check is free. The work is free while in preview.

Prices are not decided yet: the cost of drafting a post is being measured on real brands first. Invited accounts get the week's cards for one brand at no charge; when prices are set they will be per brand, per month, as a subscription through Stripe as merchant of record — and nobody is charged without saying yes.

Check

$0/ forever

  • The GTM check with every finding and its guide
  • Deterministic re-check after a fix
  • MCP tool for agents and a GitHub Action for your deploys
  • About 12 checks per hour per network
Check my site

More brands

TBDper additional brand

  • Same as Brand, per additional site
  • One sign-in, one recap per brand
  • Agencies: ask about pooled brands
Contact

Draft. Nothing is for sale during the preview and accounts are invite-only. The full note is on the pricing page; what changed and when is in the changelog.

FAQ

Questions, answered.

Is there an AI score?

No. Every row is measured or not measured. The old GTMRun scan had a 68-point AI assessment that scored the same site 8 and 16 one minute apart; a number that moves on its own cannot tell you whether a fix worked. AI drafts the work; it does not grade you. Why there is no AI score.

What does "not measured" mean?

We could not tell, so the row earns no points and is not counted as a failure. Usual causes: your HTML is a JavaScript app shell, your host answers 200 for every address, a DNS lookup failed, or one of our tools did not answer in time. The guide for each row says how to verify it yourself. Details.

Where do the measurements come from?

Most are GTMRun's own: DNS over HTTPS, raw HTTP responses and your homepage HTML. Three rows come from portfolio tools and are labelled on the result: serp's rendered-page audit (canonical, one H1, image alt text), serp's link-graph authority (Common Crawl; third-party, not a Google signal) and image-optimizer's image budget. Rows measured by other tools.

Do you do SEO tricks, llms.txt, or "GEO"?

No. Google's published guidance is canonical for everything we check and recommend. Google says it ignores llms.txt, chunking and AI-specific rewrites, and treats bought links as spam, so we do not check for them, recommend them or sell them. What we don't check, with Google's words.

Can my agent use this?

Yes. The check is a keyless remote MCP server at /mcp with three tools: gtm_check, gtm_recheck and gtm_check_result. Plain HTTP works too (POST /api/check). A GitHub Action in the repository runs the check after a deploy and fails on the rows you choose.

What do you store?

The address you check and the public facts we observe about it, at its result link, for 90 days. A salted hash of your network address for one hour, to limit free checks. No e-mail, no account, no cookies for the check.

Twenty seconds to see what to fix.

Free, no sign-up, every finding with a guide. Then decide whether you want the work drafted.

Check my site