If the starting url has a path, and that path contains encoded characters (eg %20) and relative links on the page, then the crawl may not have proceeded past the first page. Small fix for a problem that will affect very few users, but will be a very important fix for those users.(Integrity Pro) Adds checkmark to the 'sort by' popup button above list of websites.(Integrity Pro) Fixes 'list' view of sitemap visualisation not appearing correctly when system in light mode.Fixes the issues with sorting some of the columns of the 'All links' table.When scanning locally (file://) and with the 'test anchors' setting switched on, could go into a loop.Rules > Consider http and https versions of the same url to be the same and Rules > Consider http pages external Now this behaves as expected according to the preference. Fixes bug that may have prevented pdfs from correctly being included in the sitemap if the preference was checked or caused them to be included even if the preference was unchecked. These will expand / collapse all items in the current view, if the view is expandable, eg by page, by status, Spelling by word. Adds Expand All and Collapse All to View menu with keyboard shortcuts, and buttons for those functions to the toolbar palette.Fixes a bug that caused 'urls' containing a bunch of javascript to appear as bad links under very specific and unlikely circumstances.Now the images are given the status "missing image src" so that they can be distinguished from missing link urls in the By Status and other views. Previously 'flag missing link url' would also pick up img tags with missing src, if image check was switched on, but would confusingly mark them with the status "missing link url". More clearly marks image tags with empty source.Fixes potential horizontal scroll issue in SEO>Summary.Fixes selected spellcheck language not being 'remembered' sometimes.Fixes some false results in the spellcheck, which were due to concatenation of words with certain settings and when certain html tags run together.Fixes a possible issue with character encoding.In other words if an instance has been discovered at that point which doesn't have the nofollow keyword in its rel, then the link will be followed. Now observes rel=nofollow in a link, if at the point the engine comes to follow that link, *all instances discovered so far* are marked 'rel=nofollow'.This does raise some questions and the matter is left open at this point. ie if it is internal according to its domain, integrity does not mark it as an external link or treat it as external, ie not following it. Despite collecting the data and possibly generating a warning, Integrity does not *observe* the rel=external at this point.This may be deliberate and is legal but there are serious SEO implications if it happens unintentionally.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |