When an anchor link scrolls to the correct section but its heading sits behind a sticky header, the target is present and the scroll offset is wrong. Measure the overlap and adjust the target's scroll spacing. Do not move every section down or remove the header to hide the symptom.
Prove that the link reaches the intended target
Inspect the link fragment, such as #pricing, and confirm that exactly one intended element has that ID. A typo, repeated ID or link pointing to another page is not an offset problem. In Elementor, the Menu Anchor documentation describes the anchor identifier and link relationship.
Test the published page while signed out. An editor preview or the logged-in WordPress toolbar can change the visible header height. Record whether the header shrinks after scrolling and whether mobile uses a different header.
Measure before choosing an offset
At the point where the section lands, measure the space occupied by the sticky header. Add a small intentional reading gap, not an unexplained large negative margin. For illustration, a 72-pixel header plus a 16-pixel gap requires 88 pixels of clearance.
The CSS scroll-margin-top property can provide target spacing for native scrolling. This example is scoped to a single target:
#pricing {
scroll-margin-top: 88px;
}
@media (max-width: 767px) {
#pricing {
scroll-margin-top: 72px;
}
}
These numbers are illustrative. Replace them with the measured clearance for your layout. If a builder runs its own scrolling script, verify whether its calculation respects this CSS before adding another offset.
Target ID: Unique and matches the link. Desktop landing: Heading clears sticky header. Mobile landing: Menu closes, content readable. Direct fragment: Same result after a fresh load. Explanatory checklist, not a customer test result.
Avoid stacking several competing fixes
Check for existing scroll-padding on the scroll container, an anchor pseudo-element, theme smooth-scroll settings and custom JavaScript. Multiple offsets can produce an excessive gap or a jump after the first scroll.
On staging, choose one owner for the behavior. Prefer a scoped supported setting or CSS rule. Do not use a huge invisible element that sits over links or form fields. A section that looks correctly positioned but blocks pointer input is still broken.
If the header itself is malformed, start with the Avada header repair guide. Scroll spacing cannot fix duplicated header markup or the wrong active template.
Test more than a menu click
Open the full page URL with its fragment directly, click the navigation link from the top, repeat after scrolling down, and use browser back. Test desktop and mobile with the menu closed after selection. Check keyboard navigation and ensure the target heading remains readable.
Also test a target near the bottom of a short page. The browser may lack enough remaining scroll distance to place that target at the same position as an earlier section; that is different from a failed link.
Provide the published URL, target ID and two affected viewport sizes to HandL WP for a scoped navigation fix. Keep the fix attached to the actual header behavior rather than a site-wide collection of compensating margins.
References reviewed October 5, 2026. Examples are explanatory, not customer test results.