Guide editorial and verification policy

These guides are designed to be checked. This page explains what qualifies as evidence, how claims are scoped, and how corrections are handled.

Published July 22, 2026.

Source hierarchy

Use legislation, standards, regulator material, and official product documentation for factual claims.
Use first-party announcements only for the product behavior they directly describe.
Label operational recommendations as guidance rather than turning them into legal requirements.
Exclude a claim when an authoritative source cannot verify it.
Link the source beside the relevant fact and list it again in the source section.

Tool-guide verification

Every tool guide must contain tool-specific facts that would not survive a name swap. Claims about seeds, history, job IDs, metadata, watermarking, retention, or exports require an official documentation URL. Pages are reviewed for duplicated language and thin templating before publication.

Interfaces and plans change. A visible updated date is changed only after a substantive review or correction, not automatically on every deployment. Readers should treat the linked vendor page as the current authority when a product has changed since the guide date.

Legal and provenance language

The guides do not provide legal advice and do not describe an internal template as a statutory form.
A record may support inclusion, integrity, and time claims when the corresponding evidence exists.
A declared reference does not prove that the reference caused particular output features.
C2PA, file hashes, timestamps, approvals, and workflow records are described as distinct evidence layers.
No structured-data property is added solely for search visibility when the same fact is absent from the visible page.

Search and AI accessibility

The guide library follows ordinary search fundamentals: public pages are crawlable, internally linked, represented in the XML sitemap, and written as visible HTML. Search and assistant crawlers are allowed on public pages while authentication, client, share, billing, and API paths remain disallowed.

The site also publishes llms.txt and llms-full.txt as machine-readable inventories. Those files are supplementary discovery aids, not a substitute for indexing, visible content, or the controls documented by individual crawler operators.

Corrections

Send a correction with the page URL, disputed sentence, and primary source to support@behindtheworkflow.ai. Confirmed factual errors are corrected in the visible article and its structured data. Material corrections update the page date; minor typography changes do not.

Sources

How guides are verified

Google Search Central: AI features and your website Google's current guidance on crawlability, visible text, internal links, and structured data for AI search features.

OpenAI crawler documentation The documented roles of OAI-SearchBot, GPTBot, and ChatGPT-User.

Anthropic crawler documentation The documented roles of ClaudeBot, Claude-User, and Claude-SearchBot.

Perplexity crawler documentation The documented search and user-fetch crawler tokens.

Bing Webmaster Tools: AI Performance Microsoft's citation and grounding-query reporting for AI search.

Related guides

What is an AI production log?

AI provenance: what you can prove and what you cannot

How to document AI-generated work for client delivery What broadcasters, platforms, agencies, and rights offices already require when AI is part of delivered work, and the per-shot checklist that answers all of them.

EU AI Act Article 50 for creative teams What the transparency obligations for AI-generated and AI-manipulated content actually say, the real timeline and penalty ceiling, and what a team should record to be ready.

Prompt and model documentation: a practical checklist for studios The fields worth capturing for every generation: prompts, models, versions, settings, references, and edits, and how to keep the habit alive in production.

C2PA vs. AI workflow documentation C2PA and AI workflow documentation solve different parts of the provenance problem. C2PA protects signed assertions attached to media; workflow records preserve prompts, sources, decisions, rights, versions, and approvals around the file.

AI shot log template for image and video production A practical AI shot log template for prompts, models, references, versions, human edits, disclosure, and approval. Download the CSV and adapt the field guide to your production workflow.

How to record client approval for AI-generated work A client approval record for AI-generated work should identify the exact version, disclosed AI use, review scope, requested changes, approver, and time. This guide turns sign-off into evidence instead of an ambiguous email.

Every requirement in this guide is answered from a record kept while the work happens. BTW keeps that record for you.

Start your own record