JetMenu is Crocoblock's mega menu builder for Elementor. It lets you stuff Elementor content blocks into a menu dropdown, add icons and badges, and design hover megapanels that work on desktop and mobile. The trade-off is the same one every mega menu has: visitors who know what they want can find it in two clicks, and visitors who don't, scroll past it entirely. Heat maps usually show that only the top one or two columns of a JetMenu panel get any attention.

SleekAI reads the same navigation tree JetMenu reads: WordPress's wp_term_taxonomy entries for the nav_menu taxonomy, the menu items in wp_term_relationships, and the JetMenu Elementor blocks attached to each top-level item. It also reads the JetEngine CPTs those menu items link to. When a visitor asks the bot where to find something, the bot walks the menu like a person would: top-level category, second-level subcategory, JetMenu mega panel content, and any contextual links to product or article CPTs.

Generic chatbots cannot do this. They either ship with a hard-coded site map or rely on whatever the search index happens to include. Anything inside a JetMenu mega panel, especially custom Elementor content blocks, is invisible to most off-the-shelf bots. SleekAI sees it because it walks the same menu tree WordPress uses to render the menu in the first place.

Mega menus make sense visually: they put a lot of options in a small piece of screen real estate, organized into clear columns and icons. The problem is that visitors only scan a fraction of any given panel. Eye-tracking research consistently shows that the top-left and top-center of a mega menu get most of the attention, while the right two columns get a few hundred milliseconds at most.

On a JetMenu with five columns and three rows per column, that means 60 to 70 percent of the items go effectively unseen. A chat surface fixes that by accepting natural language and routing to the right destination directly. Visitors no longer need to know that the menu thinks of tents under Camping rather than Backpacking, or that the third column of the Climbing panel has a Beginners section.

They ask, the bot answers. SleekAI does this without forking the menu data into a second system. It reads the same nav_menu taxonomy WordPress renders from, walks the same JetMenu mega panel blocks, and follows the same links into JetEngine CPTs that the menu itself uses.

That means there is exactly one source of truth, and changes to the menu structure show up in the bot's answers without any rebuild. For Crocoblock sites with deep navigation hierarchies, that consistency is what makes the chat surface usable in the first place.