Mobile Menus and Page Structure for Digital Device Sites: A First Editing Workflow

A useful mobile menu starts with understanding what visitors came to do. It is more important to help them find a key task quickly than to create a long list of menu items. The workflow below assumes a site that sells or introduces digital devices such as smartphones, tablets, or computers.

1. Define the visitor’s first task

Write one sentence describing the site’s main purpose. Make it specific, such as, “Visitors compare earbud features and find purchase information.” Then list around three tasks visitors are likely to perform.

**Hypothetical example:** A tablet site might prioritize “compare devices,” “check compatible accessories,” and “read shipping and exchange information.” This example is only an illustration of structure; it does not describe actual products or operating terms.

• State the most important visitor task in one sentence.
• Note what the site will actually provide: product information, purchasing, or support.
• Do not promise a feature or information in the menu if the site does not provide it.

2. Plan the pages before building the menu

Give each page a clear job: answer one visitor question. Separate a product listing from individual product details. Put information shared across products, such as shipping and exchange instructions, on a dedicated guide page so visitors can find it easily. Draft a page before adding it to the menu; avoid publishing menu items that lead to content that is not ready.

**Hypothetical example:** A “Devices” page could introduce product categories and comparison criteria; a “Product details” page could describe specifications and compatibility for each model; and a “Customer information” page could explain shipping and exchange procedures. Use only information the site actually provides, and do not fill gaps with unverified specifications.

• For each page, write its title and the answer a visitor should get from it.
• Avoid publishing the same information in several places; maintain one page as the source of truth.
• Choose one next action for each page, such as viewing a comparison or finding contact instructions.

3. Keep the mobile menu short and clear

Once page drafts exist, build the menu. Put the most frequently needed items near the top, and use concise labels whose meaning is immediately clear. Instead of a vague label such as “Info,” use one that describes the content, such as “Shipping and exchanges.” Choose menu items based on the visitor’s main tasks rather than listing every page.

TalkTalkMySite supports AI chat and visual editing. You can ask the AI chat for a draft page structure, but do not publish its output without checking it against what the site really offers. Use visual editing to adjust the pages and menu. Do not assume AI output is always accurate or error-free.

• Confirm that every menu item links to a page that exists.
• Check whether visitors can predict the destination from the menu label alone.
• Remove duplicate items that lead to the same page unless there is a clear reason to keep them.

4. Test navigation and the mobile display

Select every menu item and confirm that it opens the correct page. Buttons and instructions inside each page must also match their destinations. For example, check that a “View device comparison” button opens a page that actually provides comparison information. In mobile preview, look for a menu that is obscured, headings that wrap awkwardly, or body text that feels excessively long.

• Open and close the menu on a phone-sized screen.
• Select every menu item and primary button to test its destination.
• Make sure no item leads to a missing page or content that is not ready.
• If possible, check the same navigation flow on a tablet and computer as well.

5. Separate SEO setup from the publishing check

Organize SEO settings after the page structure is stable. TalkTalkMySite Basic supports shared SEO, while Standard supports per-page SEO. Write page titles and descriptions that match the content and purpose of each page, within the options available on your plan. Do not expect a guaranteed search ranking or visitor count. HEAD meta tags work on published sites, while custom scripts run only on connected customer domains. Account for this distinction in your editing plan; do not assume a setting behaves identically in every preview environment.

• Check that each page title and description match its content and purpose.
• Review the mobile menu, links, and wording again before publishing.
• After publishing, open the key pages on the live site and test them there.

For your first task, write down three key visitor tasks and the pages needed to support them. Draft those pages from the list, then connect them in the mobile menu. This order helps you avoid unnecessary menu items and makes the final navigation check more straightforward.