Avada Header Not Showing: Layouts, Conditions and the Page That Opted Out

Missing everywhere, on one page, or only on phones

Where the header vanished says more than the fact that it vanished. Gone on a single landing page suggests a deliberate setting someone copied. Gone across every blog post or every product suggests a layout condition. Gone only on phones or tablets points at visibility settings. Gone only in the Spanish version of the site points at translation. Present but blank over a full-width hero suggests a transparent header with nothing to stand out against.

Note the pattern, then open the page logged out in a private window, because a cache can keep serving yesterday's header after you fix today's setting. The general header guide covers the problem across themes; this page follows Avada specifically.

Two header systems, and only one is in charge

Avada can draw a header two ways. The older way is the legacy header, configured in Global Options and adjusted per page in the Header tab of Page Options. The newer way is a Header Layout Section, built with containers and elements in Avada Layouts and attached either to the Global Layout, which covers every page, or to a Conditional Layout, which covers only the pages its conditions match.

Avada's docs are clear on the hand-off. When a Header Layout Section is attached to the Global Layout, the header options in Global Options are no longer available. And when a layout supplies the header, the Header tab in Page Options disappears too. Knowing which system your site uses tells you which half of the causes below to read. If Avada > Layouts shows a header section attached anywhere, you are on the new system, at least for some pages.

First test: is the header in the HTML at all?

Open the broken page, view its source, and search for a word from the menu or the logo's alt text. The result sorts every likely cause into one of two columns and saves you from editing settings that were never the problem.

When the layout never printed a header

An empty section that won the match

Avada's own recipe for a landing page without a header is to create an empty Header Layout Section and attach it to a Conditional Layout limited to that page. It works perfectly, which is the danger: widen that layout's conditions by one checkbox and every matching page loses its header. A second trap comes from the docs too. Once a layout is active, any section you add is live immediately, even while empty, so setting conditions before building the section leaves matching pages blank until you finish it. Check: in Avada > Layouts, open each conditional layout and read its conditions and its header slot.

Conditions that reach too far, or not far enough

Conditions in Avada Layouts can include and exclude, for example all posts except one category. An exclusion ticked on the wrong row, or a condition written for one post type when the page belongs to another, sends a page to the wrong layout. Multilingual sites add a quirk: Avada's WPML instructions say to switch the language selector to All Languages before assigning pages to a layout, and to translate header sections one by one. Check: compare the broken page's post type, category and language against each layout's conditions.

A legacy header switched off on purpose

On a site still using the Global Options header, any page can hide it: Page Options, Header tab, Display Header set to No. Pages duplicated from a landing page, or imported from a prebuilt website, carry that setting with them. Check: open the page's Page Options. If the Header tab is missing, a layout controls the header, so go back to the first cause.

When it printed, but nobody can see it

Header sections are built from containers, and every container has Element Visibility for small, medium and large screens. A desktop header container hidden on small screens, paired with a mobile container that was later deleted, leaves phones with nothing. Sticky headers add Element Sticky Visibility, which can hide elements once the container turns sticky. For a header that shows but whose menu will not open, see Avada mobile menu not working.

Transparency is the subtle one. On the legacy header, Avada's docs say that with the header in the top position and opacity set below 1, the header's background area height disappears and the content beneath slides up behind it. White links over a white section look exactly like a missing header. The same docs note that transparent headers are disabled on archive and search pages, so the header can look different there. If the header is styled oddly rather than absent, stale styles are likely and Avada CSS not updating explains how to clear them.

Bringing the header back without breaking the landing pages

1. 1

   Run the source test

   Logged out, private window. Search the source for menu text to learn whether the header was output.

2. 2

   Map every layout

   In Avada > Layouts, list the Global Layout and each conditional layout with its conditions and its header section. Find the one that matches the broken page.

3. 3

   Fix the match, not the page

   If a landing-page layout is catching too much, narrow its conditions or add an exclusion. If a layout's header slot holds an empty section by mistake, attach the finished Header Layout Section in its place.

4. 4

   Check Page Options on legacy headers

   On the affected page, set Display Header back to Yes in the Header tab, and check the same setting on any page that was copied from it.

5. 5

   Check visibility and transparency

   Open the header section and review Element Visibility and Element Sticky Visibility on every container. On legacy headers, check the opacity and colors against the content behind them.

6. 6

   Clear and confirm

   Reset Avada Caches, regenerate critical CSS if enabled, purge the page cache and CDN, then test a page, a post, an archive and a product on a phone and a laptop.

If the header vanished straight after an update rather than after a layout edit, the cause may be a theme, Avada Core and Avada Builder mismatch; Avada update problems handles that case.

Rules that keep the header where it belongs

• Name layouts by intent. 'Landing pages, no header' beats 'Layout 4' when someone edits conditions in a hurry.
• Build the section first, set conditions last. Avada's docs recommend exactly this order, so nothing matches an empty section.
• Keep a written list of conditional layouts and the pages each one should catch, and test one example of each after edits.
• Retire the legacy header deliberately. Running both systems across different pages is how a site ends up with headers nobody can find the settings for.
• Test new post types and languages. A new custom post type or translation may match no layout you expected.

Our Avada developers can untangle a layout system that grew without a plan, and our hosting and maintenance plans check key templates after each update. For the full list of Avada faults, start at the Avada repair hub.

Five places that can say no to one header

Global Options, the Global Layout, a dozen conditional layouts, each page's Page Options and each container's visibility settings can all decide whether a header appears. Each layer was added to give owners flexibility, and each is a place a header can be switched off without anyone noticing. That is WordPress built from settings rather than code: powerful, and hard to audit. The troubleshooting section shows the same pattern on other themes, and the Avada speed guide covers what all those layers cost in load time.

In a Next.js site, which header a page gets is written in code and reviewed before it ships, so a checkbox cannot quietly remove it from two hundred posts. It costs more to build, and a new header design needs a developer. Our Avada vs Next.js comparison sets out both sides, and migrating from Avada to Next.js explains how layouts and their content come across with every URL kept. Owners then edit pages in Athena CMS, where Argus watches for broken pages. For a fix on the site you have now, our theme repair team is the shortest route.