Search

This is a custom search module for users. It provides a search page that can search for users by username, email, or a custom text field. The custom text field can come from any content type, thus this module plays nicely with any user-as-node strategy.

The module does one thing and does it well, and is independent of search module. It has enough customization options to allow you to bend it to your will, as well as a healthy number of themable functions.

The XML sitemap module creates a sitemap that conforms to the sitemaps.org specification. This helps search engines to more intelligently crawl a website and keep their results up to date. The sitemap created by the module can be automatically submitted to Ask, Google, Bing (formerly Windows Live Search), and Yahoo! search engines. The module also comes with several submodules that can add sitemap links for content, menu items, taxonomy terms, and user profiles.

Please read the included README.txt, the handbook documentation, and the current list of known issues for more information before using the module.

Overview

This module allows you to add autocomplete functionality to virtually any fields of a Drupal site. During the input, the field will be expanded and offers a list of suggestions before you start the search.
By default, the module integrates with search forms from the Drupal core Search and Search Block.

What is it?

This module provides two ways of referencing relevant content. Both of these methods provide configuration to filter for specific content types and vocabularies, limit the maximum size of the result and provide some header text. The result on both cases are a list of nodes which the module considers most relevant based on the categorization of the current page. This is achieved by finding other nodes which are of one of the allowed types and have the most number of terms in common. The two methods are:

Blocks

This module will provide as many customisable blocks as a site administrator wants. Each block has its own settings for node type, vocabulary, maximum result size and otional header text. Blocks can appear on any page which causes terms to be loaded into Relevant Content. Usually this is any page which views a node (a node page or a view such as a taxonomy term list). Usually you only want a block to appear on a node page, however you may find situation where you want to place a block on a non-node page.

CCK (new)

The new CCK Field Type (available in both 1.3 releases for Drupal 5 & 6). This is a read-only field (much like Node Referrer) which allows the administrator to embed a field that is "display only" (ie, nothing appears on individual node edit forms). This field is configured in the same way the blocks are configured; node type & vocabulary filtering, maximum result size limit and header text. The advantage of the CCK method is the result set is more "embedded" within the content.

Visitors find your site with a search engine. Are you interested in what they were searching for?

Search Engine Referers is a simple module to view the search engine queries used by your visitors. It parses the referer URLs of popular search engines in you access log and extracts the search queries. Currently supported: Google, Yahoo!, Live.com, Yandex.ru, Rambler.ru.

Revolutionize your Drupal search experience

This module integrates Drupal with the Apache Solr search platform. Solr search can be used as a replacement for core content search and boasts both extra features and better performance. If you're looking for Apache Solr integration, this is possibly the best option available.

Designed for sites using Nodeprofile. Enables searching of node profiles, with results linking to user profiles.

Exhibit displays structured data in the form of rich visualizations that can be searched, filtered and sorted using faceted browsing.

Synopsis

Provides a patch to remove content and user search from Drupal core, leaving only the search framework. Provides two new modules, contentsearch and usersearch, which replace the functionality that has been removed. This allows you to turn content or user search off, if you don't want to have them.

Provides one-way string transliteration (romanization) and cleans file names during upload by replacing unwanted characters.

Generally spoken, it takes Unicode text and tries to represent it in US-ASCII characters (universally displayable, unaccented characters) by attempting to transliterate the pronunciation expressed by the text in some other writing system to Roman letters.