How To Add Search To A Jekyll Site

09 Dec 2021 | ~6 minute read

When I flipped from WordPress to Jekyll, one thing I really missed was the ability to search my posts on-site. I've now added a proper search tool and this post will show you can do it too.

To add search functionality to a Jekyll site, I used Chris Fei's Simple Jekyll Search, which has really verbose documentation on how to set it all up.

But there were a couple of things I did differently to how Chris recommends, so I wanted to write up how I did it, just in case any of you fine folk find it useful.

How it works is pretty clever. Basically, you create a search.json data file within your site that pulls in all kinds of metadata from your posts at build time.

This is all compiled into the search.json file and then a little bit of JavaScript parses that file for a term you search for, which is then displayed on-screen. Very simple, yet very clever. I like it!

Right, enough waffle, let's get on with the how to...

Step 1 - create the data file

The first thing we're going to do is create the search.json file so that our JavaScript has something to parse when a search is run.

Create a new file in the root of your website and call it search.json, then add the following code to it:


  {% for post in site.posts %}
      "title"    : "{{ post.title }}",
      "url"      : "{{ site.baseurl }}{{ post.url }}",
      "date"     : "{{ | date_to_string }}",
      "description" : "{{ post.description | strip_html | strip_newlines | escape }}"
    } {% unless forloop.last %},{% endunless %}
  {% endfor %}

So what the hell are we doing here then? Well, the first thing we do is add two lines that contain three dashes each. This is to add front matter to the page, so Jekyll knows to render it at build time.

Then we're doing a little hop, skip and a loop through all of the posts on our site so that search.json is populated with the post title, URL, date and description at build. All of the quotes, commas and square brackets are to ensure the output is correctly formatted in JSON markup.

Once the build completed, the contents of search.json looks something like this for my blog:

      "title"    : "Goodbye WordPress, I've Switched To Jekyll (Again)",
      "url"      : "/goodbye-wordpress-switched-to-jekyll/",
      "date"     : "04 Dec 2021",
      "description" : "I've decided to leave WordPress behind and switch to Jekyll...for a second time. This post explains why..."
    } ,

      "title"    : "The Pagination Predicament",
      "url"      : "/the-pagination-predicament",
      "date"     : "26 Nov 2021",
      "description" : "I've removed pagination from my blog for SEO reasons. This post explains why."

We're escaping the HTML on the description so that any special characters in our description, like quote marks, don't break the JSON markup in the file.

Step 2 - add the JavaScript & form

Now we have the data set we want our search form to query, it's time to add some JavaScript so we can parse the results, as well as form so we can, you know, display said results.

The instruction on Chris' repository recommend pulling the JS from NPM's CDN by way of a <script> element in the <head> of the site's default layout.

I decided not to do that for 2 reasons:

  1. I don't want to load that JavaScript on every single page, when it's only needed on my search page.
  2. I didn't want add any third party requests on page load.

So instead, I decided to save the raw JavaScript to /_assets/js/search-script.js within my site.

Then I made another file inside my _includes folder called search-form.html that includes the following content:

<!-- HTML search field -->
<div id="search-container">
<input type="text" id="search-input" placeholder="Type your search here..." autofocus>
<ul id="results-container"></ul>

<!-- Grab search-script.js -->
<script src="/_assets/js/search-script.js" type="text/javascript"></script>

<!-- Configuration -->
  searchInput: document.getElementById('search-input'),
  resultsContainer: document.getElementById('results-container'),
  json: '/search.json'

What this code is doing is calling my search-script.js file, adding the actual search field, then finally configuring the results that are displayed.

As this is in my _includes folder and it contains everything I need to perform a search, I can add it anywhere to my site knowing that the JS will only be loaded where needed.

To embed the search field into anywhere, all I need to do is add the following code where I want it to be displayed:

{% include search-form.html %}

Step 3 - format the results

The default output of the search form is to display the results as a simple unordered list, complete with bullet points and padding.

Because of this, the mobile experience isn't great as the results are too close together. Plus, I wanted to add the date of the post to the results as well.

To do this, I added an extra line to the configuration section of my search-form.html file with the following:

searchResultTemplate: '<li><a href="{url}">{title}</a><br><span class="post-meta">{date}</span></li>'

It's VERY important to add a comma at the end of the previous line, otherwise the results won't work.

With that in mind, our completed configuration section should look like this:

<!-- Configuration -->
  searchInput: document.getElementById('search-input'),
  resultsContainer: document.getElementById('results-container'),
  json: '/search.json',
  searchResultTemplate: '<li><a href="{url}">{title}</a><br><span class="post-meta">{date}</span></li>'

So here we've added a line break to the output and configured it to display the date of the post, as well as add a class of post-meta using the <span> element.

The final step is to remove the bullet points and padding, as well as space out the results and format the date so it's a little smaller than the rest of the text. I did that with the following CSS:

ul#results-container {
  padding: 0;
  list-style-type: none;

#results-container li {
  margin-bottom: 1.5rem;
} {
  font-size: 1rem;

Keeping it accessible

There was still more to do. Personally, I don't mind JavaScript as long as it's used correctly, but some people don't. So I wanted a way to search this site without JavaScript too.

On my search page I added an extra form that doesn't require any JS, but instead searches this site on DuckDuckGo.

Having two search forms on one page would be confusing though, so I hid the DuckDuckGo search form behind the good old <details> element. Here's what it looks like:

Hey, I don't like Javascript!

I get it, not everyone likes JavaScript. I want this site to be as accessible as possible, so if you prefer not to use JavaScript, or have it disabled in your browser, use this form to search my site with DuckDuckGo instead:

Closing thoughts

Adding on-site search to a Jekyll site was a lot easier than I thought, but people shouldn't be forced to use JavaScript if they don't want to.

I think the solution I've come up with should satisfy pretty much every one who visits this site. For those that don't mind, you have a first class, on-site search solution that you can make use of. But if you prefer to avoid JS, I still have you covered.

If you're thinking about adding search to your Jekyll site, hopefully this post will help, but I have assumed a certain level of knowledge here. If anything isn't clear, please feel free to get in touch using the button below.

← The one before
Goodbye WordPress, I've Switched To Jekyll (Again)

Up next →
Be curious...

Get in touch!

Receiving emails from my readers is my favourite thing, so if you have something to say, feel free to drop me an email or sign my guestbook.

Want more content?

Say no more, dear reader. Click the button below to be taken to a random post:

Read a random post...

Want to be informed when I post new articles? Simply enter your email address below and you will get an email whenever new posts are published.

Alternatively, you can subscribe via RSS instead.

Enjoyed this post?

I put a lot of work into maintaining this site and I really enjoy interacting with my readers.

My fuel of choice is coffee, so if you did enjoy this post, or found it in any way useful, I'd appreciate more fuel to keep me going. ❤️

Buy me a coffee