The crawl engine is designed to scan all pages it can access and understand, however it is important to note that it doesn't have context of a page's purpose. So while a human would avoid clicking a Delete button, Sitemap Creator will, if it can.

Most websites are properly written, so the previously mentioned button is an actual BUTTON or INPUT element with a backing FORM. Sitemap Creator will ignore these; it doesn't submit forms it detects. This also applies if the "button" is a hyperlink with JavaScript events bound to it as Sitemap Creator cannot execute JavaScript. But if the button is a simple A pointing to delete.asp without a confirmation (or, with a confirmation that only exists as JavaScript on that A tag), then following the link could lead to data change or destruction.

For that reason it is not recommended to allow Sitemap Creator to crawl private areas of websites unless you have verified that it won't do any harm. And if you do find that your website is allowing for data changes via GET or HEAD requests - upgrade your software!

As a final point, question why you want to scan the private area - it is next to certain that any data management pages in the copy will no longer function or sitemap pages be accessible, so consider the benefit of making the copy or sitemap in the first place.


As per the license agreement, Sitemap Creator is provided "AS IS" and we are not responsible for how you use this software.

See Also

Configuring the Crawler

Working with local files

Controlling the crawl



Modifying URLs


Deprecated features

© 2010-2023 Cyotek Ltd. All Rights Reserved.
Documentation version 1.2 (buildref #81.15583), last modified 2023-04-09. Generated 2023-04-29 14:30 using Cyotek HelpWrite Professional version 6.19.1