How to Edit a Header and Footer in a Block Theme
A slow, beginner-friendly WordPress guide to edit a header and footer in a block theme, defining the relevant WordPress concepts and checking the real public result.
By the end: You will complete and verify edit a header and footer in a block theme without relying on a three-step generic checklist.
You will complete and verify edit a header and footer in a block theme without relying on a three-step generic checklist.
Key terms before you start
These definitions make the steps easier to follow and help distinguish controls, files and concepts that can look similar at first.
What you need before starting
- Your WordPress /wp-admin/ login
- Permission to use the admin screens named in this tutorial
- A staging/backup plan for site-wide, plugin, theme, code or URL changes
Real-world notes from public discussions
These are tied to public discussions, not invented case studies. Open the source to read the full thread and surrounding replies.
A practical answer is: open Appearance → Editor, select the Header/Navigation block, then use the + control to add the link or menu item and save the site-wide change.
Step-by-step tutorial
Every step is shown below. Work through them in order and use each checkpoint to confirm the result before moving on.
Open the WordPress login address
In your browser enter https://YOURDOMAIN.com/wp-admin/ and sign in.
WordPress Dashboard is private administration; YOURDOMAIN.com must be replaced with the real domain.
Your theme, WordPress version, plugins or role can alter available UI. Confirm whether the site uses a block theme and whether your account has permission before changing architecture.
Check your role/permissions
Look at the left admin menu and confirm the menu items named in this tutorial are available.
Editors, Administrators and custom roles can have different permissions. Missing controls do not automatically mean WordPress is broken.
Your theme, WordPress version, plugins or role can alter available UI. Confirm whether the site uses a block theme and whether your account has permission before changing architecture.
Confirm the site uses a block theme
Click Appearance and look for Editor. A block theme exposes the Site Editor through Appearance → Editor.
If Appearance → Editor is absent, the theme may be classic/hybrid or your role may lack permission. Do not switch themes just to follow a tutorial without a migration plan.
Your theme, WordPress version, plugins or role can alter available UI. Confirm whether the site uses a block theme and whether your account has permission before changing architecture.
Open the Site Editor
Dashboard → Appearance → Editor.
The Site Editor changes templates/site-wide parts, so edits can affect many URLs.
Use the rollback/backup/staging plan rather than stacking emergency CSS/plugin changes on top of an unknown cause.
Open Patterns / template parts
Open Patterns and locate Header or Footer template parts (exact navigation can vary by current version).
Header/Footer are reusable template parts in block themes.
Your theme, WordPress version, plugins or role can alter available UI. Confirm whether the site uses a block theme and whether your account has permission before changing architecture.
Open Header in Edit
Select Header → Edit.
Use List View to understand Groups, Site Logo, Navigation and Buttons before moving anything.
Your theme, WordPress version, plugins or role can alter available UI. Confirm whether the site uses a block theme and whether your account has permission before changing architecture.
Inspect Navigation instead of replacing blindly
Select the Navigation block and identify the menu currently assigned.
Creating a new empty menu can make links disappear.
Your theme, WordPress version, plugins or role can alter available UI. Confirm whether the site uses a block theme and whether your account has permission before changing architecture.
Change one item at a time
Edit logo/link/CTA/spacing, save, then preview.
Small changes reduce site-wide risk.
Use the rollback/backup/staging plan rather than stacking emergency CSS/plugin changes on top of an unknown cause.
Check mobile navigation
Preview phone width and open/close the navigation overlay/menu.
Desktop header correctness does not prove mobile behavior.
Your theme, WordPress version, plugins or role can alter available UI. Confirm whether the site uses a block theme and whether your account has permission before changing architecture.
Edit Footer separately
Return to Patterns/template parts → Footer → Edit.
Footer may contain navigation/legal/contact blocks reused across the entire site.
Test logged out, clear the appropriate cache layer, and inspect whether you edited the template/content item actually used by that URL.
Check legal/contact links
Test Privacy, Terms, email and any glossary/tutorial links after saving.
Footer links are easy to leave stale because they appear site-wide.
Use the rollback/backup/staging plan rather than stacking emergency CSS/plugin changes on top of an unknown cause.
Inspect several templates
Open a Page, Post and 404/search if available.
Template parts can render differently within templates/styles.
Test logged out, clear the appropriate cache layer, and inspect whether you edited the template/content item actually used by that URL.
Check for collateral changes
Visit at least Home plus one normal Page/Post and any template affected by the change.
Site-wide templates/styles can change many URLs at once.
Use the rollback/backup/staging plan rather than stacking emergency CSS/plugin changes on top of an unknown cause.
Record what was changed
Note the WordPress screen, plugin/theme/template and reason in project notes/version control where applicable.
Future maintenance is easier when site-wide changes are traceable.
Your theme, WordPress version, plugins or role can alter available UI. Confirm whether the site uses a block theme and whether your account has permission before changing architecture.
Know whether you are editing one content item, a reusable pattern, a template part, a theme or a plugin before clicking Save.
Concrete examples
Troubleshooting
Your theme, WordPress version, plugins or role can alter available UI. Confirm whether the site uses a block theme and whether your account has permission before changing architecture.
Test logged out, clear the appropriate cache layer, and inspect whether you edited the template/content item actually used by that URL.
Use the rollback/backup/staging plan rather than stacking emergency CSS/plugin changes on top of an unknown cause.
Another maintainer can locate the setting/code.
Continue with these tutorials
Documentation and references
Use these primary and supporting sources to verify current controls, browser behavior and product-specific details.