# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Hide label/badge on a specific page in your store](https://docs.samita.io/badges-and-labels/hide-label-badge-on-a-specific-page-in-your-store.md)
- [Display banner at specific position on Homepage](https://docs.samita.io/banners/display-banner-at-specific-position-on-homepage.md)
- [Display Highlight on front store](https://docs.samita.io/trustbadge-plus/display-highlight-on-front-store.md)
- [Where to find Shopify’s collaborator request code for access?](https://docs.samita.io/faqs/where-to-find-shopifys-collaborator-request-code-for-access.md)
- [Display banner on selected product pages](https://docs.samita.io/banners/display-banner-on-selected-product-pages.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://docs.samita.io/badges-and-labels/hide-label-badge-on-a-specific-page-in-your-store.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://docs.samita.io/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.samita.io/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., `/badges-and-labels/hide-label-badge-on-a-specific-page-in-your-store.md`).

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