The fictional Willow Reach Gardens is promoting an evening opening. The event page can keep the full garden-site header, navigation, and footer. It can keep a smaller bar, with the logo and a way back, and a short footer for contact and policy links. Or it can set the shared chrome aside, and use a campaign-specific presentation built around the evening only.
Decide whether this campaign destination should keep the main site’s chrome, use a reduced version, or set that chrome aside. The third option is a campaign-specific presentation without the shared header, navigation, and footer, not merely a different address that still carries the main site chrome. A site can use more than one pattern, and it is the marketer’s call.
The Willow Reach example is fictional, not a test result.
Decide the Surrounding Navigation, Not the Whole Site’s Purpose
In this guide, chrome means the shared surroundings of a page: the header, the main navigation, and the footer. The question is whether a campaign page keeps those, reduces them, or sets them aside.
For the sitewide purpose, use Brochure Site or Task-Led Site?. Here, decide which parts of the header, navigation, and footer support this campaign visit.
Compare the Three Options Against the Promised Destination
Start from the promise the visitor arrived with, and the one action the page is there to support. Then use this matrix as reviewer questions, not as a finding that one option always works.
| Question | Same chrome | Reduced chrome | Chrome set aside |
|---|---|---|---|
| Will the visitor still recognize the organization? | The full header and footer already carry the brand | A logo and a short footer can be enough | The page still needs to look like the same organization |
| Which routes do they actually need? | Full nav is useful if they may continue into the main site | Keep the routes that help this visit, such as a way back, contact, and policy links | You will have to provide any route they still need on the page itself |
| Does the chrome help or fight the action they came to do? | A full nav can help, or it can pull them away | A smaller bar leaves more room for the event | A tighter page can stay focused, but it can also feel stranded |
Nielsen Norman Group, in 2014, says the destination page should fulfill what the anchor text promises, and that broken promises erode trust. In 2020, they describe information scent as the cues that tell people whether a path will lead to what they want. Applying those ideas to an advertisement or an email, and to the page it opens, is our use of the principle, not a study of ads. Ask whether the Willow Reach evening page delivers what the invitation promised, and whether the chrome supports that or talks over it.
Make the Navigation Trade-Off Explicit
Nielsen Norman Group’s 2024 homepage principles say every page should include both implicit and explicit links to the homepage, such as a logo and a Home link. In one example, a plan-selection page without a way home left customers feeling trapped. That advice sits in tension with a chromeless campaign page. Treat it as a trade-off, not a ban. If you reduce or remove the main navigation, decide whether a way back to the main site still belongs on the page, and make that decision visible in your note.
WCAG 2.2 Success Criterion 3.2.3 Consistent Navigation, at Level AA, asks that navigational mechanisms repeated on multiple pages in a set of pages appear in the same relative order each time, unless the visitor changes that order. It applies within a set of web pages: pages that share a common purpose and are created by the same author, group, or organization. The Understanding page gives a checkout with its own template as an example that is not part of the product pages’ set. Whether a campaign page is a separate set is a question for a specialist, not a verdict you can reach from a preview. Do not write that the page passes or fails this criterion.
How to Check Visual Consistency Across Your Website can help you judge whether the campaign page still looks like the same organization, even when the chrome is reduced. If a header stays on the page, Should Your Header Stay Visible While You Scroll? covers whether it should remain visible while people scroll.
Review the Campaign Page Beside Its Main-Site Context
Paste the campaign address into Online Website Previewer and press Preview. Note the header, navigation, and footer. Then preview the main-site address and compare it with your notes. Compare them at 390 by 844, 820 by 1180, and 1920 by 1080 CSS pixels, the tool’s phone, tablet, and desktop sizes. Keep notes as you switch from one address to the other. Look at what chrome is present, whether the organization is still recognizable, and which routes remain.
Each frame loads the live page, not a screenshot. You can scroll, follow links, and fill in forms, and those actions are real, so the previewed site receives the visit. Arrange a safe test path before you interact with a form. Password-protected campaign pages often will not preview. A staging or test address works like any other site if your browser can reach it and the site allows previews.
A useful note might say: “On the Willow Reach evening-opening page at [address], in the 390 by 844 preview, compared with the main garden site, the full header and nav sit above the booking details, and I cannot see a way back to the gardens except inside that full menu. Please try a reduced bar with the logo, a way back, and a short footer for contact and policy links, so the page still looks like Willow Reach without carrying the whole site menu.”
Once the chrome is chosen, use the campaign landing page section of How to Test Your Website Before Launch for the broader pre-launch review.
Keep the Search-Status Note Small
Brochure-style sites often also have a separate set of ad landing pages, each built for a narrower path, and those pages are often kept out of search engine results. That is practical guidance from experience, not a published finding.
Google’s documentation describes noindex as a rule set with either a meta tag or an HTTP response header, used to prevent indexing by search engines that support the rule, and says that when Googlebot crawls the page and extracts the tag or header, Google will drop that page entirely from Google Search results. This guide does not advise whether to use that rule, or how to implement it.



