How I implement Search like Google Search in PHP or JAVA  

When our web site size hit 60 pages, we added a simple search engine that went through the text of each page and let you look for search terms on the fly. It worked excellently, and it still worked well when the site reached 600 pages.

By the time we were approaching 6000 pages, though, it was beginning to run out of steam; the server load was high (to the extent that it was timing out at busy times of day), and as parts of the web site data migrated from plain pages into MySQL databases, they were no longer found by the search mechanism.

The new mechanism includes a tailored search to look through each of the areas of our site as relevant (and to eliminate as may repetitions as possible - for example between full and summary course page listings), and also searches the MySQL databases.

Matches are sorted not only by relevance, but also by the area of the site in which the hit occurs; a truely tuned search engine. If you enter a search term that fails to match (or only matches one or two times), our engine will suggest alternative searches, in each case suggesting only words or terms that actually occur on the site.

Answered by Yash at 10:12 AM on July 03, 2008

well, When our web site size hit 60 pages, we added a simple search engine that went through the text of each page and let you look for search terms on the fly. It worked excellently, and it still worked well when the site reached 600 pages.

By the time we were approaching 6000 pages, though, it was beginning to run out of steam; the server load was high (to the extent that it was timing out at busy times of day), and as parts of the web site data migrated from plain pages into MySQL databases, they were no longer found by the search mechanism.

The new mechanism includes a tailored search to look through each of the areas of our site as relevant (and to eliminate as may repetitions as possible - for example between full and summary course page listings), and also searches the MySQL databases.

Matches are sorted not only by relevance, but also by the area of the site in which the hit occurs; a truely tuned search engine. If you enter a search term that fails to match (or only matches one or two times), our engine will suggest alternative searches, in each case suggesting only words or terms that actually occur on the site.

Phonetic matching helps to ensure that you'll be offered good alternative words even if you mis-spell your initial term, and the system even looks for two words in one in case you've run your search words together.

Answered by Romi at 4:23 PM on July 01, 2008

When our web site size hit 60 pages, we added a simple search engine that went through the text of each page and let you look for search terms on the fly. It worked excellently, and it still worked well when the site reached 600 pages.

By the time we were approaching 6000 pages, though, it was beginning to run out of steam; the server load was high (to the extent that it was timing out at busy times of day), and as parts of the web site data migrated from plain pages into MySQL databases, they were no longer found by the search mechanism.

The new mechanism includes a tailored search to look through each of the areas of our site as relevant (and to eliminate as may repetitions as possible - for example between full and summary course page listings), and also searches the MySQL databases.

Matches are sorted not only by relevance, but also by the area of the site in which the hit occurs; a truely tuned search engine. If you enter a search term that fails to match (or only matches one or two times), our engine will suggest alternative searches, in each case suggesting only words or terms that actually occur on the site.

Phonetic matching helps to ensure that you'll be offered good alternative words even if you mis-spell your initial term, and the system even looks for two words in one in case you've run your search words together.

Answered by Raksha at 9:51 AM on June 24, 2008

When our web site size hit 60 pages, we added a simple search engine that went through the text of each page and let you look for search terms on the fly. It worked excellently, and it still worked well when the site reached 600 pages.

By the time we were approaching 6000 pages, though, it was beginning to run out of steam; the server load was high (to the extent that it was timing out at busy times of day), and as parts of the web site data migrated from plain pages into MySQL databases, they were no longer found by the search mechanism.

The new mechanism includes a tailored search to look through each of the areas of our site as relevant (and to eliminate as may repetitions as possible - for example between full and summary course page listings), and also searches the MySQL databases.

Matches are sorted not only by relevance, but also by the area of the site in which the hit occurs; a truely tuned search engine. If you enter a search term that fails to match (or only matches one or two times), our engine will suggest alternative searches, in each case suggesting only words or terms that actually occur on the site.

Phonetic matching helps to ensure that you'll be offered good alternative words even if you mis-spell your initial term, and the system even looks for two words in one in case you've run your search words together.

Answered by Madhurima at 1:22 PM on June 14, 2008

When our web site size hit 60 pages, we added a simple search engine that went through the text of each page and let you look for search terms on the fly. It worked excellently, and it still worked well when the site reached 600 pages.

By the time we were approaching 6000 pages, though, it was beginning to run out of steam; the server load was high (to the extent that it was timing out at busy times of day), and as parts of the web site data migrated from plain pages into MySQL databases, they were no longer found by the search mechanism.

The new mechanism includes a tailored search to look through each of the areas of our site as relevant (and to eliminate as may repetitions as possible - for example between full and summary course page listings), and also searches the MySQL databases.

Matches are sorted not only by relevance, but also by the area of the site in which the hit occurs; a truely tuned search engine. If you enter a search term that fails to match (or only matches one or two times), our engine will suggest alternative searches, in each case suggesting only words or terms that actually occur on the site.

Phonetic matching helps to ensure that you'll be offered good alternative words even if you mis-spell your initial term, and the system even looks for two words in one in case you've run your search words together.

Answered by Ashish Yadav at 6:53 PM on June 10, 2008

hello sudhakar well;
When our web site size hit 60 pages, we added a simple search engine that went through the text of each page and let you look for search terms on the fly. It worked excellently, and it still worked well when the site reached 600 pages. By the time we were approaching 6000 pages, though, it was beginning to run out of steam; the server load was high (to the extent that it was timing out at busy times of day), and as parts of the web site data migrated from plain pages into MySQL databases, they were no longer found by the search mechanism.

The new mechanism includes a tailored search to look through each of the areas of our site as relevant (and to eliminate as may repetitions as possible - for example between full and summary course page listings), and also searches the MySQL databases. Matches are sorted not only by relevance, but also by the area of the site in which the hit occurs; a truely tuned search engine. If you enter a search term that fails to match (or only matches one or two times), our engine will suggest alternative searches, in each case suggesting only words or terms that actually occur on the site. Phonetic matching helps to ensure that you'll be offered good alternative words even if you mis-spell your initial term, and the system even looks for two words in one in case you've run your search words together.

Answered by raj u at 2:04 PM on June 10, 2008

well;
When our web site size hit 60 pages, we added a simple search engine that went through the text of each page and let you look for search terms on the fly. It worked excellently, and it still worked well when the site reached 600 pages. By the time we were approaching 6000 pages, though, it was beginning to run out of steam; the server load was high (to the extent that it was timing out at busy times of day), and as parts of the web site data migrated from plain pages into MySQL databases, they were no longer found by the search mechanism.

The new mechanism includes a tailored search to look through each of the areas of our site as relevant (and to eliminate as may repetitions as possible - for example between full and summary course page listings), and also searches the MySQL databases. Matches are sorted not only by relevance, but also by the area of the site in which the hit occurs; a truely tuned search engine. If you enter a search term that fails to match (or only matches one or two times), our engine will suggest alternative searches, in each case suggesting only words or terms that actually occur on the site. Phonetic matching helps to ensure that you'll be offered good alternative words even if you mis-spell your initial term, and the system even looks for two words in one in case you've run your search words together.

Answered by kishore at 9:01 PM on June 09, 2008

Try to ensure that no page is ever more than three clicks away, and a clear navigation system helps. But with the best will in the world, these principles that work well for a small site aren't so effective as it grows ... and we expect it to continue to grow.

When our web site size hit 60 pages, we added a simple search engine that went through the text of each page and let you look for search terms on the fly. It worked excellently, and it still worked well when the site reached 600 pages. By the time we were approaching 6000 pages, though, it was beginning to run out of steam; the server load was high (to the extent that it was timing out at busy times of day), and as parts of the web site data migrated from plain pages into MySQL databases, they were no longer found by the search mechanism.

The new mechanism includes a tailored search to look through each of the areas of our site as relevant (and to eliminate as may repetitions as possible - for example between full and summary course page listings), and also searches the MySQL databases. Matches are sorted not only by relevance, but also by the area of the site in which the hit occurs; a truely tuned search engine. If you enter a search term that fails to match (or only matches one or two times), our engine will suggest alternative searches, in each case suggesting only words or terms that actually occur on the site. Phonetic matching helps to ensure that you'll be offered good alternative words even if you mis-spell your initial term, and the system even looks for two words in one in case you've run your search words together.

If you're looking to improve your own site search, there's some technical information available on how our new engine now works and on how we suggest alternative search terms. You can learn about the technoligies we use on our PHP course and our MySQL course; I present both of these personally and will be very happy to talk with you about searching.

Answered by Shobhit at 5:45 PM on June 09, 2008

Hi there

Try to ensure that no page is ever more than three clicks away, and a clear navigation system helps. But with the best will in the world, these principles that work well for a small site aren't so effective as it grows ... and we expect it to continue to grow.

When our web site size hit 60 pages, we added a simple search engine that went through the text of each page and let you look for search terms on the fly. It worked excellently, and it still worked well when the site reached 600 pages. By the time we were approaching 6000 pages, though, it was beginning to run out of steam; the server load was high (to the extent that it was timing out at busy times of day), and as parts of the web site data migrated from plain pages into MySQL databases, they were no longer found by the search mechanism.

The new mechanism includes a tailored search to look through each of the areas of our site as relevant (and to eliminate as may repetitions as possible - for example between full and summary course page listings), and also searches the MySQL databases. Matches are sorted not only by relevance, but also by the area of the site in which the hit occurs; a truely tuned search engine. If you enter a search term that fails to match (or only matches one or two times), our engine will suggest alternative searches, in each case suggesting only words or terms that actually occur on the site. Phonetic matching helps to ensure that you'll be offered good alternative words even if you mis-spell your initial term, and the system even looks for two words in one in case you've run your search words together.

If you're looking to improve your own site search, there's some technical information available on how our new engine now works and on how we suggest alternative search terms. You can learn about the technoligies we use on our PHP course and our MySQL course; I present both of these personally and will be very happy to talk with you about searching.

Answered by Reeta K at 3:56 PM on June 09, 2008