- Published
- Byline
- GoHighLevel Partners Editorial
- Filed under
- GoHighLevel Automation
A global block is a shared dependency, and shared dependencies behave differently from copies in ways that only show up later.
Global sections page builder: one block, edited once, everywhere
A global section is a block of page content that exists once and appears on many pages, so that editing it in one place changes it in all of them. The appeal is obvious on a site of twenty pages carrying the same call-to-action band. What is less obvious is what it costs — a global block is a shared dependency, and shared dependencies behave differently from copies in ways that only show up later.
This is about those mechanics: how propagation actually works, what an override does to it, and how to decide which blocks deserve to be global at all. The specific case of the top and bottom of every page is covered in a reusable header and footer; almost everything here applies to the blocks in between.
Global, template, and the difference that matters
| A saved template | A global section | |
|---|---|---|
| What is stored | A pattern to start from | The block itself |
| After you place it | The page owns a copy | The page holds a reference |
| Editing the original | Affects nothing already placed | Affects every page at once |
| Editing on a page | Local, and expected | Either edits everywhere or breaks the link |
| Deleting the original | Placed copies survive | Depends on the platform — check before you rely on it |
saving a section to the library gives you the first. The second is a stronger commitment and is not always what people mean when they ask for a reusable block, so it is worth establishing which one a client is describing before building it.
What deserves to be global
The test is whether the block ever legitimately differs between pages. If the answer is no, make it global and stop maintaining copies. If the answer is sometimes, a template is safer, because the exception will arrive and an override on a global block is where the confusion starts.
Good candidates are the contact band, the legal and disclosure block, a consistent testimonial strip, a standard trust row. Poor candidates are anything carrying a page-specific promise: an order bump belongs to its checkout position, and a countdown timer, only where the deadline is real should reflect a deadline that is real for that offer rather than a shared countdown running everywhere.
Overrides, and why they cause the most confusion
Platforms differ in what happens when someone edits a global block on one page. Some prevent it. Some apply the edit everywhere, surprising whoever made it. Some silently detach that instance so the page keeps its own version and stops receiving updates — which is the worst of the three, because the page looks correct today and quietly drifts from then on.
Find out which behaviour yours has before rolling global sections out across a client site, and write it in the handover notes. The failure mode is not technical: it is a client editing one page, believing they changed one page, and either changing all of them or creating a copy nobody knows is a copy.
Responsive settings travel with the block, and that is a benefit
Because there is one block rather than many, its behaviour at each screen size is settled once. That is a real saving, and it also concentrates the consequences: an error at one breakpoint is on every page rather than one. Settle row and column width settings inside the block first, then check what the tablet view inherits, which is the view least likely to be looked at and most likely to be inherited from a value someone set elsewhere.
Type is the same story. A global block using uploading a brand typeface renders consistently everywhere, which is the point, and a weight that was never uploaded will be synthesised everywhere too.
Performance, and the block that quietly loads on every page
Anything in a global section is on every page that uses it, so its weight is multiplied by the site. A background image chosen for a homepage band, a decorative animation, an embedded video: each is fine once and expensive repeated. a page speed score is where this shows up, usually as a puzzle, because the heavy element is not on the page anyone is looking at — it is in a block that appears on all of them.
The upside is symmetrical. Fixing it once fixes it site-wide, which makes a global section the most efficient place to spend an optimisation.
What happens when pages move
Global sections are usually scoped to a container — a funnel, a site, an account — and moving a page out of that scope is where the reference breaks. copying a step into another funnel carries the page and not necessarily the link to a global block defined in the source funnel, and moving pages into a website container raises the same question at larger scale. a funnel template import is the reverse case: a template arriving with its own blocks, which may or may not merge with the ones you already have.
The practical habit is to check the global blocks explicitly after any move, rather than checking the page looks right. A detached block looks right on the day it detaches. That is the entire problem with it.
Testing, and one thing not to do
Do not run split testing a funnel step on a global section. Whatever you change is changed everywhere it appears, so the variant is not confined to the page under test and the comparison measures nothing. If a block is worth testing, take a local copy on the page you are testing, detach it deliberately, and put the winner back into the global version afterwards.
A last note on structure: some elements are easier to make global than others. an accordion faq block is a good example, since a shared question set genuinely belongs in one place — but only if the answers are true on every page it appears on. A global block whose content is right for most pages and wrong for two is a block that will be overridden twice, and those two overrides are the ones nobody will remember in six months.
Frequently Asked Questions
What is the difference between a global section and a saved template?
A template is a pattern to start from: the page owns its copy and later edits to the original change nothing. A global section is the block itself, referenced by each page, so one edit changes every page that uses it. They are often confused, and the choice determines whether exceptions are easy or dangerous.
Which blocks should be global?
Those that never legitimately differ between pages — a contact band, a legal block, a standard trust row. If a block sometimes needs to differ, use a template instead. The exception will arrive, and an override on a global block is where the confusion starts.
What happens if someone edits a global section on one page?
It depends on the platform, and you need to know which behaviour yours has. Some block the edit, some apply it everywhere, and some silently detach that instance so the page keeps a private copy and stops receiving updates. The third looks correct today and drifts from then on.
Do global sections affect page speed?
Their weight is multiplied by every page that uses them, so a heavy background or an embedded video inside one is expensive site-wide. It shows up as a puzzle because the heavy element is not on the page being examined. The upside is that fixing it once fixes it everywhere.
Can I split test a global section?
Not usefully. Any change appears on every page using the block, so the variant is not confined to the page under test and the result measures nothing. Detach a local copy on the page you are testing, run the test there, and fold the winner back into the global version.
Do global sections survive when I move a page?
Often not, because they are scoped to a funnel, site or account and the reference does not necessarily follow the page out of that scope. Check the global blocks explicitly after any move rather than checking the page looks right, since a detached block looks right on the day it detaches.
What should I tell a client about global sections at handover?
Which blocks are global, what happens when they edit one, and that an edit intended for a single page may change every page or silently create a private copy. This is not a technical problem so much as an expectation one, and it is cheap to prevent with two sentences in the notes.
We build your GoHighLevel account for you
CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.
- Setup (one-time)$850
- Ongoing (per month)$38.80
No obligation quote · reply within 1 business day
This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.