# Page Not Found

The URL `files/Ku6rLHRHoVraJRwpUOAV` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Post, Page, Product and other Post Type Search](https://documentation.ajaxsearchpro.com/general-settings/search-in-posts-and-pages.md)
- [Search box and input field layout](https://documentation.ajaxsearchpro.com/theme-options/search-box-and-input-field-layout.md)
- [Search by categories, tags or other terms](https://documentation.ajaxsearchpro.com/general-settings/search-in-terms-categories-tags....md)
- [Gutenberg and Other Page Editors](https://documentation.ajaxsearchpro.com/getting-started/gutenberg-elementor-divi-other-page-editors.md)
- [Purchase Code (license key)](https://documentation.ajaxsearchpro.com/plugin-updates/automatic-updates/purchase-code.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://documentation.ajaxsearchpro.com/general-settings/search-in-posts-and-pages.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://documentation.ajaxsearchpro.com/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://documentation.ajaxsearchpro.com/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/general-settings/search-in-posts-and-pages.md`).

You may also use `Accept: text/markdown` header for content negotiation.