Method v1.0 ยท transparent boundaries
One observed run. One local SEO reading.
SEO Fanout does not recreate, repeat or imitate the upstream search. It reorganises only the selected query strings, source relationships and metadata already visible in one AI Fanout result.
What travels
- The original short question.
- Selected visible query strings.
- Provider and locale labels.
- Sources visibly attached at query, search-action or run scope.
- The observed-versus-modelled evidence state.
What never travels
- Provider keys, CAPTCHA tokens or hidden prompts.
- A final answer or chain of thought.
- Search volume, rankings or Search Console data.
- Local AI Fanout history beyond the selected visible run.
- A Crawl Foundry account or workspace identifier.
Browser contract
The result is carried in a URL fragment and removed immediately.
AI Fanout constructs a versioned, size-limited object in the browser. The object is encoded after the # in the SEO Fanout URL. Browsers do not send that fragment in the HTTP request or normal referrer. SEO Fanout validates it, keeps it in page memory for the current view and calls history.replaceState to remove it from the address bar. There is no second provider request and no server-side result store.
Deterministic research lenses
Visible wording patterns classify queries into comparison, cost, implementation, troubleshooting, definition, trust or open research. These labels are a review aid, not a model inference or verified search intent.
Source scope stays intact
A source is shown beside a query only when the transferred result contained that visible relationship. Shared search-action and run-level sources are not silently converted into exact query citations.
Stop rule
The research plan cannot decide what to publish.
A fanout observation can expose useful research branches. It cannot establish keyword demand, business relevance, existing site coverage, rankings or citation probability. Verify those separately before changing a website.
Open the research view