Build your agent
Import checker
When a document-like source is imported — pasted text, a Google Doc, a Notion page — Pitchbar runs an advisory check on it and shows a short summary of adjustments on the source row: suggestions that would make the document answer better. The checker never modifies the document, never blocks an import, and its findings are suggestions to review, not errors.
What it checks
| Finding | Why it matters |
|---|---|
| No headings | Long documents without headings chunk poorly — facts from different sections blur together in retrieval. Use a heading per section or product. |
| Prices found | Prices hardcoded in documents go stale the moment the shop changes. Refer to the product page instead; the crawler keeps that current. |
| Unfilled placeholders | [fill in]-style tokens left over from a template end up verbatim in answers. Bracket notation used consistently (3+ times) is recognised as intentional and not flagged. |
| Materials list doesn't sum | A composition list totalling e.g. 85% will be recited as if complete. The checker flags any 3+-percentage line summing outside 95–105%. |
| Encoding damage | Mojibake (é, €) from a bad copy-paste corrupts retrieval for every affected word. |
| Oversized sections | A single section far beyond the chunk budget fragments into pieces that lose their context. |
| Advisory (AI) | One model pass looks for internal contradictions, sections mixing multiple products, and unfinished sentences. Best-effort: if the model is unavailable, the deterministic findings above are still saved. |
Where the report lives
On the agent's Sources page, each checked source shows
either “Document check: no suggestions” or an expandable
“N suggestions to improve this document”. The report is stored
on the source (check_report + checked_at) and
refreshes on every re-import or reindex of the source.
Scope
Document-like sources only: pasted text, Google Docs and Notion pages. Crawled website pages are deliberately excluded — marketing copy plays by different rules than knowledge documents, and flagging every price on a product page would be noise. The check runs on the queue after indexing; it adds nothing to visitor response times.