> For the complete documentation index, see [llms.txt](https://docs.codpeller.com/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codpeller.com/en/multi-level-menu/faq/how-do-i-place-the-menu-under-my-stores-main-menu.md). # How do I place the menu under my store’s main menu? ### **Adding the menu**

Figure 1. Multi-level menu

Go to your store’s main page. Hover your mouse over the standard menu, then right-click on it. In the menu that appears, choose **"Inspect"** (see Figure 2)

Figure 2. Click "Inspect"

In the window that opens, look at the selector and make sure it highlights the entire menu (or any other block where you want your custom menu to appear under). Choose a container class that’s unique — one that doesn’t repeat anywhere else (see Figure 3).\ In our example, the class is `.ins-tile--header` ```html .ins-tile--header ```

Figure 3. Choose the selector

Now take the script ```javascript ``` Find `.ins-tile--announcement-bar` in the script and replace it with your chosen selector — for example, `.ins-tile--header` Your updated script should now look like this ```javascript ``` Go to the menu settings page and scroll down to the **Compatibility Parameters** section (Figure 4). In the **Container** field, enter: `#kinvasoft-menu-static-container` ```css #kinvasoft-menu-static-container ```

Figure 4. The "Container" field

Go to the **Website** page and open the **SEO Settings** section. Click **Edit** and paste the script into the field (Figure 5). Click **Save**.

Figure 5. Adding the script

Then go to your **main page** to check if the menu appears correctly.\ Also visit your **storefront** page to make sure the menu is displayed there too. ### **Show the search bar** Once you’ve placed the menu and enabled the search bar, the menu loads smoothly and works great. However, when clicking the **Search** button, the search bar may be hidden behind the menu (see Fig. 7).

Fig. 7. Search bar is not visible

Let’s fix that by adjusting its visibility (see Fig. 8)

Fig. 8. Search bar is now visible

To fix it: Go to **Website** → **SEO Settings** in your store admin. Click Edit and paste the following script in the code field. ```css ``` Save the changes. Visit your storefront to check the result. If the search bar is still hidden, try: * clearing your browser cache, or * opening the site in **Incognito mode**. **Tip**: If you want the search bar to appear lower on the page, increase the value (e.g., replace `70px` with `120px`) in the script. ### **Adjusting the menu width** If you'd like the menu to stretch across the full width of the storefront,\ go to **Menu bar > Layout > Menu Width** (Figure 6), select **Maximum**, and click **Save**.

Figure 6. Adjusting menu width.

If you have any questions or suggestions, feel free to reach out to our [support](/en/what-is-codpeller/support.md) — we're always happy to help. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.codpeller.com/en/multi-level-menu/faq/how-do-i-place-the-menu-under-my-stores-main-menu.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.