Dear Pierre,

This feature gives you the flexibility to create a fully customized mobile menu using Divi Builder. The design and structure of your menu are entirely up to you. If you choose not to include the Menu module, the menu tag will not be included. To ensure your layout follows best practices for structured navigation, it’s important to build it accordingly. Similarly, if you don’t add schema markup, it won’t be included in the layout.

Overall, you have complete control over how you design and build this layout, allowing for a personalized and tailored mobile menu experience.

I recently read your article and I’m really excited about its potential! However, I have a few technical questions regarding its implementation, particularly in terms of HTML structure and SEO best practices.

1. Does the module automatically wrap the menu in a tag?

Proper HTML semantics are crucial for both accessibility (screen readers) and SEO. If is not included by default, would you recommend manually wrapping the module inside a element?

2. Will the module follow best practices for structured navigation menus?

For example, will it use and elements for proper hierarchical structuring?

3. Does the module support schema markup for navigation menus?

Structured data (e.g., WebSite and SiteNavigationElement schema) can improve how search engines interpret menus.

4. How will the module impact Core Web Vitals and performance?

Since mobile menus often load dynamically, does this module use efficient loading techniques (e.g., avoiding unnecessary JavaScript render-blocking)?

I appreciate any details you can share regarding these aspects. Thank you in advance for your time, and I look forward to hearing more about this exciting new feature!

Best regards.