You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 9, 2022. It is now read-only.
I've confirmed the lvl0 xpath works on those pages so am not sure what would have caused it to fail. Maybe your crawler searched cached pages that didn't have this selector available?
The text was updated successfully, but these errors were encountered:
Hi Tom,
Thank you for the feedback.
The crawler isn't using any cache. We are doing a total new crawling each 24h. I have checked it and it looks like this issue is solve.
This issue should be because of the time needed to have the crawling done.
Let us know if you need anything.
Yes, the issue appears to have resolved itself. What I meant by cache is that it could have been a problem with our site. Our Cloudfront cache (which we'll eventually disable) takes about 24 hrs to clear so it's possible the Algolia search script was seeing older versions of some of our pages.
Thank you for your help! We have a better understanding of how the search config works now.
For https://thumbprint.thumbtack.com our
lvl0
selector looks like:https://github.com/algolia/docsearch-configs/blob/master/configs/thumbprint.json
When I search for the page title "Using Thumbprint in Sass" — https://thumbprint.thumbtack.com/guide/creating-pages/ — the search result correctly categorizes it under "Guide".
But if I search for the pages titles of the following pages:
It categorizes them under "Documentation" instead of "Guide".
In this screenshot "https://thumbprint.thumbtack.com/guide/utility-classes/" is among the results, note that it's categorized under "Documentation"
I've confirmed the
lvl0
xpath works on those pages so am not sure what would have caused it to fail. Maybe your crawler searched cached pages that didn't have this selector available?The text was updated successfully, but these errors were encountered: