Release Notes for version 1.7.1.4

Product release notes detail every single modification made on the release. Find out what changed with Visual SEO Studio version 1.7.1.4

Visual SEO Studio 1.7.1.4

Published: Thursday, December 7, 2017

Release 1.7.1 is a maintenance release mostly fixing a few issues introduced with the new major feature Links Inspector, introduced with Visual SEO Studio 1.7

Usability/UX:

  • Pro Trial expired dialog, cancel button text colour made more readable.
  • Upgrade to Professional dialog, cancel button text colour made more readable.

Various:

  • Google Search Console "Search Analytics" integration dialog: we restored displaying property sets. We did hide them with 1.7.0 as they have a cryptic name making a poor user experience, yet as soon as we did users pointed out they are too useful to get rid of them (e.g. they are useful in the transition period of an HTTP-HTTPS migration, when protocol URLs are indexed). In the future we might display them only optionally.

Fixes:

  • Fixed real-world crash occasionally occurring when an crawl started. This is a regression introduced with 1.7.0 by an optimization. We couldn't reproduce it, but on some clients' machines evidently occurred.
  • Fixed crash condition occurring to some users when opening the "Crawl URL List" window. We are not sure about what triggered the crash (we were not able to replicate the issue), but this fixes it.
  • Links Inspector: in case of destination non-explored (e.g. due to a timeout), calculated values "Destination receives PR" and "Destination wastes PR" were not processed correctly.
  • Links Inspector: in case of destination page blocked by robots.txt, calculated values "Destination receives PR" and "Destination wastes PR" were not processed correctly.
  • Links Inspector, calculated value "Destination wastes PR": while the business logic computed the field using the (here simplified) rule "(noindex AND nofollow)", the user interface treated it as it was "(noindex OR nofollow)". We decided to make it behave like the latter "(noindex OR nofollow)" because it helps to point out "half wastes", e.g. when destination is "noindex, follow" (half waste: it passes received PR internally, but doesn't use it to position itself) or it is "index, nofollow" (half waste: it uses received PR to position itself, but doesn't pass it internally).
  • Links Inspector, links by "anchor-text" tree: the treeview showed Source URL (already shown under the grouped item) instead of the Destination URL.