> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/volume-themes/faq/navigation-and-header/can-i-make-the-mega-menu-column-headings-non-clickable.md). # Can I make the mega menu column headings non-clickable? Why mega menu column headings are always links in Volume, and the Custom CSS rule that turns them into plain labels. Not with a setting, no. In Volume every item in a mega menu is a real link, headings included. The column heading is not a separate field you fill in — it *is* the first-level item from the menu you selected in the **Header**, and it renders as a link pointing at whatever URL that item has in **Online Store → Navigation**. Shopify's menu editor requires a URL on every item, so there is no "label only" state to switch to. ### The better fix first Give the heading somewhere worth going: the matching collection, or a landing page for that category. Shoppers routinely click category titles expecting the full listing, and a heading that does nothing reads as a broken link. In practice this solves the request more often than hiding the link does. ### If you really want a plain label Add this to **Theme settings → Custom CSS**: ```css .mega-menu .menu__dropdown-child-item-link { pointer-events: none; cursor: default; } ``` The links listed underneath each heading stay clickable — only the headings are affected. The rule covers both **Mega menu** and **Mega menu short**, and it survives theme updates, because Custom CSS is stored with your theme settings rather than in a file. {% hint style="warning" %} This hides the click, not the link. The heading is still a link in the page, so keyboard and screen-reader users can still land on it and follow it. It also applies to every mega menu in the header at once — there is no per-block version of the rule. The mobile menu drawer is built from different markup, so this rule does not touch it. {% endhint %} {% hint style="success" icon="lightbulb" %} If what you actually want is a heading that *looks* like a heading rather than like a link, style it instead: **First nested → Link style**, **Uppercase** and **Bolder font** in the mega menu block change the headings only, and leave the links below them alone. More on the block in [Mega menu: columns, banners, width and clickable parents](/docs/volume-themes/faq/navigation-and-header/mega-menu-columns-banners-width-and-clickable-parents.md). {% endhint %} --- # 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://staylime.com/docs/volume-themes/faq/navigation-and-header/can-i-make-the-mega-menu-column-headings-non-clickable.md?ask=&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.