<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ahmet Cetin on Medium]]></title>
        <description><![CDATA[Stories by Ahmet Cetin on Medium]]></description>
        <link>https://medium.com/@ahmetcetin?source=rss-fcc0a37ebe57------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*zj9tinITXasOSH-v.jpg</url>
            <title>Stories by Ahmet Cetin on Medium</title>
            <link>https://medium.com/@ahmetcetin?source=rss-fcc0a37ebe57------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:17:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ahmetcetin/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How search engines works, and what you need to know about it (no, i’m not talking about Google)]]></title>
            <link>https://medium.com/@ahmetcetin/how-search-engines-works-and-what-you-need-to-know-about-it-no-im-not-talking-about-google-49d10be8c14d?source=rss-fcc0a37ebe57------2</link>
            <guid isPermaLink="false">https://medium.com/p/49d10be8c14d</guid>
            <category><![CDATA[seo]]></category>
            <category><![CDATA[search-engine-marketing]]></category>
            <category><![CDATA[search-engines]]></category>
            <category><![CDATA[search-engine-optimizati]]></category>
            <category><![CDATA[search]]></category>
            <dc:creator><![CDATA[Ahmet Cetin]]></dc:creator>
            <pubDate>Fri, 19 Oct 2018 13:12:57 GMT</pubDate>
            <atom:updated>2018-10-20T06:10:02.977Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vt0z5E9jJm5SxsaCFAA70w.jpeg" /></figure><p>No need to mention anymore about importance of being ranked high in search results, be it in Google search, Ebay, Twitter, PikWizard, Pinterest…, you got the idea.</p><p>Let’s say you‘re planning to add an item in the database of one of those web applications and want to know how people can find your item when they search. In this post, I will not go too much into technical details, i’ll just try to explain in layman terms.</p><p>Every web application uses different search engines, different strategies. For some of them, backlink might be very important (guess for which one), for some of them not at all. Some of them are using their own proprietary search engine, some of them are based on open-source search engines, like Solr, Lucene, Sphinx, Elasticsearch (based on Lucene anyways), or some of them are using commercial search engines like Amazon CloudSearch, Algolia.</p><p>Of course every search engine works differently, but there are common approaches and applied more or less in a similar way in all search engines.</p><p>Let’s see step by step what happens when you write a search term in the text box and click on Search button. Search engine basically is doing it’s job in two main steps:</p><ol><li>Finding the related items in database</li><li>Sorting the result based on relevance (unless otherwise requested, like newest first, or most sold etc.)</li></ol><p>Obviously, regardless how you organize the title, description, keywords of the item, if what the user is searching is not included in your item, it won’t be listed.</p><p>Let’s go with an example, so it would be easier to understand the whole process. Again, I’ll not go into too much details to keep this post easier to understand. Of course engines are doing much more than what stated below, but here are main steps.</p><p>In our example, we assume that when you add an item to database, you are specifying the title, description and keywords.</p><p>Let’s say someone is searching for “tooth whitening”, here are the steps search engine does in this order:</p><ol><li>Tokenize the search terms: it separates the words, there are two words, tooth and whitening. So, our tokens would be “tooth” and “whitening”. Some additional steps would be carried out depending on the engine and/or their configuration, it may add synonyms of the words, striping plurals, extensions, removing stop words, converting to lower case, etc.</li><li>Search: it searches each token, in title, description and keywords fields of the database. For example, if there is an item with title “white dog”, it will be included in the result set.</li><li>Ranking: that’s the most important and least understood part.</li></ol><p>A bit more detail on ranking process. What I describe here is applicable to most of the search engines in the market, because almost all of them are using the same algorithm (<a href="https://en.wikipedia.org/wiki/Tf%E2%80%93idf">TF/IDF — term frequency / inverse document frequency</a>), in slightly different way maybe. One exception deserves to mention is Algolia, they’re using different algorithm, but still what described here partially applies. Again, not all the steps listed below might work in every search engine, so knowing which search engine you are targeting has advantage.</p><p>Now, we have the search term tokenized, “tooth” and “whitening”, now let’s see how the raw result set which contains at least one of the tokens are ranked:</p><ul><li>It checks how many times the tokens appears in the item. If item has the word “whitening” twice, it would rank higher than the other items which contains the token once. This is called term frequency.</li><li>Between these tokens, “tooth” and “whitening”, one of them appears in less items than the other. I’ve made the search in one web application, and here are the results, term tooth appears in 1.1 million items, and whitening appears in 83 thousands items. So, the token “whitening” is about 15 times more important than token “tooth”. It’s called specificity or inverse document frequency.</li><li>It checks the relation between the tokens. Let’s consider the title fields of the following two items:<br>- “Tooth whitening service”<br>- “Tooth cleaning and whitening”<br>If we ignore the length of the text (described below), between these two items, first one would rank higher, because the tokens are just next to each other in correct order, but in second item, there are other words between them. This is called proximity.</li><li>It also checks the length of the field. Let’s see an example:<br>- “Tooth whitening service”<br>- “Tooth whitening and cleaning service”<br>Between these two although proximity and frequency are the same, the first item will rank higher than the first one. Because search terms appears in a shorter text. It means more importance giving to the search term than the second one.</li><li>There is no way to know exactly how search engine is configured in each application, but generally speaking not all fields are equal. Most probably in most of the web applications, title has the most importance, then the description, then the keywords. Given two items if search term appears in title, and in another it doesn’t but it appears in keywords, the first item would rank higher.</li><li>Depending the type of the application of course, but most of the applications would like to show to the user newer items more than the old items given the ranking score of the items are similar. Therefore, they are adding a decay factor to the calculation.</li></ul><p>The importance of each factor would differ obviously between each application, but those are things to keep in mind when you are preparing the title, description and keywords of your items, if you want to be found in searches.</p><p>I hope it’s helpful, I’d love to hear your opinions in comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49d10be8c14d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>