From a7307815a7b628f58ae61ab3dc95ff7131001de6 Mon Sep 17 00:00:00 2001 From: Sylvain Pace Date: Thu, 7 Jun 2018 19:26:40 +0200 Subject: [PATCH] Doc/update content update content (#354) * integrate previous work enhance tyle/content reformat part 1 wait for review * adance start_urls * enhance attributes description * fix typo * proofread documentation/docsearch * add apiKey mention intefrate review and small fixes finished proofreading update sclient-rendering use unseen review * update README #269 * fix json * explain new parameter from algolia/docsearch-scraper#368 , solve algolia/docsearch-configs#321 * enhance as algolia/docsearch-configs#387 * updating flavicon * add FAQ section * made some text corrections * Update 1-customize-configuration-file.html.md.erb * fix bad anchor --- .../documentation/1-docsearch/3-recommendations.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/documentation/1-docsearch/3-recommendations.html.md.erb b/docs/source/documentation/1-docsearch/3-recommendations.html.md.erb index 43b6fee0..c45cfa30 100644 --- a/docs/source/documentation/1-docsearch/3-recommendations.html.md.erb +++ b/docs/source/documentation/1-docsearch/3-recommendations.html.md.erb @@ -86,7 +86,7 @@ this precise page will be scraped, crawled and so forth. This **de facto discovery** is really practical but not exhaustive enough. If for any reason, a webpage could not be referenced from another covered one, the scope of the search will be imperfect. -For those reasons we highly recommend that you use a **Sitemap** (#). +For those reasons we highly recommend that you use a [**Sitemap**](#https://www.sitemaps.org/). This lists every page of your web site and will be used as the **main source of truth** and it will define the roadmap of our scraping. Beside this exhaustivity, using a sitemap introduces a significant performance improvement for our scraper.