# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Adding Smartrr to a custom page (Shopify Liquid)](https://help.smartrr.com/docs/getting-started/implementation/adding-smartrr-to-a-custom-page-shopify-liquid.md)
- [Developer Documentation](https://help.smartrr.com/docs/support/developer-documentation.md)
- [Troubleshooting](https://help.smartrr.com/docs/support/troubleshooting.md)
- [Out of stock behavior](https://help.smartrr.com/docs/support/transactions/out-of-stock-behavior.md)
- [Installing Smartrr on a Shopify 2.0 theme (Automatic Install)](https://help.smartrr.com/docs/getting-started/implementation/installing-smartrr-on-a-shopify-2.0-theme-automatic-install.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://help.smartrr.com/docs/getting-started/implementation/adding-smartrr-to-a-custom-page-shopify-liquid.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://help.smartrr.com/docs/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://help.smartrr.com/docs/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., `/docs/getting-started/implementation/adding-smartrr-to-a-custom-page-shopify-liquid.md`).

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