Send mail to the author(s) E-mail

View Richard Soeteman's profile on LinkedIn

RSS 2.0 | Atom 1.0 | CDF




The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

Sign In


# Friday, 26 March 2010
Friday, 26 March 2010 22:53:02 (GMT Standard Time, UTC+00:00) ( SiteAnalyzer | Umbraco )

This Blog is not active anymore, further posts will be available on my company website. Read new posts here

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  “” 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 “” to “” 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 in Q2,  before Codegarden. The first preview will focus on the Standard functionality.

The next blogpost will describe the architecture of this package.

Friday, 26 March 2010 23:03:15 (GMT Standard Time, UTC+00:00)
This looks really useful! I look forward to seeing this in action, and I am sure that there will be some demos at CG10 :)
Wednesday, 31 March 2010 19:44:48 (GMT Daylight Time, UTC+01:00)
If it's anywhere near as useful as the CMSImport package, which it potentially is, I look forward to this. Count me in for beta testing if required ;) One initial comment I would have is allowing the user to preview any changes before they are made in case any 'autofix' is not the desired solution.
Wednesday, 31 March 2010 20:12:01 (GMT Daylight Time, UTC+01:00)
Hi Peter and Simon,

Thanks for your comments I will unofficial demo this during CG10. It's a technique I'm thinking about for several years. Since SEO is important these days I think it's profitable to build a package for this. Regarding autofix, nice suggestion. I was thinking about the option to configure autofix, but a preview is also a great idea. Thanks for sharing that idea.

Comments are closed.