Hi @jamiemccardle, @RahulPa - There are two things to consider: 1) We do not index special characters 2) Auto-Suggest and SERP search are slightly different. Every special character is considered as a whitespace and characters preceding and succeeding the special character are considered as two separate words.
Example: For Auto-suggest, in your query, the search will happen for words "awrrpt" and "sql...". So all the posts that have "awrrpt" and "sql" and words that begin with "sql" will be showcased. In your case, there is 1 result that you got. On SERP page, the search will happen for "awrrpt" AND/OR "sql". Here, the search results fetched would be more and will be ranked basis the frequency of the words in the post. Thus your relevant result went beyond the first page.
... View more
Sorry about the delay here. I would highly recommend filing a Support ticket. Like I mentioned earlier, sometimes, some bots do slip by the filter if they were developed in a way to not get detected as a bot but rather get detected as actual human users. The engineers used to make a change in the dictionary of the bot filter and add the information of such bots there so the filter can detect that specific bot in the future. But it is no longer the process now.
This was discussed with Engineering and as the process of manually adding the details of the bot is not really a solution but rather a temporary relief, the team no longer manually updates it. Instead, when you create a ticket with Support and let us know about such bots that have bypassed the filter, we record the data for case studies so that we can come up with a permanent solution to this which will require some extensive development work. I hope this helps.
Update ( @Wendy_S 😞
I was mistaken. I discussed this with Engineering again. We never actually made changes to the bot traffic in LSI by updating the DB to detect bots. Any metric that has been fetched by LSI once, will stay there for good. If you do come across suspicious traffic then you can file a support ticket and let us know about it. The Analytics team can provide you with details of where the bot traffic generated from (user agent details and IP address etc.) and you can block them from the community so no future traffic gets accepted from there.
... View more