Skip to content

Navigation, pages & blog

Your store’s content lives in two places in the admin sidebar. Knowing which section holds what saves a lot of clicking:

  • Content holds your Blog Posts, Blogs, Metaobjects, Files, and Menus.
  • Online store holds your Themes, Pages, and Filter & Search.

So menus and the blog live under Content, while pages and themes live under Online store. This guide covers menus, pages, and the blog.

Menus (sometimes called linklists) control your store’s navigation. Each menu has a handle that your theme references — the default theme reads main-menu for the header and footer for the footer. When you add a menu link list block in the visual editor, you point it at one of these handles.

Open Content → Menus to manage them. The handle is generated from the menu title (and made unique per store) — you can edit it, but keep main-menu and footer intact so your theme keeps finding them.

Build a menu

  1. Click Add menu item to add a row.

  2. Type the menu item title — this is the visible label buyers see.

  3. Click the link field and pick where it points from the dropdown. You don’t have to memorize URLs — the picker offers every destination type for you.

  4. Repeat for each item, then save.

The link picker covers these destinations. Most are pickable from a single search box:

  • Home — your storefront home page.
  • Search — the search results page.
  • Collections → All collections, or a specific collection.
  • Products → All products, or a specific product.
  • Pages — any custom page you’ve published.
  • Blogs — a blog section (its listing page).
  • Policies — any active policy from Settings → Policies (see Policies).
  • Customer Account, Customer Orders, and Account Settings — the logged-in buyer’s account pages.
  • An external URL — just paste any web address into the link box and choose the External URL option that appears.

To link a single blog article, point the menu item at its blog section and let buyers browse to the post, or paste the post’s full URL as an external link.

Reorder and nest

The menu editor is drag-and-drop:

  • Drag up or down to reorder items.
  • Drag an item to the right to nest it under the item above, creating a dropdown or mega-menu group. You can also use the Add child action on a parent.
  • Nesting goes up to three levels deep (a top-level item, a child, and a grandchild). The editor stops you from nesting deeper.

The active link is highlighted automatically when a buyer is on the matching page. How dropdowns and mega-menus actually render is up to your theme — the menu only stores the structure.

Pages

Pages hold evergreen content: About, Contact, FAQs, size guides, store policies that aren’t legal documents, and so on. Manage them under Online store → Pages.

  1. Click New page and enter a page title.

  2. Write the body in the rich-text editor. You can format text, add images, and use the AI assist button to draft content from a prompt.

  3. (Optional) Open the Metafields section to attach metafields — useful for structured fields your theme reads.

  4. Open the Search Engine Optimization section to set a meta title (kept under 70 characters) and meta description (under 160). Set the URL handle here too, or leave it blank to auto-generate one. The page lives at /pages/your-handle.

  5. In the right-hand panel, choose a visibility status:

    • Hidden — saved but not visible to buyers (the safe default).
    • Visible — live immediately.
    • Scheduled — set a future date and time; the page goes live then, in your store’s timezone.
  6. (Optional) Pick a template from the dropdown. The default works for most pages; choose an alternate template only when a page needs a different layout.

  7. Click Create page (or Save changes).

Legal documents — refunds, privacy, terms, shipping — have a dedicated home under Settings → Policies so checkout can link them automatically. Don’t recreate those as plain pages; generate starting drafts with the free policy generators instead. See Policies.

Blog

The blog is built in. It has two layers:

  • A Blog is a section — a container like News, Recipes, or Buying Guides. It holds the comment setting and an optional template for its posts.
  • A Blog post is an article that lives inside one blog section.

You create the section first, then write posts into it.

Create a blog section

  1. Go to Content → Blogs and click to add a new blog.

  2. Enter a title (this becomes the section’s handle, part of every post URL underneath it).

  3. Choose a comment setting (see Comments below).

  4. (Optional) Set a featured image, SEO fields, a template, and metafields.

  5. Save.

Write a blog post

Go to Content → Blog Posts → New post.

  1. Enter a post title.

  2. Set the web address (handle), or use the Use title button to generate one. The preview shows the final URL: /blogs/{blog-handle}/{post-handle}.

  3. Choose the blog section this post belongs to, and the author. The author dropdown lists your staff accounts, so different team members can be credited on different posts. It defaults to you.

  4. Write the content in the rich-text editor (with AI assist available). Add an optional excerpt — a short summary used on cards, email previews, and search snippets.

  5. Under Media and tags, pick a featured image or video from the media library and add comma-separated tags (for example seasonal, gifts, beginner tips). Tags group related posts and power tagged blog feeds.

  6. In Publish settings, choose:

    • Draft — saved, not visible (the safe default).
    • Publish now — live immediately.
    • Schedule for later — pick a future date and time.
  7. (Optional) Open Search and discovery for SEO title/description, Appearance for a custom theme template, and Custom data for metafields.

  8. Click Create post.

Published posts appear at /blogs/{blog-handle}/{post-handle} and in your theme’s blog sections. Each blog section also exposes an Atom feed at /blogs/{blog-handle}.atom, and buyers can browse a single tag at /blogs/{blog-handle}/tagged/{tag}.

Comments

Comment behavior is set per blog section, not per post. When editing a blog, pick one of three modes:

Review comments before publishing — the default and the right choice for most stores. New comments are held and do not appear until you approve them. Spam never goes live on its own.

On the storefront, a comment form collects the buyer’s name, email, and message — all three are required, and the email must be valid. Behind the scenes every comment carries a status: it starts as pending when the blog is set to review-before-publishing, becomes approved automatically when the blog auto-publishes, and can also be marked rejected or spam. Only approved comments render to other buyers.

Next steps