Skip to main content
Support for Montlake SiteMapper

Support for Montlake SiteMapper

Search
Montlake Software Support
Montlake FindUnique
Montlake SiteMapper
Montlake SortIPs
Press Releases
  
Montlake Software Support > Montlake SiteMapper > Support for Montlake SiteMapper  

Montlake Software Support > Montlake SiteMapper > Support for Montlake SiteMapper
Support and details for this Windows application from Montlake Software International.

 Usage notes


For a file name, this refers to the name of both the text and also the XML files that will provide the mapping. Use something simple—you can always change it after it has been created. Examples are "FirstGov," "Marys site," "Company site," etc. No quotation marks.

Use the Set output file path... button to choose the folder on YOUR system where the text and XML files will be created.

When you enter the address to map, it's a good idea to end the entry with a '/' (unless you have specified a particular page).

If you find yourself involved in a mapping that is taking more time than you want to allow, simply click the Cancel button. At the earliest appropriate moment, the application will cease operation and gracefully exit.

 

 Announcements

Please report public web sites that fail mapping 
by Michael Robert BroschatNo presence information
 7/25/2009 9:30 AM
Use the email address (image) to tell us of any web site we can get to that fails to map with Montlake SiteMapper.
 
It has been amazing to see the different ways that sites around the world are constructed. Sometimes, these differences cause SiteMapper...
 

 Issues and feature requests

Use SHIFT+ENTER to open the menu (new window).
Description
Fixed error involving input data
The previous version (...2.2) expected a trailing '/' after each web site specification. Version 2.0.2.3 does not.
 
You should use the trailing '/', however, unless you are specifying a root site (http://www.some.com) or a particular page (http://www.some.com/page.html).
 
Send in notice of issues or feature requests
I'll add anything here that I feel is worth noting, including whether I have a chance of fixing the problem or adding the feature.
 

 Background notes


This project started so innocently. I had attempted to use a "commercial" indexing application on my web site, which resulted in a simulated Syn Flood attack on my site. That got me wondering just how hard it is to programmatically obtain the content of a web page, and I quickly found out it isn't difficult at all. So, what to do with the result?

Although I doubt my need for indexing (or, at least, to compete with the Big Boys out there), I have been curious about what pages are actually in my web site. And, of course, once you get to programming something, it becomes reason enough just to keep going. There were many, many issues, and it was (sometimes) fun solving them. Sometimes, simply no fun at all.

Once I had my four test sites successfully mapping (during which I was introduced to non-standard HTML—my own!), I began to work through my bookmarked sites (where appropriate). It was fascinating to see that sites are often marked by particular styles of coding, some of which broke SiteMapper. For example, one woman is something of a neat freak, and insists on placing A (anchor) attributes on one line for each. This broke the regular expression evaluator, which doesn't tolerate line breaks. Some of my target sites are Microsoft SharePoint sites, and they required some special treatment. And other problems that have faded from memory (probably into nightmares).

I really haven't tried all that many sites, so do let me know if you find another that breaks the application.

 

 
 

 For support issues:

Email address for MSI

 Links

 Install Montlake SiteMapper
 Michael Broschat main site

 Features

Use SHIFT+ENTER to open the menu (new window).
Description
No limit in size
Actually, because SiteMapper works entirely within memory, there is certainly a limit to how many pages can be seen by the application. As of this writing, a site with 3,000 pages has been successfully mapped.
 
Rooted at first URL
The resulting site map can be started further down a site hierarchy than the root address, and the resulting site map will only include pages at the specified site and below.
 
Generates both text and XML site maps
At present, you don't get a choice. Specify a name (no file extension), which is used for both the TXT and the XML reports.