Add and organize URLs manually

A specific page is managed as its own source

The “Web page” type suits an important URL missing from a crawl, a situation where the whole domain should not be analyzed, or a few policies that need independent management. Each record has its own title, URL, active status and training.

There is no bulk URL field guaranteeing unlimited processing. Add coherent pages, respect the plan resource limit and wait for processing before concluding they are ignored.

Good use case
A manual URL is ideal for a return policy, pricing page or stable service page whose activation you want to control precisely.

Select pages that provide facts

Before adding, open each URL without an administrator session and check what a visitor can actually read.

• Stable information

  Prefer specifications, public prices, procedures, published lead times, terms and contact details. An expired event page may continue influencing answers while active.

• Content visible in HTML

  If text appears only after login, in a video or in an unrendered JavaScript component, import an authorized document or pasted text instead.

• No secret

  Do not add signed links, invoices, customer areas or temporary URLs. A knowledge source is not a private document vault.

Create and name the source

Under Knowledge base, choose Web page. The title is used for internal management and the URL for retrieval.

1. Useful title

   Use “France returns — 2026” rather than “Page 1”. Add language, market or version when they change the rule.

2. Final HTTP or HTTPS URL

   Paste the canonical address without advertising parameters. An invalid URL is rejected before saving; an inaccessible page may fail later during training.

3. Train now

   Keep the option selected to start immediately. When preparing several sources, save them and then use the bulk Train action.

Organize, activate and test

Bulk actions can train, activate, deactivate or delete selected sources.

1. Deactivate for comparison

   Deactivate an old version before activating its replacement to limit contradictions. Deletion is permanent; use it only when the source should no longer be retained.

2. Wait for final status

   A test run while queued proves nothing. Wait for indexing to complete, then ask a question whose answer appears explicitly and unambiguously on the page.

3. Spot contradictions

   Also test an old value. If it still appears, search for a crawled page, document or active text containing it before concluding there is an AI fault.

A manual URL is ready when…

Verify the source and the answer, not just the “saved” message.

• Unambiguous title — Your team immediately identifies language, subject and version.
• Active and processed status — The source is neither inactive, still queued nor failed.
• Faithful answer — The test returns the fact without mixing it with an obsolete policy.