> For the complete documentation index, see [llms.txt](https://attr.sygnal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://attr.sygnal.com/sa5-404/article-1.md).

# 404 Smart Search ❺

Add a Smart Search to Your 404 Pages.

{% hint style="info" %}
**These are 100% internal R\&D.**\
No public product is available, but if you need these features, contact us for details on how we can implement them for you. 
{% endhint %}

*404's happen* - but they don't need to be the end of the road. Help your visitors get where their going by automatically populating Webflow's search component with the URL path keywords they were originally trying to reach?

## Demonstration <a href="#display-captions-in-webflows-lightboxes" id="display-captions-in-webflows-lightboxes"></a>

This URL points to a Webflow site, for which the page does not exist;

```
https://www.sygnal.com/blog/export-redirects
```

Click the link to see the 404 lib auto-populate a Webflow site search input.&#x20;

{% embed url="<https://www.sygnal.com/blog/export-redirects>" %}

## Usage Notes <a href="#getting-started-nocode" id="getting-started-nocode"></a>

Click to expand the feature you want.

<details>

<summary>I want this Search input to auto-populate from the current path</summary>

Add a [Webflow Search](https://university.webflow.com/lesson/site-search) element, and on the input field add a custom attribute of `wfu-404-search`. No value is needed.

</details>

## Getting Started ( NOCODE ) <a href="#getting-started-nocode" id="getting-started-nocode"></a>

### STEP 1 - Add the Library <a href="#step-1---add-the-library" id="step-1---add-the-library"></a>

First, **add the library** as detailed in [Quick Start](/sa5-404/quick-start-or-sa5-404.md).&#x20;

### STEP 2 - Add `wfu-404-search` to your Search input

Add a [Webflow Search](https://university.webflow.com/lesson/site-search) element, and on the input field add a custom attribute of `wfu-404-search`. No value is needed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://attr.sygnal.com/sa5-404/article-1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.