We have 2 Load Balanced servers (A and B) using CMS 2001. We moved away from Web Indexing for searches and use 2 external 2 load balanced Google hardware devices (1 and 2). CMS 2001 is set up using Hierarchy-based URLs so we thought we'd be fine for search results integrated into our web site. In the past, when a load balancer passed a user to CMS Server A and made a search for let say sample.pdf, Web Indexing on Server A provided the results www.mywebpage.com/News/pdf/abdc_123_sample.pdf. You would hit the search link result and get the file. No problem. Now having an external search engine device, the external search engine devices would web crawl www.mywebpage.com and either hit CMS Web Serve A or B. Remember the web site is load balanced, so web crawl gets randomly sent to CMS Server A or B. We didn't think this was an issue until we noticed that if we hit CMS Web Server A and did a search for "sample.pdf" we would get mixed search results maybe hitting CMS Web Server B content, therefore giving a URL link like www.mywebpage.com/News/pdf/abdc_xyz_sample.pdf and not www.mywebpage.com/News/pdf/abdc_123_sample.pdf When the user on CMS Web Server A would hit the resulting web crawl link found on CMS Web Server B with www.mywebpage.com/News/pdf/abdc_xyz_sample.pdf, we would get an Error Page with "Page Not Found" from Server A. I think that when CMS Web Server A or B did Web Indexing in the past, it would find it's own CMS content while the user attached to it's session did the search. When using external search engines that crawl www.mywebpage.com on sites that are CMS Web Server load balanced, there is a disconnect, and correct content links will only resolve if your on Server A, where Search Engine Device 1 provides results pointing to content distributed by CMS Web Server A. Hope this doesn't sound confusing? Has anyone encountered such an issue when using external search engine devices using CMS 2001? Any work around when using external search engines versus Web Indexing? Thanks, Mark