Pro Features

Mega-Menu & Schema.org Pro

April 10, 2026 docsadmin 4 min read

Two features for sites that have outgrown the basic five-link top nav and want stronger search-engine visibility: a multi-column mega-menu, and Schema.org Pro markup that emits structured data for each counsel, an FAQ block, and the firm’s testimony.

Mega-Menu

The default Legal theme uses a single-row top navigation. That works well for firms with 4–6 navigation items, but breaks down for firms with deep practice areas — where you might want to expose every practice category on hover from the “Practice” item.

Enabling the mega-menu

  1. Go to Appearance → Customize → Legal Pro → Mega-Menu.
  2. Enable Mega-Menu on Primary Nav.
  3. Set Columns per Mega Panel — between 2 and 4. Three is the default and reads well at most viewport widths.

Building the menu

Mega-menus work with WordPress’s standard menu editor — no custom UI to learn.

  1. Go to Appearance → Menus.
  2. Open your Primary menu.
  3. For top-level items that should have a mega-panel (typically “Practice” or “Services”), add child items directly under them — drag-and-drop indents them.
  4. Save.

The mega-menu walker takes over rendering. Top-level items with children get a wide multi-column panel on hover. Top-level items without children render as plain links — no panel.

Each mega-panel can have one “featured” item — typically a calls-to-action like “Latest case study” or “Schedule a consultation”. The featured item:

  • Spans all columns at the top of the panel
  • Renders the menu item’s description field as a lede paragraph below the title
  • Shows in italic Fraunces, oxblood-accented

To mark an item as featured:

  1. In the Menus editor, click the menu item to expand its details.
  2. If Description isn’t visible, click Screen Options at the top right and check “Description”.
  3. Tick the new checkbox Mega: Featured (highlights this item with its description text as a lede).
  4. Add description text — this becomes the lede paragraph.
  5. Save the menu.

Mobile behavior

On mobile (under 768px), mega-panels collapse into a single-column accordion. The featured item still renders with its lede, but as a stacked block rather than a header.

Schema.org Pro

The free Legal theme outputs LegalService structured data in <head> on the front page — basic firm name, URL, and address if configured. Pro extends this with three additional schema types: Attorney (per counsel), FAQPage, and Review (from the testimony block).

Search engines use this structured data to enrich how your site appears in results — counsel names with photos in knowledge panels, FAQ snippets with expandable answers, star-rating displays, and so on.

Attorney schema (per counsel)

Automatically emitted for each counsel filled in under Customize → Counsel. For each counsel with a name, the plugin emits a JSON-LD block like:

{
  "@context": "https://schema.org",
  "@type": "Attorney",
  "name": "Anaïs R. Mehta",
  "jobTitle": "Founding Partner",
  "description": "Civil litigation, with a focus on contracts and commercial disputes...",
  "worksFor": {
    "@type": "LegalService",
    "name": "Lex & Co.",
    "url": "https://example.com"
  }
}

If you’ve uploaded a counsel image, it’s added as an image property. If you’ve set a counsel URL (like a longer profile page), it’s added as url.

FAQPage schema

Pro lets you author up to six question/answer pairs in the Customizer. They emit as a single FAQPage block with all six entries.

  1. Go to Customize → Legal Pro → Schema.org Pro.
  2. Enable FAQPage Schema.
  3. Fill in pairs Q1/A1 through Q6/A6.

The FAQs you author here are schema-only — they don’t render anywhere on the front-end. They exist purely to feed search engines structured FAQ content. If you want to display the FAQs visually, do it via the block editor on a page (separately).

Common FAQs for legal practice sites:

  • “What is the consultation process?”
  • “How are fees structured?”
  • “Do you take cases on contingency?”
  • “What’s the geographic scope of your practice?”
  • “How do I prepare for an initial consultation?”
  • “What’s covered under attorney-client privilege?”

Review schema

If you’ve configured the testimony block in the Customizer, Pro automatically emits a Review schema block:

{
  "@context": "https://schema.org",
  "@type": "Review",
  "reviewBody": "When our shareholder dispute went sideways...",
  "author": {
    "@type": "Person",
    "name": "Founder & CEO — GROWTH-STAGE FINTECH · MUMBAI · 2024"
  },
  "itemReviewed": {
    "@type": "LegalService",
    "name": "Lex & Co.",
    "url": "https://example.com"
  },
  "reviewRating": {
    "@type": "Rating",
    "ratingValue": "5",
    "bestRating": "5"
  }
}

The review rating is hard-set to 5 of 5 — testimony on your own site is by definition a positive review. If you have specific concerns about misrepresentation, disable Review schema in the Customizer settings.

Where schema appears

All three Pro schema types output on:

  • The front page
  • Any page using the template-firm.php template

They don’t output on regular pages, single posts, or archives — keeping the schema scoped to the firm-info page where it makes sense.

Validating schema

Use Google’s Rich Results Test: https://search.google.com/test/rich-results. Paste your home page URL and run the test. You should see Attorney entries, optionally FAQPage and Review depending on what you’ve configured.

If something fails validation, the most common cause is a malformed customizer value — for example, an unclosed HTML tag in a counsel bio. The schema generator strips most HTML, but bad input can still produce malformed JSON.

Leave a comment