Import your website into the knowledge base
Import your website into the knowledge base
To fill a knowledge base from your public website, you run the import wizard, check every proposal, and add only what you approve.
Who: an admin of the workspace. Permission: knowledge.manage.
Before you start
- You hold the
knowledge.managepermission. Without it, the import wizard does not open. - The workspace has a knowledge base. If it has none, the wizard shows This workspace has no knowledge base yet. and cannot start.
- The website belongs to your business and its pages are public. The wizard does not log in and does not send forms.
- You know the website address. The home page is enough, because the wizard reads the sitemap from there.
Steps
- Select Assistants > Knowledge > Import from a website. If you don’t see Import from a website, ask an admin to grant you
knowledge.manage. The wizard opens on the Site step and lists Previous imports. - In Website address, enter the address of your site, for example
https://example.com. The line Knowledge base it feeds shows which knowledge base receives the result. - Tick This website belongs to my business, and I allow it to be read. Then select Read the website. If the button stays disabled, fill in the address and tick the box. The wizard moves to the Discovery step.
- Wait while the status moves from Queued through Reading the sitemap, Reading the pages and Deciding what each page is to Ready. A counter shows how many pages are read. If you see Failed, the message that the website could not be read gives the reason.
- Read What this site is like and Found on your site. The first lists facts such as the sitemap, languages and contact details. The second lists broken links, other sites of yours that were not read, and pages the browser draws that came back empty.
- Open the Pages step. Each row shows the page, where it was found, What it is and Where it belongs. Where a page belongs is Knowledge base, Catalogue or Ignore.
- To disagree with a suggestion, change the choice in Where it belongs. Your choice shows as Your decision, and Use the suggestion hands the page back. Check pages marked Worth a look — we were not sure.
- Open the Proposals step and select Generate proposals. The status shows Writing the proposals and then Proposals ready. Each proposal sits under its page with Claims and where they come from, each claim beside the sentence of your site. Nothing is added yet.
- Open the Review step. For each proposal, select Approve, Edit or Leave out. In the edit form, Save and approve saves your correction and approves it. To act on several proposals, tick them or select Select all, then use the buttons that approve or leave out the selected proposals.
- If a proposal shows Price unclear or No price on the page, answer the question under it and select Send. A proposal with an open question cannot be approved until you answer or leave it out. Then open the Apply step and select the button that adds the approved proposals. The counts update.
Result
You can check the import in the Apply step. The counts Proposed, Approved, Left out, Applied and Failed show how each proposal ended.
Each applied document shows Added to the knowledge base with an Open link to the document in the knowledge base. A proposal that failed shows the reason instead, for example Another product already uses this code.
Limits
- The wizard reads only public pages. It obeys the site’s
robots.txtand reads at one request a second. - Pages that the browser draws on screen arrive empty, so nothing is read from them.
- Nothing reaches the knowledge base until you approve it and select the button that adds the approved proposals.
- Importing the same page again updates what was added.
- Gaps and inconsistencies the wizard flags, such as a missing or unclear price or a statement the page does not back, are for your business to fix. The wizard does not resolve them for you.
- The wizard routes each thing you sell to the catalogue, not the knowledge base. Prices live in the catalogue.
- Items for the catalogue are added only if you hold the
catalogue.managepermission when you apply. Documents never need it. - A product managed by a connected system cannot be changed by the import. The wizard shows This product is managed by a connected system, so it cannot be changed here.