![]() ![]() There isn’t a common standard, so we have utilised customer provided JSON formats, and provided support for as many as possible. In version 3.0, we provided support for log files in JSON format. This is available in the ‘new’ project configuration and is particularly useful when you have known parameters or issues, and need to consolidate data. You’re now able to supply a list of parameters to strip from URLs and consolidate when you import log files. ![]() The updated Chrome versions, are the Googlebot which renders the page. Chrome 41 represents the Googlebot that makes the initial HTTP request to fetch the HTML of a page. In reality, Google are still going to be crawling with their old Chrome 41 user-agent as discussed here. The default user-agent wildcard matching for Googlebot and Bingbot has also been updated to improve tracking of their ‘evergreen’ version naming. You can choose from our pre-defined list of common search engine bots, or configure your own. This makes it far more flexible, particularly when user-agents strings change regularly, such as the new evergreen Googlebot and Bingbot. You’re now able to use wildcard matching when configuring user-agents you wish to import into a project. While everyone has more important things on their minds at this time, this small release includes limited, but essential updates that will help improve tracking of evergreen Googlebot and Bingbot and more. If you’re not already familiar with the Log File Analyser tool, it allows you to upload your server log files, verify search engine bots, and get valuable insight into search bot behavior when crawling your website. ![]() I am pleased to announce the release of the Screaming Frog Log File Analyser 4.0, codenamed ‘Stay At Home’. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |