Coding, content and startups

James Crowley

Detecting 404 errors after a new site design

with one comment

We recently re-designed Developer Fusion and as part of that we needed to ensure that any external links were not broken in the process. In order to monitor this, we used the awesome LogParser tool. All you need to do is open up a command prompt, navigate to the directory with your web site’s log files in, and run a query like this:

"c:\program files (x86)\log parser 2.2\logparser" "SELECT top 500 cs-uri-stem,COUNT(*) as Computed FROM u_ex*.log WHERE sc-status=404 GROUP BY cs-uri-stem order by COUNT(*) as Computed desc" -rtp:-1 > topMissingUrls.txt

And you’ve got a text file with the top 500 requested URLs that are returning 404. Simple!

Written by james.crowley

February 18th, 2011 at 4:47 pm

Posted in ASP.NET,IIS

One Response to 'Detecting 404 errors after a new site design'

Subscribe to comments with RSS or TrackBack to 'Detecting 404 errors after a new site design'.

  1. I often use Xenu to crawl sites that are almost ready for production.
    http://home.snafu.de/tilman/xenulink.html

    http://

    18 Feb 11 at 8:36 pm

Leave a Reply