Easy Search Documentation

EasySearch Pricing -- Product, Support, and Upgrades

Fri, 07 Aug 2009 07:57:22 GMT

EasySearch is not only easy to use (and fast to setup), it's very affordable. Anyone interested in adding a search engine to their ASP.NET application should not be hindered by price. The only difference between versions of EasySearch is the maximum number of pages the search engine will scan.

	EasySearch 200	EasySearch Pro
Limited Page Scans	Yes (200)	5000/15,000
License Price	Buy Now $99	Buy Now $249/499
Annual Support/Upgrades 1st Year Included
New... Live Hints Live hints dispalyed as search is being typed
Zero Coding Required Modify your Web.Config, then Simply Drag and Drop EasySearch Controls onto your ASPX page
Automated Crawler Simply Tell EasySearch Where to Start
Configurable User-Agent Give a custom name to the Crawler User-Agent
Configurable User Controls It's Easy to configure EasySearch to match your site
CSS Style Sheet Friendly
Save EasySearch To File Fast Startup Times Between Application Restarts
Search Multiple Domains
Access Search Reports What are your customers searching for?
Web Service Enabled Programmatic access to a WebService DataSet

Excluding Pages and Directories from Scanning and Search Results

Fri, 07 Aug 2009 07:53:03 GMT

The web.EasySearch.Config has four nodes to help you control certain pages and directories from being scanned, or being displayed in search results.

ExcludePageNamesFromResults
ExcludePageNamesFromScanning
ExcludeDirectoryNameFromResults
ExcludeDirectoryNameFromScanning

These nodes allow for certain file names and directory names (with all the files found in that directory) to be excluded from your search results and/or excluded from your scanning engine. It should be known that the XML nodes (inside the <> marks) are case sensitive, while the data (inside the >< marks) is not case sensitive. If you exclude <pageNameStartsWith> an S, all pages beginning with S or s will be excluded.

It will be also helpful to know that the values supplied to these nodes can be singular or comma seperated. In the below example, we're Excluding the page name "AllArticlePage" from the results, which is a singular exclusion. If you have to pages to exclude, you would set the value as "AllArticlePage,SecondPage,AnotherPage,WhateverPage".

1:     <ExcludePageNamesFromResults>

2:        <pageName>allarticlepage</pageName>

3:        <pageNameStartsWith></pageNameStartsWith>

4:        <pageNameEndsWith></pageNameEndsWith>

5:        <pageNameContains></pageNameContains>

6:     </ExcludePageNamesFromResults>

7:     

8:     <ExcludePageNamesFromScanning>

9:        <pageName>askquestion</pageName>

10:       <pageNameStartsWith></pageNameStartsWith>

11:       <pageNameEndsWith></pageNameEndsWith>

12:       <pageNameContains></pageNameContains>

13:    </ExcludePageNamesFromScanning>
14:     
15:     <ExcludeDirectoryNameFromResults>
16:        <directoryName>_includes</directoryName>

17:        <directoryNameStartsWith></directoryNameStartsWith>

18:        <directoryNameEndsWith></directoryNameEndsWith>

19:        <directoryNameContains></directoryNameContains>

20:     </ExcludeDirectoryNameFromResults>

21:     

22:     <ExcludeDirectoryNameFromScanning>

23:        <directoryName>askquestion</directoryName>

24:        <directoryNameStartsWith></directoryNameStartsWith>

25:        <directoryNameEndsWith></directoryNameEndsWith>
26:        <directoryNameContains></directoryNameContains>

27:    </ExcludeDirectoryNameFromScanning>

Each node has 4 child nodes that work the same for exclusions.

Name: Notice in the examples, the page or directory names do not include the file extensions. File extensions are controlled by EasySearch_ValidExtentions
NameStartsWith: Will exclude all page or directory names that start with the included text. Some pages might want to be excluded if for example they start with an "_", which might be a testing page or directory.
NameEndsWith: Will exclude all page or directory names that end with the included text.
NameContains: Will exclude all page or directory names that have the included text anywhere in the page or directory name.

In the above examples, there are two pages that we use on the EasySearchASP.net Site that we want to be excluded from our search index. Lines 2 and 5 are simple examples of how you can exclude pages from being scanned, as well as simply being ignored in the results. Lines 14-27 show the syntax for excluding directory names.

Why would you want to scan a page, and exclude it from the results?

In the above example, we have a page named AllArticlePage.aspx which we wrote for the sole intention of Search Engine Spiders to follow, IE. google, EasySearch, Yahoo, etc. This page point to all the articles on our knowledge base, and is dynamically generated. We want to scan it, because we want search engine spiders to be able to follow all the links on that page, but we don't actually want search results to show the summary page.

FAQ :: Is EasySearchASP.Net licensed for multiple sites?

Sat, 19 Jul 2008 19:31:58 GMT

The EasySearchASP.net License file currently looks like this.

1:     <?xml version="1.0" encoding="utf-8" ?>

2:     <EasySearch>

3:        <License>

4:           <CustomerName>Your Name</CustomerName>

5:           <MajorVersion>1</MajorVersion>

6:           <MaxPageScans>200</MaxPageScans>

7:           <LicenseKey>Your LicenseKey will go here</LicenseKey>

8:        </License>

9:     </EasySearch>

An EasySearchASP.net license is limited to a storing a single dictionary. This single dictionary does have the ability to scan and store information from multiple domains.

For example, the EasySearchASP.net site, and the EasySearchASP.net Knowledge Base are different websites. We outsource our support site to http://www.myKB.com and of course our marketing site is just www.EasySearchASP.net. The EasySearchASP.net product searches both of these domains, and returns a single result set.

The EasySearchASP.net Pro Server license, does allow multiple installations, which in turn will each be allowed to store one or multiple indexes. This license should be purchased when the software is to be used across multiple customers sites, for different purposes.

How does forms authentication work?

Sun, 25 Nov 2007 14:19:51 GMT

EasySearchASP.NET does not have any login capabilities. The index is built only as anonymous users can read the site.

The EasySearchASP.NET web crawler is the same as Google, Yahoo, or Microsoft search engine crawlers. The index is only picking up what content is available to the robot crawler.

For secure content you may consider using a knowledge base to store and search content that needs to only be made available to certain users, or user groups. Our parent company creates myKB.com, which is the knowledge base software we use for our secure content.

Step 1 :: Unzip the EasySearchASP Files and Give Write Permissions to /EasySearchASP Directory

Thu, 01 Nov 2007 14:03:55 GMT

When you purchase EasySearchASP.net, you will receive an EasySearchASP.zip file attached in an email. Unzip this zip file in the root of the website you're installing EasySearchASP.net into. This process will place the EasySearchModule assembly into your application /Bin folder, and create an EasySearchASP folder, and finally a web.EasySearch.Config file in the root.

The zip file will include the following files.

/Web.EasySearch.Config [Details]
Bin/EasySearchModule.dll [Details]
EasySearchASP/EasySearchResults_DataGrid.ascx [Details]
EasySearchASP/EasySearchResults_Repeater.ascx
EasySearchASP/LiveResults.aspx [Details]
EasySearchASP/SearchControl.ascx [Details]
EasySearchASP/XML.aspx.config [Details]
EasySearchASP/EasySearch.css [Details]
EasySearchASP/Sample1.aspx [Details]
EasySearchASP/Sample2.aspx [Details]
EasySearchASP/Sample3.aspx [Details]

After these files have been extracted, an EasySearchASP directory will have been created. This directory can be renamed or moved, it is only the default installation. The ASPNET(IIS5) or Network Service(IIS6) accounts need to be granted write access to this directory so that EasySearchASP.net can serialize itself to disk. This is one of the key features for EasySearchASP.net to be able to startup quickly. Also a log file gets written to this directory if logging is turned on.

/Bin/EasySearchASP.licx

If you've purchased EasySearchASP, then your email also contains an EasySearchASP.licx file. This file needs to be placed inside the /Bin directory after you've extracted the above files. In some cases this license file will be placed inside the EasySearchASP.zip file. This license file needs to stay in the /Bin directory, or alternativley can be embedded as a resource to any assembly in the bin directory.

INFO :: EasySearch\Xml.aspx.config

Thu, 01 Nov 2007 14:00:59 GMT

For security, the xml.aspx file is shipped as xml.aspx.config. This makes the file not available for browsing because of the config ForbiddenFileHandler. To use the file temporarily for debugging purposes you should rename the file to xml.aspx.

EasySearch\Xml.aspx is the page used to display XML information about your EasySearch catalog. From this page you can see the catalog data that is currently stored in your EasySearch Catalog as XML, as well as a few administrative functions, such as deleting the EasySearch Catalog, which will cause the catalog to be reconstructed.

This file does not have to remain in the EasySearch directory, and can actually be renamed. This is a common practice if you have a secure directory to move this file, into that directory. If you do rename the Xml.aspx page, we suggest renaming it to EasySearchXml.aspx, so it is easily recognizable.

Sample XML

We have created a dedicated area in our knowledge base to show examples of how the xml.aspx file can be used. We intend for this to grow over time, but to start there are four examples

EasySearch in a Server Farm -- New Setting for MasterServer

Fri, 24 Feb 2006 14:25:46 GMT

Friday, February 24, 2006

EasySearchASP.net has had several problems running on a server farm environment. The major problem is that there was no way for one server to be an indexer, and another server to be a read only server. So both servers (or all the servers) would scan documents, and try to write files all at the same time. This setting allows you to set the name of your master server, and only that server will do the scanning, and writing of the catalog files. All other servers will act as read only servers, and will only read the resource files, that the master server has written.

On a single server installation, you're free to omit this setting, or set it to the single server machine name.

   1:  <!-- For Server Farms, Enter the Master Server Name, All other servers will be read only -->

   2:  <add key="EasySearch_MasterServerName" value="machinename" />

New Strings in Web.EasySearch.Config

Fri, 24 Feb 2006 14:20:00 GMT

Friday, February 24, 2006

A lot of EasySearch customers have requested that a a few strings in the application be customizable. They don't like the default values, or are possibly international sites, and need this info to be displayed in their native language.

These features were added in EasySearchASP.dll assembly version 1.1.2246.27533, and will remain in effect for all versions after 1.1.2246.27533.

Three string values have been added to the Web.EasySearch.Config file for your customizing.

   1:  <!-- Application Strings -->

2:

   3:  <add key="RequiredSearchResults" value="Search Results Are Required&lt;br/&gt;" />

4:

   5:  <!-- {0} = current page, {1} total pages, {2} = items per page -->

   6:  <add key="PageXofY" value="Viewing Page {0} of {1} ({2} Listings per page)" />

7:

   8:  <add key="PhraseNotFound" value="Phrase Not Found" />

RequiredSearchResults

This is the error message displayed to the end user that a search phrase is required.

PageXofY

This is displayed at the bottom of the Search Data Grid, showing the customer what page they're on, the total number of pages, and the number of items per page being displayed.

PhraseNotFound

Displayed in the type ahead drop down list, when a search phrase is not found.

Add a Search Engine to your ASP.NET Site

Tue, 22 Nov 2005 12:06:12 GMT

Help your Customers Search with Hints

EasySearch Hints assist your customers while they are searching. As soon as you start typing, the live search results show you words that are on your site. Try it now, on our site, in the top right corner. The following image shows how it might look if you searched for the word "hints" as you were typing. The live results ONLY show words that are on your site, so it actually assists your customer to find exactly what they are looking for ... Fast and Easy.

Add a Search Engine To Your Site Today

Adding a search engine to your site is no longer only available to websites that have large development teams behind them. We've taken the pain out of adding search capabilities to your site, by doing all the work for you. EasySearch can be added to your site, in less then 5 minutes.

How Does It Work?

EasySearch starts working as soon as it's turned on. EasySearch looks at your website, builds a dictionary of everything it finds, and keeps track of where it was found. It just takes a few minutes! Once this dictionary is built, users can start searching your site.

How Do I Start Using EasySearch?

EasySearch comes with all the controls that you need to get started. These controls are simply added to your ASP.NET web pages. The first control is a text box, and a series of submit buttons. You can see a sample of this on the top right corner of this page. This is the control that you'll use to give your users the ability to activate a search. The second control is a Repeater that lists the search results for your users. Both of these controls are fully functional, easy, and ready to use.

Try the Live Demo ...

Will EasySearch work on your site? Why not give it a try. The Live Demo lets you type in your web site address, and a search term. Then in seconds, we search your site, and show you the search results. The Live Demo only searched the first 10 pages of your site.

50%, 75%, and 100% Off Coupons

Tue, 15 Nov 2005 06:52:54 GMT

Thank you for your interest in http://www.EasySearchASP.net, The easiest and fastest five minute search solution for your asp.net website. If you're reading this page, you're obviously interested in EasySearchASP.net, and we've come up with a win/win situation, that will help you get your hands on it.

Something that we feel, will make us happy, and help your pocket book as well.

Our goal with this win/win is to have you help us spread the word about EasySearchASP.net. You can help us, by simply writing about, and linking to our EasySearchASP website. Different types of writing, and linking, will qualify for different discounts. These discounts do not apply to the source code version, only to EasySearchASP.net ($99 value) and EasySearchASP.net Pro ($249 Value).

50% Off Discounts

If you simply place a link to our website, using the below links, we'll send you a 50% off coupon. We'd like to ask that this link be on a page, or pages, that will stay active for more than one year.

<a href="http://www.EasySearchASP.net">EasySearchASP.net</a>
Produces
EasySearchASP.net
<a href="http://www.EasySearchASP.net">Search for ASP.net Sites</a>
Produces
Search for ASP.net Sites

75% Off Discounts

Similar to above, only These Links have an image as well. Again, please create these links, where they can stay active for at least a year.

<A href="http://www.easysearchasp.net/"><img border="0" alt="Add Search to any ASP.net Site" src="http://www.easysearchasp.net/Images/Logo/PoweredByEasySearch.gif"></A>
 
<A href="http://www.easysearchasp.net/">EasySearchASP.net</A>
Produces

EasySearchASP.net

100% Discount -- Yes, Free -- 100%

Write a paragraph about EasySearchASP.net. Specifically talking about how EasySearch was easy to use. The demo was easy and fast to get started and worked right away. Maybe how adding search to your ASP.net website was so fast and easy with EasySearchASP.net. Your paragraph should focus on our brand, "EasySearchASP.net" (as apposed to just EasySearch), should mention the keywords "asp.net and search" closely together, and should contain one or more links to our homepage. Not a requirement for the 100% discount coupon, but for bonus points, you can also include our "Powered BY EasySearch" logo above.

EasySearch 1.0 Released

Mon, 14 Nov 2005 22:36:34 GMT

January 3, 2005. After many sleepless nights, EasySearchASP.net is officially released. We've spent a long time making EasySearch as easy to use as possible. Hopefully this comes through to the website, and it's just as easy to use.

We've made great efforts to show you how easy it is to use by having a full working demo available on the site. Simply type in your URL and a search term in the Live Demo page, and you'll see EasySearch in action. This is not using any 3rd party services to search your site, it's same product that you can purchase today, to quickly and easily add Searching capabilities to your own ASP.net site.

If you find something that you especially like, or something that you don't like, or isn't working for you, please let us know, via the comments page.

Thank you.

EasySearch Beta Released

Mon, 14 Nov 2005 22:36:06 GMT

November 24th, 2004

Today is the public debut of EasySearch for ASP.NET. EasySearch is meant to be a "Plug-And-Play" solution for adding a search engine to your ASP.NET WebSite.

More Details To Follow as the Marketing Site Develops.

FAQ :: How do I clear the Search word in the search control?

Wed, 02 Nov 2005 16:17:17 GMT

The last search is stored in the ASP.net Session variable, EasySearch_LastSearchText. So if you want to clear the text, simply clear the session variable.

Session["EasySearch_LastSearchText"] = string.Empty;

NEWS :: EasySearch Source Code Now Available

Tue, 25 Oct 2005 11:10:33 GMT

Tuesday, October 25, 2005

By popular demand, EasySearch C# Source Code is now available for sale. With this source code you'll be able to further integrate search into your solution.

Possibilities include ... (but obviously are not limited to)

Security Integration
Custom Data Storage
Custom User Interfaces
Enhancements

INFO :: HREF attributes need Quotes

Thu, 22 Sep 2005 10:17:26 GMT

EasySearchASP.net uses regular expressions to parse the content that it finds fro a bunch of reasons. One of which is to find links to other pages.

These links are usually in the form of ...

<a href="mypage.aspx">My Page</a>

In rare cases, the link in HTML is created and saved as

<a href=mypage.aspx>My Page</a>

Notice that there are no quotes around the second href attribute. EasySearchASP.net regular expressions depend on the href="" style and for this reason, will not pick up the second instance of mypage.aspx.

It should be considered good practice to use quotes around your href values.

Fixed 2005-May-26 :: ItemsPerPage now affects the Results Repeater.

Thu, 26 May 2005 13:37:40 GMT

The SearchResults control has an ItemsPerPage property on it. This property turns paging on or off for the EasySearchResults_DataGrid.ascx DataGrid.

This is still the case, however the property will now also affect the EasySearchResults_Repeater.ascx repeater control.

If you're using the repeater, before today, there was no way to limit the number of results returned. The repeater always displayed all the results that were found.

Now the repeater will only return maximum number of results in the DataTable up to the ItemsPerPage value.

You can still display the result counts to your users by using the following logic in the EasySearchResults_Repeater.ascx (and the DataGrid.ascx) controls.

Search Phrase: <%=this.SearchPhrase%> 
Items Per Page: <%=this.ItemsPerPage%> 
Results: <%=this.SearchResultCount%> 
Message: <%=this.SearchResultsMessage%>

Frame Support

Tue, 24 May 2005 10:01:52 GMT

Follow pages as found in the following sample.

Frame support is currently in place, but has not throughly been tested. If you're using frames on your site, and would like to help us test this feature, please let us know.

SUGGEST :: Redefine Web.EasySearch.Config, to allow multiple settings.

Tue, 24 May 2005 10:00:27 GMT

Currently the Web.EasySearch.Config file has one set of settings. This can be problematic, if you're scanning multiple sites, and would like to tweak a single site.

For example, This EasySearchASP.net site, searches itself, and the knowledge base. Each of these is independent, however, the settings in Web.EasySearch.Config are single.

Therefor you can not make a change to only one of the sites. This is to be addressed in a future release of EasySearchASP.net

BUG :: International Characters

Tue, 24 May 2005 09:56:04 GMT

Several of the regular expressions in EasySearch wash international characters. If your site has international characters, such as the German Umlauts (äöü, ÄÖÜ) these words will not be indexed properly.

This is a known issue.

FIXED 2005-May-24 :: Item has already been added.

Tue, 24 May 2005 09:55:23 GMT

A bug has come alive in EasySearchASP.net when the need to deserialize the catalog, takes longer then one second. This can happen in a number of situations, where in the time it takes to complete a deserialization from disk, another background thread starts scanning a page, and then a collision occurs.

This problem has been addressed and fixed. The error that you'll see in your log file is ...

Item has already been added. Key in dictionary: "z" Key being added: "z"

Where 'z' can be any letter. This is where the collision occurred. If you already have EasySearchASP.net installed and running, simply download a new copy, and replace the Bin/EasySearchModule.dll file.

FAQ :: How do I handle repeating Meta tags?

Tue, 24 May 2005 09:29:03 GMT

It's a very common approach to use Meta tags to describe the content of your pages. Many sites use this for External search engine ranking, and to help the search engines describe pages.

Internally, to your site, these don't usually help you, since the user cannot see them.

Remember the whole idea of these tags to begin with is to explain to an outside search engine what's on the page. Well since EasySearchASP.net is an internal product, these tags won't usually be helpful.

So how do you turn them off? By using the keywords weighting system. In the configuration setting, there are options to set the weighting system for Title and Keywords, where the latter affects all meta tag settings.

If the keywords have a setting of 0, they'll never be added to the weight of search results, and are in fact rendered useless. Since this is the case, EasySearchASP.net will not scan and store the meta words at all.

This can be a tremendous memory savings for most sites. Doing the calculation, 2000 pages, with 50 meta keywords (that are the same) on each page, = 10,000 object that literally are just wasted space.

Credits

Thank you Eric J. Smith ( Code Smith Tools ) for working with us, to make this option available, and ultimately, make EasySearchASP.net a better product.

Syntax Example, Displayed on www.ASP.net Control Gallery

Wed, 04 May 2005 07:57:13 GMT

EasySearch consists of two simple to use visual
controls. A Search Control and a Search Results
Control. Both of these controls are listed in the
following Example.aspx page. A further description
can be found at the following URL.

/article_88c93.aspx



Register the Controls in the ASPX page.

1: <%@ Register TagPrefix="uc1" 
       TagName="Search" Src="SearchControl.ascx" %>
2: <%@ Register TagPrefix="uc1" 
       TagName="Results" src="EasySearchResults_DataGrid.ascx" %>



This is a supplied CSS style sheet.

7: <link rel="stylesheet" href="EasySearchASP.css" type="text/css">



Here we load the Search Control. This is the text box
that allows the end user to type in their search
criteria. This control also renders the appropriate
code that powers the Live Hints functionality of
EasySearchASP.net.

17:    <uc1:Search id="SearchControl" 
18:        ResultsPageUrl="~/EasySearch/Sample1.aspx?Search={0}" 
19:        IncludeEnterPostBack="true"
20:        runat="server" />



Here we load the EasySearch Results Control. The
product actually comes with 3 example controls. Two
DataGrid controls (one with Paging), and a repeater
control, that simply lists all the results. Keep in
mind that this is only a sample. The Search Results
emits a DataTable that can be bound to any control.

29:     <uc1:Results Id="EasySearchResults_DataGrid1" 
30:        runat="server" />


-- All very simple to use.
--
--

Medium Description With Software Box in the Top Left

Wed, 04 May 2005 07:52:49 GMT

EasySearchASP.net offers the easiest and fastest way to add search capabilities to your website.

What are your customers looking for you your website? Do you know if they're even getting the information they originally came to find.

Global search engines make it easy for users to find your site. But once a user arrives, they must rely on your site layout, and navigation to find their way around.

Add EasySearchASP.net to your website in about 5 minutes, and let your users find what they're looking for.

EasySearchASP.net is easy to install on both dedicated servers, as well as Hosted Servers via FTP. After functionality, our number one goal when developing EasySearchASP.net was to make the product as EASY to use as possible.

Short Description of EasySearch ( Less than 255 Chars )

Wed, 04 May 2005 07:49:30 GMT

Add Search with Live Results (results displayed to the user types) to your website in less than 5 minutes with EasySearchASP.net.

EasySearchASP.net is easy to configure and install on both dedicated servers, as well as Hosted Servers via FTP.

SearchEngine_ValidExtensions

Mon, 02 May 2005 13:40:40 GMT

Valid Extensions that the crawler will scan. These extensions should only include URL extentions that return text or html that can be scanned into EasySearch. Any url ending in an extension not listed here will be skipped. Url's ending in directories ( www.domain.com/directory/ ) will automatically get scanned.

Examples of these valid URL extensions are

html
htm
asp
aspx
php
cfm
txt

INFO :: Bin/EasySearchASP.net.chm

Sat, 23 Apr 2005 10:07:57 GMT

This is the windows help file for the objects found within EasySearchModule.dll. This is a great code reference for developing against EasySearchASP.net.

The most current version of this file can also always be downloaded here.

http://www.EasySearchASP.net/CodeDocs/EasySearchASP.net.chm

FAQ :: Does EasySearchASP Crawl DHTML Menus?

Wed, 20 Apr 2005 09:31:31 GMT

I'm currently using a DHTML Menu from http://www.milonic.com/

Will EasySearch crawl a DHTML Menu system?

Answer :: Yes!

Viewing the source of Milonic.com's home page, revieles source for their great looking Menu Control that looks like the following.

1:     <td class=menu1 valign=top>

2:        <li><a href="/mfa/">Discussion Forum Archive</a>

3:        <li><a href="/login.php">Login</a>

4:        <li><a href="/register.php">Register</a>

5:        <li><a href="/searchengines_milonic.php">Search Engines & Milonic</a>

6:        <li><a href="/removelink.php">Removing the forced Link</a>

7:        <li><a href="/multiplemenus.php">Multiple Menus</a>

8:        <li><a href="/cssbasedmenus.php">CSS Based Menus</a>

9:        <li><a href="/apachesetup.php">Apache Setup</a>

10:       <li><a href="/iissetup.php">Internet Information Server IIS setup</a>

11:       <li><a href="/pipermail/milonic/">Mailing List</a>

12:       <li><a href="/menuvinfo.php">Version Info</a>

13:    </td>

14:    <td class=menu1 valign=top><a href="/aboutmilonic.php">About</a>

15:       <li><a href="/aboutus.php">About us</a>

16:       <li><a href="/testimonials.php">Testimonials</a>

17:       <li><a href="/tablemenu.php">Embedding a Menu inside a Table Cell</a>

18:       <li><a href="/nonprofits.php">Investing in None Profits</a>

19:       <li><a href="/contactus.php">Contact us</a>

20:       <li><a href="/location.php">Where</a>

21:       <li><a href="/corp_customers.php">Distinguished Clients</a>

22:       <li><a href="/cbuy.php">Purchase</a>

23:       <li><a href="/privacy.php">Privacy</a>

24:       <li><a href="/license.php">License</a>

25:       <li><a href="/fraudusers.php">Beware of these guys!</a>

26:    </td>

This type of HTML is very simple, and EasySearch loves it. There are alternative options for you to feed the URL's of your site into the EasySearch Queue.

You can create a page, that just has links on it, and then set it to not be shown in your search results. Look at the ExcludePageNamesFromResults setting.

You can also programatically use EasySearchASP and add URL's to the Queue. Look for a Catalog.AddPageToQueue(string URL) method to accomplish this.

FAQ :: How many HTML pages can EasySearch index?

Wed, 20 Apr 2005 09:27:44 GMT

What is the maximum number of pages EasySearch can index? Of course this is also dependent on the hardware used -- but what is a reasonable number, 100, 200 1000, 2000, 10000 (or more) pages?

Today, EasySearchASP.net has happily indexing 2000 pages for many of our customers. EasySearchASP has been tested and continues to work on a site scanning 15,000 pages. This maximum load, test site uses a High End Web Server, with 8 Gig of Ram on it.

For most modern hardware, EasySearchASP can index around 2000 pages, and not have any impact on the machine.

The important portion of this answer is Hardware.

FAQ :: What happens with repeated content like Menus and Footers?

Wed, 20 Apr 2005 09:18:32 GMT

EasySearchASP has a few rules built into it that makes it easy for you to setup your pages to be scanned as accurately as possible. If you have common elements on your pages, like a footer, then every page on your site that has that foot will be returned when a user searches for a word contained in your footer. This doesn't make for very accurate search results.

Can you ignore the footer? Yes!

There are actually two solutions that can be used independently or together. The first are a set of Ignore comments that the EasySearch crawler looks for. Any content found within these ignore tags will not be indexed into the EasySearchASP catalog. These tags are HTML comments.

These tags are not case sensitive, but they are space sensitive. There should be no spaces in these tags.

To ignore your footer might be to wrap the footer with these comments. That is to place the start tag above your footer, and the end tag below your footer.

You might also look at the ContentStart and ContentEnd tags.

Download the Free Full Working Demo

Mon, 18 Apr 2005 13:56:24 GMT

Full Functioning Free EasySearchASP Demo

The EasySearchASP demo is free. It is fully functional, with no time limit, and none of the features have been turned off. The EasySearchASP Demo displays a "Powered By www.EasySearchASP.NET" link at the bottom of the Search Results pane and is limited to scanning 15 pages on your website.

If you enjoy using the EasySearchASP Demo, upgrading is as simple as purchasing a license, and dropping a new license file into your application.

Please fill out the following form, and an EasySearchASP Demo will be emailed to you.