Apart from developing client websites, writing a manual for CMSImport and developing CMSImport V1.1 I’ve started the development of SiteAnalyzer last week. In the coming blogposts about SiteAnalyzer I will describe the development process of this package.
What is SiteAnalyzer?
SiteAnalyzer is tool that checks published pages for broken links, broken images in both content and Templates/ XSLT/Usercontrols. In next versions of SiteAnalyzer it will check more and more. My goal is to check for every SEO rule which you can turn on/off. It will be using a plugin architecture so you can add custom rules. SiteAnalyzer will report back pages where the rules failed to validate, like the Link failed due a 404 etc.
Now I hear you think, “Tools like these already exist why develop your own?”". I have a few reasons for that, first I was not finished and second I think integrating such a tool into Umbraco is better so people can maintain their site through one interface instead of having a tool for everything. This is why the Google Analytics package for Umbraco is so popular.
Again I was not finished. The killer feature of SiteAnalyzer will be the auto repair functionality(only for content) . Best to explain by an example. Let’s say the content editor entered the url “www.umbraco.org” in the Rich Text editor. The validator will fail due a 404 page not found. The auto repair function will try to fix the url and in this example it will convert “www.umbraco.org” to “http://www.umbraco.org/” So instead of just reporting that a url failed to validate, it will report that it found a link that failed and repaired it for you, which saves you a few clicks.
Will SiteAnalyzer be open source?
No just as CMSImport SiteAnalyzer comes in two editions, standard (free) and a PRO commercial edition. The difference between standard and pro will be that the standard edition can handle only a certain amount of pages, the Pro version can be scheduled instead of manual start of the scan and the Pro version comes with advanced reporting which sends you a pdf after it executed.
When will we see a first release?
A first Preview release will be on our.umbraco.org in Q2, before Codegarden. The first preview will focus on the Standard functionality.
The next blogpost will describe the architecture of this package.