Table of Contents
Ever wondered how the best CMS tools like WordPress deliver consistent layout throughout the website pages and posts? Well, the key is the website templates and files involved in them. Think of the template as a blueprint that dictates how your content is organized and displayed on your website.
WordPress template hierarchy is a system of pages and PHP files that work together to deliver your content in a structured manner. So when a visitor accesses a page on your website, WordPress searches through the hierarchy and finds the suitable template to display the content.
With our WordPress development experts, I have tried to provide you with the best information on the WordPress template hierarchy. Hence this blog. But first, let’s see what the template files are.
What is a WordPress Template?
A WordPress template is a blueprint that dictates how your content is displayed on your website. It’s like a design framework that defines the structure, layout, and appearance of your pages and posts. Think of it as the skin of your website.
When a visitor accesses a page on your WordPress website, the template system determines which template file to use based on the content type and hierarchy. For example, a blog post might use the single.php template, while a page about your company might use the page.php template.
Templates are typically written in PHP, a programming language. They can be customized to a great extent, allowing you to create unique and visually appealing designs for your website.
Key WordPress Template Files
The WordPress template hierarchy is a system of files that work together to determine how your content is displayed. Here are some of the most important template files:
- index.php: This is the default template file. It’s used for most pages and posts if a more specific template file is not found.
- home.php: This template is used for the homepage of your website.
- single.php: This template is used for displaying individual posts.
- page.php: This template is used for displaying individual pages.
- archive.php: This template is used for displaying archives of posts, such as category or tag archives.
- search.php: This template is used for displaying search results pages.
- author.php: This template is used for displaying author archives.
- date.php: This template is used for displaying date-based archives.
- comments.php: This template controls the display of comments on your website.
These are just some of the most common template files. Depending on your theme and plugins, you may encounter other template files as well.
Want a consistent design and layout on your WordPress website?
WordPress Template Hierarchy
The WordPress template hierarchy is a system that determines which template file is used to display a specific page or post on your website. It’s a cascading order of precedence, meaning that WordPress searches for the most specific template file first. If not found, it then falls back to more general templates if a specific one is not found.
Let’s look at the template files and hierarchy for different types of pages and posts.
Home Page (or Front Page)
The home page is often the first impression visitors have of your website. It serves as a central hub that introduces your site and guides users to relevant content.
- front-page.php: This is an optional template file that can be used for the homepage if you want to have a different design for your home page compared to other pages. If this file exists, it will take precedence over home.php and index.php.
- home.php: If this file exists, it will be used for the homepage.
- index.php: If home.php doesn’t exist, WordPress will use index.php for the homepage.
Single Posts
Single posts are individual pieces of content that you publish on your WordPress website. They can be blog posts, articles, news items, or any other type of content that you want to share with your audience.
- single-{post_type}-{slug}.php: If a template file exists with this naming convention (where {$post_type} is replaced with the actual post type and {$slug} is replaced with the post’s slug), it will be used for that specific post.
- single-{post_type}.php: If a specific post type template doesn’t exist, WordPress will use a template with this naming convention (where {$post_type} is replaced with the post type).
- single.php: If a specific post type template doesn’t exist, WordPress will use single.php. This is the default template for all single posts.
- singular.php: This is a fallback template that can be used for both single posts and single pages. If single-{post_type}-{slug}.php, single-{post_type}.php, and single.php don’t exist, WordPress will use singular.php.
- index.php: If none of the above templates exist, WordPress will use index.php for single posts.
Single Pages (or Static Pages)
Single pages provide a more structured and permanent presence on your WordPress website. Unlike posts, which are typically arranged in chronological order, pages are standalone pieces of content that can be organized into a hierarchy.
- page-{slug}.php: If a template file exists with this naming convention (where {$slug} is replaced with the page’s slug), it will be used for that specific page.
- page-{id}.php: If a template file exists with this naming convention (where {$id} is replaced with the page’s ID), it will be used for that specific page.
- page.php: If a specific page template doesn’t exist, WordPress will use page.php.
- singular.php: This is a fallback template that can be used for both single posts and single pages. If page-{slug}.php, page-{id}.php, and page.php don’t exist, WordPress will use singular.php.
- index.php: If none of the above templates exist, WordPress will use index.php for single pages.
You can also hire expert WordPress developers to create a custom template file for complete page customization.
Category Archive
Category archives are pages that display a list of posts that belong to a specific category. They are a useful way to organize and categorize your content, making it easier for visitors to find what they’re looking for.
- category-{slug}.php: If a template file exists with this naming convention (where {$slug} is replaced with the category’s slug), it will be used for that specific category archive.
- category-{id}.php: If a template file exists with this naming convention (where {$id} is replaced with the category’s ID), it will be used for that specific category archive.
- category.php: If a specific category template doesn’t exist, WordPress will use category.php.
- archive.php: If a specific category template doesn’t exist, WordPress will use archive.php as a fallback.
- index.php: If none of the above templates exist, WordPress will use index.php for category archives.
Tag Archive
Tag archives display a list of posts that have been tagged with a specific keyword or phrase. They are a useful way to organize and categorize your content based on common themes or topics.
- tag-{slug}.php: If a template file exists with this naming convention (where {$slug} is replaced with the tag’s slug), it will be used for that specific tag archive.
- tag-{id}.php: If a template file exists with this naming convention (where {$id} is replaced with the tag’s ID), it will be used for that specific tag archive.
- tag.php: If a specific tag template doesn’t exist, WordPress will use tag.php.
- archive.php: If a specific tag template doesn’t exist, WordPress will use archive.php as a fallback.
- index.php: If none of the above templates exist, WordPress will use index.php for tag archives.
Custom Taxonomy Archive
Custom taxonomies are user-defined categories that can be used to organize and categorize your content in a way that is specific to your website’s needs. They are often used for custom post types, but can also be used for regular posts and pages.
- taxonomy-{taxonomy}-{term}.php: If a template file exists with this naming convention, it will be used for that specific custom taxonomy term archive. The {$taxonomy} is replaced with the custom taxonomy’s name and {$term} is replaced with the term’s slug
- taxonomy-{taxonomy}.php: If a template file exists with this naming convention (where {$taxonomy} is replaced with the custom taxonomy’s name), it will be used for the archive of all terms within that custom taxonomy.
- taxonomy.php: If a specific custom taxonomy template doesn’t exist, WordPress will use taxonomy.php.
- archive.php: If a specific custom taxonomy template doesn’t exist, WordPress will use archive.php as a fallback.
- index.php: If none of the above templates exist, WordPress will use index.php for custom taxonomy archives.
Custom Post Types
Custom post types allow you to create new types of content beyond the default post and page types in WordPress. This is particularly useful for websites that require specialized content, such as products, events, or portfolios.
- archive-{$post_type}.php: If a template file exists with this naming convention (where {$post_type} is replaced with the custom post type’s name), it will be used for the archive page of that custom post type.
- archive.php: If a specific custom taxonomy template doesn’t exist, WordPress will use archive.php as a fallback.
- index.php: If none of the above templates exist, WordPress will use index.php for custom taxonomy archives.
Author Archive
Author archives are pages that display a list of posts written by a specific author. They are a useful way to showcase the work of individual contributors on your website.
- author-{nicename}.php: If a template file exists with this naming convention (where {$nicename} is replaced with the author’s nicename), it will be used for that specific author archive.
- author-{id}.php: If a template file exists with this naming convention (where {$id} is replaced with the author’s ID), it will be used for that specific author archive.
- author.php: If a specific author template doesn’t exist, WordPress will use author.php.
- archive.php: If a specific author template doesn’t exist, WordPress will use archive.php as a fallback.
- index.php: If none of the above templates exist, WordPress will use index.php for author archives.
Date Archive
Date archives are pages that display a list of posts based on their publication date. They can be filtered by year, month, or day, providing a chronological overview of your content.
- date.php: If a template file exists with this naming convention, it will be used for date archives.
- archive.php: If a specific date template doesn’t exist, WordPress will use archive.php as a fallback.
- index.php: If none of the above templates exist, WordPress will use index.php for date archives.
Search Result Page
Search result pages display a list of posts that match a user’s search query. They are an essential tool for helping visitors find the information they need on your website.
- search.php: If a template file exists with this naming convention, it will be used for search result pages.
- searchform.php: This file contains the search form that allows users to enter their search query.
- index.php: If a specific search template doesn’t exist, WordPress will use index.php as a fallback.
Error 404 Page
The 404 error page is displayed when a visitor tries to access a page on your website that doesn’t exist or is no longer available. It’s important to have a well-designed 404 page to provide a positive user experience and guide visitors back to your website.
- 404.php: If a template file exists with this naming convention, it will be used for the 404 error page.
- index.php: If a specific 404 template doesn’t exist, WordPress will use index.php as a fallback.
Attachment Pages
Attachment pages are used to display individual media files, such as images, PDFs, or audio files. They are typically linked to posts or pages that reference the attachment.
- MIME_type.php: If a template file exists with this naming convention (where MIME_type is replaced with the MIME type of the attachment), it will be used for that specific attachment.
- attachment.php: If a specific MIME type template doesn’t exist, WordPress will use attachment.php.
- single-attachment.php: This is an optional template that can be used for attachment pages. If it exists, it will take precedence over attachment.php.
- single.php: If neither MIME_type.php nor attachment.php exist, WordPress will use single.php as a fallback.
- index.php: If none of the above templates exist, WordPress will use index.php for attachment pages.
If you need custom template files for your WordPress website, our WordPress development company will be suitable. We will explore your requirements and create custom template files for the hierarchy.
How to Locate the WordPress Template Files?
Now that you understand the WordPress template hierarchy, it will be easier to find the template files. This hierarchy determines the order in which WordPress searches for template files when displaying content.
There are two ways to find the template files of your WordPress website.
Using the Theme Editor
Most WordPress themes come with a built-in theme editor. You can access this by going to Appearance → Theme Editor in your WordPress admin dashboard. From there, you can view and edit the template files for your theme.
Using an FTP Client
If you prefer to edit the template files directly, you can use an FTP client to connect to your WordPress website and navigate to the theme’s directory. Once you’re connected, you can view, edit, and save the template files.
Doing this, you can customize the appearance and functionality of your WordPress website.
FAQs on WordPress Template Hierarchy
To Summarize
WordPress template hierarchy is a key part of customizing the appearance and functionality of your website. By understanding the key template files and how they work together, you can create a unique and visually appealing design. That will reflect your brand and meet your specific needs.
The key template files include index.php, home.php, single.php, page.php, archive.php, header.php, and footer.php. You can customize your website’s appearance by editing these template files or using a child theme.
If you need help with the template hierarchy and other design aspects, our WordPress professionals will be helpful. Let’s have a chat!