Open the website in Knowledge Base to see its status and which pages were read. Then find your case below.
Failed
Nothing was read. The message tells you why:
- "The site's robots.txt does not allow this page to be fetched." Your site asks crawlers to stay away. Allow
TideReplyBotin yourrobots.txt, or add the content as files or text entries. - "The page requires a login or blocks automated access." The page is behind a login, a password or a bot blocker. TideReply can only read public pages.
- "The page was not found." Check the address for typos and that the page is published.
- "This URL is not an HTML page." The address points to a file such as a PDF. Use Upload files instead.
- "The page had too little readable content to index." The page is mostly images or video. Add its information as a text entry.
Fix the cause and click Retry.
Warnings or missing pages
Warnings means the source is live, but some pages couldn't be read. Open the source to see which pages are missing or have little text. Common causes:
- The page builds its content with JavaScript. TideReply reads these on a best-effort basis. Add the important information as a text entry.
- The page is mostly images. Product grids and image banners have little text to learn from.
- The site is very large. TideReply reads up to 500 pages per site. Choose the pages that answer customer questions with Edit pages.
Discovery stopped early
On large sites you may see that discovery timed out. You can continue with the pages found so far, or try again with a lower Crawl Depth.
A page I wanted is unticked
Blog, news, press, legal pages and translated copies are unticked by default. Tick them in the page list (or later with Edit pages) if you want them included.
"You already have crawls in progress"
You can run up to 3 website reads at a time. Wait for one to finish, then try again.
Still stuck? Email support@tidereply.com with your website's address.