All posts

What Is WordPress Full Site Editing? The Site Editor Explained

Full Site Editing lets you edit headers, footers and templates with blocks in the Site Editor. What it covers in WordPress 7.1, SEO effects, and when to skip it.

Site wireframe with header, content, sidebar and footer marked as editable regions

You open Appearance in wp-admin and see "Editor" where "Customize" and "Widgets" used to be, or a tutorial tells you to "edit the template" and you can't find any template. That's Full Site Editing. It's WordPress's way of letting you edit every part of the site (headers, footers, templates, global styles) with the same blocks you use in posts, instead of PHP files or the old Customizer.

Full Site Editing arrived in WordPress 5.9 in January 2022. WordPress itself has mostly dropped the "FSE" label since then and now just calls it site editing, done in the Site Editor. It only works with a block theme. As of WordPress 7.1, released in August 2026, it's mature enough to be the default choice for most new sites, with a few exceptions covered below.

WordPress Full Site Editing UI

How it differs from a classic theme

With a classic theme, you write posts in the block editor, but everything around the content lives in the theme's PHP files: header.php, footer.php, single.php. To change those you edit code, use the Customizer's limited options, or add a page builder.

With a block theme, those templates are made of blocks too. The theme ships HTML templates, template parts, patterns, and a theme.json file that sets colors, fonts, and spacing. You edit all of it visually in the Site Editor, and your changes are saved to the database without touching theme files.

Classic theme

Block theme

Templates

PHP files

Block-based HTML templates

Header and footer

header.php, footer.php

Template parts edited in the Site Editor

Styling

Customizer and CSS

Styles panel, backed by theme.json

Menus

Appearance > Menus

Navigation block

Sidebars

Widgets screen

Blocks inside templates

Where you edit

Appearance > Customize

Appearance > Editor

What's in the Site Editor

Once a block theme is active, go to Appearance > Editor. According to the WordPress Site Editor documentation, the main menu has six areas:

Area

What you do there

Identity

Set the site title, tagline, logo, and site icon (new in 7.1)

Styles

Change colors, typography, spacing, and block defaults for the whole site

Pages

Edit page content inside the Site Editor

Navigation

Manage menus built with the Navigation block

Patterns

Manage synced patterns and template parts such as the header and footer

Templates

Edit layouts for single posts, pages, archives, search results, and the 404 page

WordPress 7.1 also keeps the admin bar visible across the Site Editor and lets you save style changes for tablet and mobile viewports from the preview menu, so basic responsive tweaks no longer need custom CSS.

The pieces you'll use most

Templates and template parts are the core of it. Edit the Single Posts template once and every post changes. Edit the Header template part and every page's header changes.

Global Styles (the Styles panel) is where site-wide design lives. Set your fonts and colors once and every block picks them up. Developers can lock or preset these options in theme.json.

Patterns are reusable block layouts. Themes ship their own, and the Pattern Directory has many more you can copy in.

The Query Loop block builds lists of posts (by category, tag, author, or date) without custom PHP. It's how block themes build blog indexes and archives.

Block Bindings, added in WordPress 6.5, connects a block's content to a data source such as a custom field, so a heading or paragraph can show post meta without a custom block. The Block Bindings reference covers how it works.

Is Full Site Editing good for SEO?

It's neutral to slightly positive. Google doesn't know or care how your template was built. What matters is the HTML that comes out, and block themes tend to produce reasonably clean output.

Where block themes help:

  • Default block themes like Twenty Twenty-Five load little CSS and JavaScript compared with heavy multipurpose themes and page builders.
  • Styles come from theme.json and Global Styles, so you need less custom CSS layered on top.
  • Headings and layout are visible and editable in the Site Editor, so it's easy to see whether the post title is your only H1.

Where to be careful:

  • A block theme loaded with large patterns, animations, and web fonts can still be slow. Test it the same way you'd test any theme. Our guide to testing WordPress theme speed covers the method.
  • Most block themes don't output schema themselves. That's fine, because your SEO plugin should handle it, but verify with Google's Rich Results Test. Our post on schema markup in WordPress themes explains how to check.
  • Template edits apply site-wide. Removing a block from the Single Posts template (say, breadcrumbs or a related-posts query) removes those internal links from every post at once.

For the broader picture of what a theme can and can't do for rankings, see how your WordPress theme affects SEO.

Block themes worth trying

The WordPress.org theme directory has a Full Site Editing tag that lists only block themes. A few starting points:

  • Twenty Twenty-Five: the newest default theme, bundled with WordPress since 6.7. A safe first choice for testing.
  • Twenty Twenty-Four and Twenty Twenty-Three: older defaults, still updated and still block themes.
  • Ollie: a popular free block theme with a large pattern library, actively updated.

Several popular "lightweight" themes are classic or hybrid themes, not block themes. GeneratePress, Astra, Kadence, and Blocksy all fall into that group. They work well with the block editor for content, but they don't give you the Site Editor. If you want to compare those, see GeneratePress vs Astra or our list of fast-loading WordPress themes.

How to try it safely

Don't switch an established site to a block theme on live. Rebuilding templates takes time, and menus, widgets, and Customizer settings don't carry over from a classic theme.

  1. Copy the site to staging. Most managed WordPress hosts do this in one click.
  2. Activate a block theme on staging. Twenty Twenty-Five is the safest starting point.
  3. Rebuild your header, footer, and Single Posts template in the Site Editor. Recreate your menu in the Navigation block.
  4. Check your top pages: one H1 per page, schema still present, internal links still there.
  5. Compare speed against your current theme on the same pages.
  6. Move to production only when the staging site matches or beats the current one.

The full pre-switch and post-switch checklist is in does changing a WordPress theme affect SEO. It applies directly.

When Full Site Editing isn't the right fit

Stick with a classic theme for now if:

  • Your site is built on a page builder (Elementor, Divi, Beaver Builder) and you or your team know it well.
  • Your site depends on custom PHP templates that would need rebuilding from scratch.
  • Your store relies on a theme tightly tied to classic WooCommerce templates. Check compatibility before switching.
  • The people editing the site find the Site Editor confusing. It still has a learning curve.

In those cases a well-built classic theme with good block editor support is a sensible middle step.

Resources

The short version

Full Site Editing means editing your whole site, not just posts, with blocks in the Site Editor. It needs a block theme, it's mature as of WordPress 7.1, and it's a solid default for new sites. It doesn't help or hurt SEO by itself. Test speed, headings, schema, and internal links the same way you would for any theme change, and try it on staging before you move an established site over.