Search: Difference between revisions

(One intermediate revision by the same user not shown)

Line 1:

~~{{Template~~:~~Categorypage|~~Search}}

== 2025 update ==

Google’s enshittification is real. It used to be that businesses wanted to use SEO to optimize for the Google platform. But that was 10-15 years ago, and we're now at "Google Zero" where Google doesn't really send you outside their platform. So, here's a quick update on some options.

=== Open Web Engine ===

interesting portal to multiple search engines https://openwebengine.com/

=== AI-overview-free Google search ===

'''[https://udm14.org/ udm=14]''' is easy access to Google Search results using '''only''' web results (no AI overviews, knowledge panels, or other fluff). Other [https://support.google.com/websearch/answer/2466433 advanced filter techniques] are still offered in Google's help pages.

== User Aids ==

~~=== Searching the Web ===~~

# 'Google is your friend' tm, and the 'Customize Google' tool (see [[Browser Extensions]]) does all kinds of things to help you search using Google, AND easily opens up the world of search engines by letting you replicate your search across other engines in a click.

~~# http://www.googletutor.com/ Google Tutor helps you learn and understand Google~~

~~# http://www.googleguide.com/ Google Guide helps you learn and understand Google~~

=== Semantic Web Search ===

Line 20:

Line 24:

Applications such as this wiki (runs on MediaWiki), and CMS systems (e.g. Drupal) obviously know their own content. So, usually it would suffice to make use of the search facilities built in to the application. However, this doesn't always ring true -- especially when you consider that search as a service in it's own right is probably more powerful than search as a "feature" that is independently tacked on to each application in your stack.

There is a series of articles about the introduction of Full Text Search (FTS) in InnoDB engine for MySQL 5.6 at https://www.percona.com/blog/2013/02/26/myisam-vs-innodb-full-text-search-in-mysql-5-6-part-1/

[[wp:full-text_search|Full-text search]]<ref>In text retrieval, full-text search refers to techniques for searching a single computer-stored document or a collection in a full-text database. Full-text search is distinguished from searches based on metadata or on parts of the original texts represented in databases.</ref> has since been integrated as a feature of all major SQL database products<ref>[[wp:Full-text_search#Software|List of software]]</ref>. And now the world has "moved on" (with considerable overlap since major products also feature vector search) to [[Vector database|vector databases]] offering search based on similarity using different algorithms.

Users and Implementors of MediaWiki, see [[MediaWiki/Search]].

Line 26:

Line 32:

== General ==

[[File:Apache Solr Front Cover.jpg|200px|right|reviewed by Greg Rundlett|link=https://books.google.com/books?id=9jByAgAAQBAJ&pg=PT24&source=gbs_toc_r&cad=3#v=onepage&q&f=false]]

[[File:Google Custom Search Engine (GSE) appliance.png|alt=screenshot of a Google Search Engine implementation|thumb|Google Search for Enterprise users]]

Google offers a service called the [http://www.google.com/coop/cse/ Google Custom Search Engine]. The Google CSE is much like the 'normal' Google, but is configured to include only domains that you want. Additionally, the domains can be grouped into 'realms' that can be used to assist the user to find content according to functional area.

Line 52:

Line 59:

[https://github.com/mozsearch/mozsearch MozSearch] is the engine behind '''[https://searchfox.org/ Searchfox]''' allowing to search the 21 millions of lines of code in the Mozilla project.

'''[[ElasticSearch]]''' is a search engine based on Apache Lucene and is used by the [[MediaWiki]] software (through extensions) to offer search; and is also the default backing store for the [[Semantic MediaWiki]] extension. WMF staff have decided to migrate off ElasticSearch onto the fork, called [[:en:OpenSearch_(software)|'''OpenSearch''']]. (not to be confused with the long-standing syndication standard for search interfaces ~~- see "Browser extensions" below~~)

'''[[ElasticSearch]]''' is a search engine based on Apache Lucene and is used by the [[MediaWiki]] software (through extensions) to offer search; and is also the default backing store for the [[Semantic MediaWiki]] extension. WMF staff have decided to migrate off ElasticSearch onto the fork, called [[:en:OpenSearch_(software)|'''OpenSearch''']]. (not to be confused with the long-standing '''syndication standard for search interfaces''' See [[OpenSearch standard]])

[https://www.opensearch.org/ '''OpenSearch'''] is a community-driven, Apache 2.0-licensed open source search and analytics suite that makes it easy to ingest, search, visualize, and analyze data. The OpenSearch '''Dashboards''' component is equivalent to the '''Kibana''' tool of Elastic.

~~=== Browser extensions / Web Apps ===~~

* [[wp:OpenSearch]] is a standard for building search plugins, and exposing search services. It is how Firefox is able to hook up with wikipedia to offer suggestions '''as you type''' in the wikipedia search toolbar within Firefox. It is also how this site tells the browser that it offers a search toolbar plugin.

~~# Visit this site http://freephile.com/wiki/~~

~~# notice that the icon in the Firefox search toolbar turns bluish~~

~~# click the little icon to reveal that there is a plugin available that will 'Add {{SITENAME}} (En)'~~

~~=== Opensearch Implementation example ===~~

~~Opensearch is implemented in the [[MediaWiki]] system.~~

~~Viewing source on a page, you will see the following element:~~

~~<pre>~~

~~<xml>~~

~~<link rel="search" type="application/opensearchdescription+xml" href="/wiki/opensearch_desc.php" title="{{SITENAME}} (English)" />~~

~~</xml>~~

~~</pre>~~

~~That script (/wiki/opensearch_desc.php) generates xml output that the browser can interpret~~

== Search Engine Optimization (SEO) ==

How do you make your website Search-engine friendly? How do you get 'organic' traffic from Google? It's all about [[SEO]].

== See Also ==

[[Category:Help]]

[[Category:Howto]]

@@ Line 1: / Line 1: @@
-{{Template:Categorypage|Search}}
+== 2025 update ==
+Google’s enshittification is real. It used to be that businesses wanted to use SEO to optimize for the Google platform. But that was 10-15 years ago, and we're now at "Google Zero" where Google doesn't really send you outside their platform. So, here's a quick update on some options.
+=== Open Web Engine ===
+interesting portal to multiple search engines https://openwebengine.com/
+=== AI-overview-free Google search ===
+'''[https://udm14.org/ udm=14]''' is easy access to Google Search results using '''only''' web results (no AI overviews, knowledge panels, or other fluff). Other [https://support.google.com/websearch/answer/2466433 advanced filter techniques] are still offered in Google's help pages.
 == User Aids ==
-=== Searching the Web ===
-# 'Google is your friend' tm, and the 'Customize Google' tool (see [[Browser Extensions]]) does all kinds of things to help you search using Google, AND easily opens up the world of search engines by letting you replicate your search across other engines in a click.
-# http://www.googletutor.com/ Google Tutor helps you learn and understand Google
-# http://www.googleguide.com/ Google Guide helps you learn and understand Google
 === Semantic Web Search ===
@@ Line 20: / Line 24: @@
 Applications such as this wiki (runs on MediaWiki), and CMS systems (e.g. Drupal) obviously know their own content.  So, usually it would suffice to make use of the search facilities built in to the application.  However, this doesn't always ring true -- especially when you consider that search as a service in it's own right is probably more powerful than search as a "feature" that is independently tacked on to each application in your stack.
 There is a series of articles about the introduction of Full Text Search (FTS) in InnoDB engine for MySQL 5.6 at https://www.percona.com/blog/2013/02/26/myisam-vs-innodb-full-text-search-in-mysql-5-6-part-1/
+[[wp:full-text_search|Full-text search]]<ref>In text retrieval, full-text search refers to techniques for searching a single computer-stored document or a collection in a full-text database. Full-text search is distinguished from searches based on metadata or on parts of the original texts represented in databases.</ref> has since been integrated as a feature of all major SQL database products<ref>[[wp:Full-text_search#Software|List of software]]</ref>. And now the world has "moved on" (with considerable overlap since major products also feature vector search) to [[Vector database|vector databases]] offering search based on similarity using different algorithms.
 Users and Implementors of MediaWiki, see [[MediaWiki/Search]].
@@ Line 26: / Line 32: @@
 == General ==
 [[File:Apache Solr Front Cover.jpg|200px|right|reviewed by Greg Rundlett|link=https://books.google.com/books?id=9jByAgAAQBAJ&pg=PT24&source=gbs_toc_r&cad=3#v=onepage&q&f=false]]
+[[File:Google Custom Search Engine (GSE) appliance.png|alt=screenshot of a Google Search Engine implementation|thumb|Google Search for Enterprise users]]
 Google offers a service called the [http://www.google.com/coop/cse/ Google Custom Search Engine].   The Google CSE is much like the 'normal' Google, but is configured to include only domains that you want.  Additionally, the domains can be grouped into 'realms' that can be used to assist the user to find content according to functional area.
@@ Line 52: / Line 59: @@
 [https://github.com/mozsearch/mozsearch MozSearch] is the engine behind '''[https://searchfox.org/ Searchfox]''' allowing to search the 21 millions of lines of code in the Mozilla project.
-'''[[ElasticSearch]]''' is a search engine based on Apache Lucene and is used by the [[MediaWiki]] software (through extensions) to offer search; and is also the default backing store for the [[Semantic MediaWiki]] extension. WMF staff have decided to migrate off ElasticSearch onto the fork, called [[:en:OpenSearch_(software)|'''OpenSearch''']]. (not to be confused with the long-standing syndication standard for search interfaces - see "Browser extensions" below)
+'''[[ElasticSearch]]''' is a search engine based on Apache Lucene and is used by the [[MediaWiki]] software (through extensions) to offer search; and is also the default backing store for the [[Semantic MediaWiki]] extension. WMF staff have decided to migrate off ElasticSearch onto the fork, called [[:en:OpenSearch_(software)|'''OpenSearch''']]. (not to be confused with the long-standing '''syndication standard for search interfaces''' See [[OpenSearch standard]])
 [https://www.opensearch.org/ '''OpenSearch''']  is a community-driven, Apache 2.0-licensed open source search and analytics suite that makes it easy to ingest, search, visualize, and analyze data. The OpenSearch '''Dashboards''' component is equivalent to the '''Kibana''' tool of Elastic.
-=== Browser extensions / Web Apps ===
-* [[wp:OpenSearch]] is a standard for building search plugins, and exposing search services.  It is how Firefox is able to hook up with wikipedia to offer suggestions '''as you type''' in the wikipedia search toolbar within Firefox.  It is also how this site tells the browser that it offers a search toolbar plugin.
-# Visit this site http://freephile.com/wiki/
-# notice that the icon in the Firefox search toolbar turns bluish
-# click the little icon to reveal that there is a plugin available that will 'Add {{SITENAME}} (En)'
-=== Opensearch Implementation example ===
-Opensearch is implemented in the [[MediaWiki]] system.
-Viewing source on a page, you will see the following element:
-<pre>
-<xml>
-<link rel="search" type="application/opensearchdescription+xml" href="/wiki/opensearch_desc.php" title="{{SITENAME}} (English)" />
-</xml>
-</pre>
-That script (/wiki/opensearch_desc.php) generates xml output that the browser can interpret
 == Search Engine Optimization (SEO) ==
 How do you make your website Search-engine friendly?  How do you get 'organic' traffic from Google?  It's all about [[SEO]].
+== See Also ==
+{{Template:Categorypage|Search}}
 [[Category:Help]]
 [[Category:Howto]]