Support

WordPress Site Editor: How to Customise Your Whole Site

Illustration of a man using the WordPress Site Editor to customise site-wide layouts, colours, styles, templates and responsive design settings.

The WordPress Site Editor gives you a visual way to customise parts of your website that used to depend heavily on your theme.

Instead of only editing the content inside a page or post, you can work on site-wide elements such as templates, headers, footers, navigation, colours, typography and other design settings.

This makes it possible to manage much more of your website using the same block-based approach WordPress uses for content.

The Site Editor is not available on every WordPress website, though. It is designed for block themes, so what you see in your dashboard depends on the theme your site is using.

In this guide, you will learn what the WordPress Site Editor does, how it differs from the Block Editor, and how to use its main features without accidentally changing more of your website than you intended.

What Is the WordPress Site Editor?

The Site Editor is the WordPress interface for managing the broader structure and design of a website that uses a block theme.

You can normally open it from:

Appearance > Editor

From there, WordPress can give you access to areas such as:

  • Styles
  • Pages
  • Navigation
  • Patterns
  • Templates

Depending on your WordPress version and theme, you may also see other site-wide controls.

Older WordPress guides often refer to this approach as full-site editing or FSE.

That term describes the broader idea of using blocks to customise much more of a WordPress website. The actual interface you use is now generally called the Site Editor.

Site Editor vs Block Editor

The Site Editor and Block Editor both use blocks, which makes their names easy to confuse.

The difference is mainly about what you are editing.

The Block Editor is used primarily for the content inside an individual page or post.

The Site Editor is used for the wider structure and design around that content.

For example:

Block Editor tasks:

  • writing page content
  • adding headings
  • inserting images
  • creating lists
  • adding buttons
  • arranging content blocks

Site Editor tasks:

  • changing a header
  • editing a footer
  • adjusting site-wide colours
  • changing typography across the website
  • managing navigation
  • editing the template used by blog posts
  • changing the layout of archive or search pages

If you are learning how to edit the content inside a page or post, start with our beginner’s guide to the WordPress Block Editor.

Does Your WordPress Site Support the Site Editor?

The Site Editor is available when your website uses a block theme.

A quick way to check is to look under Appearance in your WordPress dashboard.

If you see:

Appearance > Editor

your active theme supports the Site Editor.

If you do not see that option, your site may be using a classic theme or another setup with different customisation tools.

That does not mean anything is wrong with the website.

Classic themes can still use tools such as:

  • the Customizer
  • theme-specific settings
  • widget areas
  • menu settings
  • page builders
  • custom theme options

The right editing method depends on how the site was built.

Do not change themes simply because you want access to the Site Editor. Switching themes can affect layouts, styling, widgets, navigation and other parts of an existing website.

If you are considering a change, our guide to choosing the right WordPress theme explains what to check first.

How to Open the WordPress Site Editor

If your active theme supports it, go to:

Appearance > Editor

The Site Editor opens with a visual view of your website and access to its main site-wide editing areas.

The exact layout can change between WordPress versions, but the main principle remains the same.

You are working with parts of the website that can affect more than one page.

That makes the Site Editor powerful, but it also means you should understand what you have selected before saving a change.

Understanding the Main Site Editor Areas

The Site Editor brings several types of website management into one interface.

The main areas you are likely to use are Styles, Pages, Navigation, Patterns and Templates.

Each solves a different problem.

Styles: Change the Look of Your Site

Styles controls the broader visual appearance of your website.

Depending on the theme, you may be able to adjust:

  • typography
  • colours
  • layout
  • spacing
  • block appearance
  • style variations

Changes made here can affect the entire site rather than one individual page.

For example, changing the default text colour through Styles may affect text across posts, pages and templates.

You can also adjust the default appearance of particular block types.

You might change how all Buttons look or adjust the typography used by Heading blocks across the website.

This is different from selecting one Heading block inside a page and changing only that instance.

Be Careful with Site-Wide Style Changes

The main advantage of Styles is also the main reason to be careful with it.

A single change can affect many pages at once.

Before saving, consider whether you want to change:

  • one block
  • one page
  • one template
  • one block type everywhere
  • the entire site

If you only want to alter one page, a global Style setting may be the wrong place to make the change.

For a broader look at the different ways WordPress themes can be changed, see our guide to customising a WordPress theme safely.

Templates: Control the Structure Used by Pages

Templates define the wider structure used to display different types of content.

A block theme may include templates for areas such as:

  • single posts
  • individual pages
  • archives
  • search results
  • 404 pages
  • the homepage
  • blog listings

A template can include structural blocks for things such as:

  • headers
  • post titles
  • featured images
  • post content
  • metadata
  • footers

This lets you control the layout surrounding the actual content.

Understand the Difference Between Content and a Template

This distinction is one of the most important things to understand in the Site Editor.

Imagine you have 100 blog posts that all use the same Single Post template.

Changing the text inside one blog post changes that one post.

Changing the Single Post template can change the layout used by all 100 posts.

Before editing something in the Site Editor, check whether you are changing the content itself or the template that displays it.

How to Edit a Template

Open Templates in the Site Editor.

You will see the templates currently available from your theme along with any custom templates that have been created.

Choose the template you want to inspect.

You can then edit its blocks in much the same way as other block-based WordPress content.

For example, you might:

  • move the Post Title
  • change where the featured image appears
  • add or remove metadata
  • adjust spacing
  • change the header or footer being used
  • modify the structure surrounding the content

Preview the result carefully before saving.

If a template is already being used across a large part of the site, even a small change can have a wide effect.

Template Parts: Headers, Footers and Reusable Structure

Template parts are reusable structural sections that can be included in templates.

The most common examples are:

  • headers
  • footers

A website may also use template parts for other repeated structural areas.

In current versions of the Site Editor, template parts are managed within Patterns.

Go to:

Appearance > Editor > Patterns

You can then find the available template parts.

Why Template Parts Matter

A header may be used by several different templates.

Instead of editing a separate copy of the header in every template, WordPress can reuse the same template part.

That keeps the site more consistent.

It also means changing that template part can affect every template that uses it.

If you edit the main header, check the website afterward to make sure the change works across different types of pages.

How to Edit Your Header or Footer

Open Patterns in the Site Editor and find the relevant template part.

Depending on the theme, this might be named something simple such as:

  • Header
  • Footer

Open the part you want to edit.

Because template parts are made from blocks, you may be able to change elements such as:

  • site logo
  • site title
  • navigation
  • buttons
  • social icons
  • columns
  • text
  • spacing

Save the changes only when you are comfortable that they should apply wherever that template part is used.

Patterns: Reuse Layouts and Content Structures

Patterns are arrangements of blocks that can help you build sections more quickly and consistently.

Your theme may provide its own patterns, and you can also create your own.

For example, a pattern might contain:

  • a heading and introduction
  • an image with supporting text
  • a call-to-action
  • a group of columns
  • a promotional section

The Site Editor’s Patterns area can include theme patterns, your own patterns, synced patterns and template parts.

Not all of these behave in exactly the same way.

A normal pattern can be used as a starting point and then edited independently.

A synced pattern is designed to remain consistent wherever it is used.

Template parts are intended for reusable site structure such as headers and footers.

Before editing reusable content, check what type of item you are working with and where else it may appear.

Navigation: Manage Your Website Menus

The Site Editor can also be used to manage navigation menus on a block-theme website.

Open:

Appearance > Editor > Navigation

From there, you can review the menus available on the site and make changes such as:

  • reordering items
  • removing links
  • renaming menus
  • creating submenus
  • opening pages linked from the menu

More detailed changes may take you into the Navigation block itself.

Creating a Menu Does Not Automatically Display It

A saved navigation menu still needs to be used by a Navigation block somewhere on the site.

For example, your Header template part might contain a Navigation block that is connected to your main menu.

This distinction matters if you create or edit a menu but cannot see the expected result on the front end.

Check:

  1. the menu has been saved
  2. a Navigation block exists in the relevant template or template part
  3. the correct menu is selected by that Navigation block
  4. the template or template part has been saved

If you specifically need to create nested menu items, our guide explains how to create a WordPress dropdown menu without code.

Pages in the Site Editor

WordPress can also let you access and manage pages from within the Site Editor.

This can be useful because it lets you see page content in the context of the template surrounding it.

You may be able to:

  • browse pages
  • open a page
  • create a page
  • edit page content
  • inspect the template being used

This overlap can initially make the Site Editor and Block Editor seem like the same thing.

They are still solving different problems.

If you are simply writing or formatting page content, the Block Editor workflow is usually the more useful concept to learn.

Use the Site Editor when you need to understand or modify the wider structure around that content.

Use List View When the Layout Gets Complicated

Site Editor layouts can contain deeply nested blocks.

A header alone might contain:

  • a Group
  • a logo
  • a Navigation block
  • buttons
  • additional Groups or Rows

Selecting the correct element visually can become difficult.

List View shows the block structure and makes it easier to understand how everything fits together.

Use it to:

  • select nested blocks
  • see which blocks are inside other blocks
  • rearrange elements
  • identify template parts
  • understand complicated layouts

If you are unsure what you are about to move or delete, List View is often safer than clicking around the visual preview.

Preview Before Saving Site-Wide Changes

A Site Editor change can have a wider impact than a normal page edit.

Before saving an important change, review what is being modified.

WordPress may show several items in the save confirmation when your work affects multiple areas.

Read that list rather than confirming automatically.

After saving, check the front end of the site.

For an important structural change, test several types of page rather than only the screen you were editing.

For example, check:

  • the homepage
  • a standard page
  • a blog post
  • an archive
  • navigation
  • mobile layouts
  • the footer

This is particularly important after editing templates, template parts or global Styles.

Common Site Editor Mistakes to Avoid

The Site Editor becomes easier to use once you understand the scope of each change.

A few mistakes are especially common.

Editing a Template When You Meant to Edit One Page

A template can control many pages.

If you only want to change one page’s content, make sure you are editing the page rather than the shared template.

Changing Global Styles for a Local Design Problem

A site-wide typography or colour setting can affect far more than the section you are looking at.

Use global Styles when you actually want a global change.

Editing a Header Without Checking Other Templates

A shared Header template part may appear across the whole website.

Check several pages after making structural changes.

Changing Themes Just to Access the Site Editor

A block theme unlocks the Site Editor, but changing an established site’s theme is a much bigger decision than enabling a new editing screen.

Review the existing design, functionality and compatibility first.

Saving Several Changes Without Reviewing Them

The Site Editor can collect changes across templates, Styles and other areas.

Review the save confirmation so you understand what is being updated.

Treating the Site Editor Like a Page Builder

The Site Editor can create sophisticated layouts, but that does not mean every design needs layers of Groups, Rows, Columns and custom settings.

Keep the structure as simple as the design allows.

Simpler layouts are generally easier to maintain later.

What If You Cannot Find a Setting?

Not every block theme exposes exactly the same design options.

A setting shown in one tutorial may not exist in your theme, or the theme may deliberately restrict certain controls.

Plugins can also add their own blocks and settings.

If a control is missing, first establish whether the change belongs to:

  • page content
  • a template
  • a template part
  • global Styles
  • the theme itself
  • a plugin

Avoid adding random CSS or another plugin until you understand where the setting should live.

Should You Use the Site Editor?

If your website already uses a well-built block theme, the Site Editor can be a useful way to manage site-wide design without working directly with theme files.

It is particularly useful for tasks such as:

  • changing global styles
  • updating headers or footers
  • adjusting templates
  • managing navigation
  • building reusable structural elements

That does not mean every existing WordPress site should move to a block theme.

If your current theme and editing workflow already suit the site, there may be no reason to change them simply to gain access to the Site Editor.

The important thing is to use the editing system your website was designed around and understand the scope of a change before saving it.

Make Site-Wide Changes Deliberately

The Site Editor brings much more of WordPress theme customisation into a visual interface.

That makes many tasks easier, but site-wide controls deserve more care than editing a paragraph on one page.

Before making a change, ask yourself what you are actually editing:

  • one piece of content
  • one page
  • one template
  • one reusable template part
  • one menu
  • one block type across the site
  • the site’s overall styles

Once that distinction is clear, the Site Editor becomes much easier to work with safely.

If you need to make a site-wide WordPress change and are unsure whether it belongs in the Site Editor, your theme or custom development, ask Newt Labs about one-off WordPress support.

About the author

Steven Watts

Steven is the founder of Newt Labs and a WordPress specialist with more than 15 years of experience. Since 2010, he has been helping businesses keep their WordPress websites secure, fast, reliable and well supported, with a focus on practical advice and long-term website care.

Related advice

More Support articles

Need a clearer next step?

Get practical help with your WordPress website

You can start with one issue, a free audit, or an ongoing care plan depending on what your website needs.

WordPress support illustration.