Dropdown Menus in Squarespace: Why the Answer Is a Folder

Updated September 2026 · Written and maintained by the Progression Agency strategy team

There is no control called dropdown in Squarespace. You create a folder in the Pages panel and put pages inside it, and the folder renders as a dropdown automatically. That single fact resolves most questions about Squarespace menus — including the most common complaint, which is that the top-level folder item is not a clickable page. This covers how to build one, why the dropdown is not showing, the platform’s firm limits, and how many menu items a site should actually have.

How do you make a dropdown menu in Squarespace?

You do not create a dropdown directly. You create a folder in the navigation and put pages inside it — the folder renders as a dropdown automatically.

This is the single fact that resolves almost every question about Squarespace menus. There is no control called dropdown, no submenu setting and no nesting option in the page editor. The mechanism is the folder, and once you know that the whole feature is straightforward.

Go to the Pages panel, add a folder, name it what you want the menu item to say, then drag existing pages into it or create new ones inside it. The folder appears in the navigation, and hovering or tapping it reveals the pages within.

1. Open the Pages panel in the site editor.
2. Add a new item and choose Folder rather than Page.
3. Name the folder. This name becomes the top-level menu item, so name it for the visitor rather than for you.
4. Drag existing pages into the folder, or create new pages inside it.
5. Check the order. Pages appear in the dropdown in the order they sit in the panel, and you reorder by dragging.
6. Confirm the folder is in the main navigation section rather than in Not Linked, which is where pages hide.
7. Preview on desktop and on a phone, because the two render the menu quite differently.

The thing everyone hits: a folder is not a page

A Squarespace folder has no page of its own. Clicking the top-level item does nothing on desktop and opens the submenu on mobile, which surprises people who expected a landing page.

This is the most common complaint about Squarespace menus and it is a design decision rather than a limitation to work around badly. A folder is a container.

If you need the top-level item to be a real page — a services page that also has service pages beneath it — the usual approach is to name a page inside the folder as an overview and place it first, or to link the folder title to that page using a link item. Both are compromises; the second is generally cleaner for visitors.

Why folders behave this way

They exist to group navigation, not to hold content. Squarespace keeps the two concepts separate deliberately.

The overview page pattern

Create a page inside the folder called Overview, or repeat the section name, and place it first. Visitors reach it in one extra click.

The link-item pattern

Add a link in the navigation pointing to a real page, and use the folder only where a genuine group exists. Cleaner, and it avoids empty top-level items.

What not to do

Duplicating the folder name as both a folder and a separate page confuses visitors and creates two competing entries in the navigation.

Mobile behavior

On a phone the top-level item expands the submenu rather than navigating, which is usually the behavior people actually want.

Squarespace menus: what you can and cannot do

One level of dropdown, ordered by drag, styled through site styles. No multi-level nesting, no mega menus natively, and no per-item styling without custom code.

Knowing the boundaries before designing the navigation saves rebuilding it. The constraints are firm rather than hidden.

Why my Squarespace dropdown is not showing

Usually the folder is empty, the pages are in Not Linked, the folder itself is in Not Linked, or you are looking at a template that renders navigation differently.

Work through these in order; the first three account for nearly every case.

1. Check the folder actually contains pages. An empty folder shows as a top-level item with no dropdown.
2. Check the pages are inside the folder rather than beside it in the panel. The indentation in the Pages panel tells you.
3. Check the folder is in the main navigation section, not in Not Linked.
4. Check whether the pages inside are disabled. A disabled page does not appear in the menu.
5. Check on desktop as well as mobile — the behavior differs, and one working does not mean both do.
6. Clear the browser cache or check in a private window before troubleshooting further.
7. Confirm your template supports dropdowns in the header layout you have chosen. Some header layouts handle nesting differently.

How many items should a navigation have?

Fewer than most sites use. Five to seven top-level items is a sensible ceiling, and a dropdown with more than about seven entries is a sign the structure needs rethinking rather than reorganizing.

Navigation is where site structure becomes visible, and an overloaded menu is almost always a symptom rather than a problem in itself. If everything needs to be in the menu, the site has no hierarchy.

The practical test: could a visitor who has never seen the site guess where a given piece of information lives? If not, adding more menu items will not fix it.

Dropdowns and search visibility

Menu links are ordinary links and pass value normally. The real consideration is that pages reachable only through a dropdown are still reachable, and pages in Not Linked are not.

There is no penalty for dropdown navigation and no particular benefit. What matters is that every page you want found is linked from somewhere, and that the anchor text in the menu describes the page.

The mistake worth avoiding is putting important pages in Not Linked to tidy the menu and then forgetting they have no internal links at all. A page with no incoming links is close to invisible, whatever the sitemap says.

• Menu anchor text should describe the destination. About Us tells a visitor nothing; the page name matters more than tidiness.
• Pages moved to Not Linked need internal links from somewhere else, or they are effectively orphaned.
• A folder with no pages produces a dead menu item, which is a small but real usability problem.
• Overview pages placed first in a folder give both visitors and search engines a sensible entry point to a section.
• Keep the menu stable. Changing navigation labels frequently confuses returning visitors and loses whatever recognition they had built.
• Check the mobile menu separately, because a menu that is fine on desktop can be unusable on a phone.

Squarespace menus on mobile

The dropdown becomes an expanding list, the folder title becomes a toggle rather than a link, and long menus become a scrolling panel. Check it separately, every time.

Most visitors arrive on a phone, and the mobile menu is where an over-full navigation actually becomes a problem. A ten-item menu with three folders is manageable with a mouse and genuinely unpleasant with a thumb. If the mobile menu requires scrolling to reach the main call to action, the navigation is too big regardless of how it looks on desktop.

Custom code: when it is worth it and when it is not

Worth it for small, contained changes to styling. Not worth it for adding capabilities the platform deliberately does not have.

Custom CSS to adjust menu spacing, weight or hover behavior is low-risk and generally survives platform updates. Custom JavaScript to build multi-level nesting or a mega menu is a different proposition: it works against the platform’s structure, it breaks when the header markup changes, and it breaks silently, which means finding out from a visitor rather than from a test.

The practical rule is that if the change is cosmetic, custom code is reasonable. If the change adds a navigation capability Squarespace chose not to build, the honest options are to restructure the site or to accept that this platform is the wrong one for that requirement.

Naming menu items so people can use them

Describe the destination in the visitor’s words, not the organization’s. This does more for navigation performance than any structural change.

The most common navigation failure is not layout but vocabulary: menus labeled with internal department names, invented product names, or vague abstractions like Solutions. A visitor scanning a menu is matching words against what they came for, and a label that requires interpretation gets skipped.

The test is whether someone who has never seen the site could predict what sits behind each label. Where a brand name is unavoidable, pairing it with a plain descriptor costs two words and resolves the ambiguity entirely.

When a dropdown is the wrong answer

When the group is small enough to sit at the top level, when the items are unrelated, or when the section really needs a landing page rather than a menu.

Folders are used reflexively to tidy a menu, and tidiness is not the objective. Three related pages usually belong at the top level if there is room; a section with fifteen pages needs a landing page that organizes them properly, because a dropdown of fifteen items is unusable on any device and unreadable on a phone.

Structure before menus

An overloaded menu is a symptom of missing hierarchy, not a navigation problem. See the customization guide.

Working within the platform

One dropdown level, folders as containers, link items for clickable parents. Fighting these produces fragile custom code.

Nothing orphaned

Every page linked from somewhere. Not Linked is for pages you genuinely do not want found.

Mobile checked separately

A menu that works on desktop can be unusable on a phone, and most visitors are on one.

Launch handled properly

Navigation changes at launch are where redirects get forgotten. See publishing a Squarespace site.

Why dropdowns break on mobile

A hover-triggered menu has no hover on touch, so the parent link either fires immediately or the submenu never opens. Deciding which behaviour the parent has is the fix, and it has to be decided rather than inherited.

The depth limit

Two levels is usable; three is not. A navigation needing three levels is describing a structure problem rather than a menu problem.

Frequently asked questions