One of the core use cases for running site crawls on your site is to find, capture and highlight the issues found. These issues can then be worked on by your team and then the site is recrawled to confirm that the issue has been updated. Running this exercise on a recurring basis will keep your site errors in check, improve your search engine optimization and can help boost your rankings and conversion rate.

Most sites are being constantly worked on and updated by a large number of people. From content optimization to architecture changes, sites are being updated regularly. This could mean that the issues detected are also changing with each crawl that is run. Being able to view the html fragment that caused an issue to be triggered highlights the issue easily and brings transparency to the site audit process. 

For all crawls we now allow you to view the html fragment by clicking on the “eye” icon next to the issue in Site Health 3.0. This is available in the Details Tab, Canonical Audit Tab and the Hreflang Tab.