How to build custom page layouts in WordPress

Decide whether you need one unusual page, a reusable template for several pages, or a complete site-wide redesign. A block theme lets you edit templates visually in Appearance > Editor. With a classic theme, use the block editor for page content and a child theme for template-level changes.

You do not need a plugin for a straightforward layout made from headings, images, columns, groups, buttons and spacing controls. You need extra tooling when you want reusable design systems, complex responsive behaviour, dynamic content or many pre-built layouts.

Sketch the page as sections before opening the editor: header, hero, supporting content, call to action, proof or testimonials, and footer. Keep each section in a Group or Cover block, then use Columns or a Grid-style arrangement only where it improves the content.

Decide which areas belong to the page and which belong to the template. A header or footer is a template part; the hero and main content normally belong to the individual page. This separation prevents you from changing every page when you meant to change one.

On a block theme, open Appearance > Editor, then open Templates to edit an existing layout or add a page template. WordPress provides templates for page types, and the Template Editor lets you design them with blocks. You can also manage reusable headers, footers and other template parts under Patterns.

For a layout used by one page, create a page-specific template where available. For a layout used by many pages, create a general page template and assign it from the page editor’s Template setting. Save the template, then edit the page content separately.

With a classic theme, create and activate a child theme before changing template files. Add a custom page template to the child theme, give it a clear template name such as Template Name: Landing page, and then select it from the page editor’s Template or Page Attributes setting. WordPress recognises custom page templates placed in the theme folder.

Start by copying the theme’s existing page template rather than writing a complete layout from nothing. Keep the normal title and content output unless you have a reason to replace it. Do not use a filename beginning with page- for a globally selectable template, because WordPress treats that naming pattern as a page-specific template.

The drawback is maintenance: PHP, CSS and responsive rules are now your responsibility, and editing the parent theme directly can erase your work during an update. A child theme avoids that particular problem, but it still requires development knowledge.

Check the layout at a narrow mobile width, tablet width and desktop width before adding more decoration. Reduce column counts, check image cropping, keep text readable, and make buttons large enough to tap. Avoid fixed widths that force horizontal scrolling.

Use the theme’s spacing, typography and colour controls where possible instead of adding page-specific CSS for every block. If a block looks correct only at one screen size, simplify the structure before adding more CSS.

Preview the page while logged out and test its links, navigation, forms, images and accessibility basics. Confirm the page uses the intended template and that the page content still appears inside it. A template change can affect every page assigned to that template, not just the page you were viewing, so check a second page before publishing.

If the layout does not appear, check that you edited the active theme, selected the correct template, saved the template, and are not looking at a cached version of the page.

For several custom layouts, use YOOtheme Pro for WP and Joomla. Its visual drag-and-drop builder, templates and responsive controls reduce the need to create child-theme files and write layout CSS by hand. It is a sensible shortcut for designers who need more control than a basic theme customizer provides.

Keep the manual route for simple pages or sites where you want to minimise dependencies. Whichever route you choose, make a backup first and avoid building every page as an isolated design that cannot be reused.