Free tools · AI search scoping builder

A plan sized to what your team can ship.

The AI search scoping builder turns eight answers about your site into a plan. You get what to do first, what comes next and what to skip, each item sized S, M or L.

Free · no address needed · the plan updates as you answer.

Eight questions

Your plan

Updates as you answer · effort S, M, L
  1. Factual consistencygate Do firstOne approved fact sheet, then the same numbers in every language versionS
  2. Crawlabilitygate SkipSkip the rendering project: your platform already serves HTML. Check robots.txt and CDN rules only
  3. Entity foundation Do firstAdd product entities: Product schema with identifiersM
  4. Page structure NextRework the top pages answer-first, two a monthM
  5. Corroboration NextIndependent reviews and retailer listings with the same specsM
  6. The loop Do firstRecord a baseline before changing anythingS

Content work runs on its own; engineering items wait for a contractor

What to skip

Every Skip is work your team gets back.

Two teams, two plans. A site with server-rendered pages skips the rendering project. A site that renders in the browser gets that project first, and a team that already measures skips the baseline.

Kestrel OutdoorCustom, server-rendered · Company only, not products · We’ve asked ChatGPT a few times

  1. Factual consistencygate Do firstOne approved fact sheet, then the same numbers in every language versionS
  2. Crawlabilitygate SkipSkip the rendering project: your platform already serves HTML. Check robots.txt and CDN rules only
  3. Entity foundation Do firstAdd product entities: Product schema with identifiersM
  4. Page structure NextRework the top pages answer-first, two a monthM
  5. Corroboration NextIndependent reviews and retailer listings with the same specsM
  6. The loop Do firstRecord a baseline before changing anythingS

Content work runs on its own; engineering items wait for a contractor

ClauseMindsCustom, rendered in the browser · Not that we know of · Yes, measured and recorded

  1. Factual consistencygate Do firstOne approved fact sheet: prices, specs and claims in one placeS
  2. Crawlabilitygate Do firstServer-render or pre-render the pages that carry your factsL
  3. Entity foundation Do firstCreate a Wikidata item, then Organization schema with sameAs linksM
  4. Page structure NextAnswer-first rework plus comparison pagesM
  5. Corroboration NextReviews on software directories and comparison mentionsM
  6. The loop SkipSkip the baseline: you have one. Re-measure monthly against the baseline

Crawlability and content can run side by side

From plan to backlog

Turn each line into a ticket your team can close.

Copy every line of the plan into your tracker as one ticket. Give each an owner, keep its S, M or L, and write down what done looks like. A Skip line becomes one quick check, not a project. Here is one plan as a backlog.

Do first3

  1. One approved fact sheet, then the same numbers in every language version

    MarketingSFactual consistency

    Done whenPrices, specs and claims match in every language version

  2. Add product entities: Product schema with identifiers

    ContractorMEntity foundation

    Done whenEvery product page carries Product JSON-LD with its identifiers

    Use the schema generator

  3. Record a baseline before changing anything

    MarketingSThe loop

    Done whenToday’s answers are measured and saved before any change ships

    Explore AI visibility

Next2

  1. Rework the top pages answer-first, two a month

    MarketingMPage structure

    Done whenEach reworked page passes the answer-first checks

    Use the website checker

  2. Independent reviews and retailer listings with the same specs

    MarketingMCorroboration

    Done whenThe reviews and listings that matter carry the fact-sheet specs

    Find the cited reviews

Skipbecomes one check1

  1. Rendering projectCheck robots.txt and CDN rules

    MarketingCrawlability

    Done whenEvery live and index crawler can fetch the site

    Use the AI crawler access checker

From one plan: content work runs on its own; engineering items wait for a contractor.

Why this order

Built from the bottom up.

Effort spent on a higher layer is wasted while a lower one is broken. Whatever you answer, the plan comes back in this order, with the two gates first.

Read the reasoning in the field guide
  1. Factual consistencyA gate

    One approved set of facts, because contradiction is the main cause of a model hedging about you.

  2. CrawlabilityA gate

    An engine can fetch and read the page. Nothing above this layer matters until crawling works.

  3. Entity foundation

    The model knows what you are, who makes you, and what you are not.

  4. Page structure

    Your facts get retrieved cleanly as passages an engine can quote.

  5. Corroboration

    Independent sources repeating the same category and the same numbers.

  6. The loop

    Measure, change, re-measure, and keep the facts current as they drift.

Start the first ticket with the right resource.

Every Do first ticket has a tool, a template or a measurement to start from.

  • Kestrel ranked 2nd to 3rd of 5 brands by how often answers name each, Alpenway first at 41%

    Record a baseline

    Measure how often AI tools name you today, before anything changes, and compare every later result against the baseline.

    Explore AI visibility & competitors

  • The templates pack

    The files the technical items in your plan ask for.

    Open the templates pack

  • The page checklist

    What “rework the top pages answer-first” means, check by check.

    Open the page checklist

  • The GEO Field Guide

    The reasoning behind every layer of the plan, explained in full.

    Read the field guide

More free tools.

All free tools
Website checkerScore how ready a page is to be cited, with the fixes that raise the score.Open the tool AI crawler access checkerFind out which AI crawlers can fetch your site, and what stops the rest.Open the tool Schema generatorTurn your page and product facts into JSON-LD, ready to paste and check.Open the tool

Questions, answered.

Something else on your mind? Contact us.

No. The plan sets priorities from your answers, and the order holds because each layer depends on the one below. For page-level findings, run the website checker on the pages that matter most.

Because skipped work is capacity your team gets back. A site that already serves HTML needs no rendering project, and a team with a recorded baseline needs no new one.

Because it is not shown to change citations. The file is cheap and harmless: publish one if it costs an hour, but never in place of robots.txt, structured data or crawlable HTML.

Yes. The plan updates the moment you change an answer. Rebuild the plan when your stack, publishing capacity or team changes.

No. The plan comes from a fixed rule table applied to your eight answers, in your browser. The field guide explains the same dependency order.

Want a second pair of eyes on the plan?

Send us your answers, and someone who has read them will reply about your stack and capacity. The plan is yours either way.

Check your website free Talk the plan through with us