A custom post type’s archive template — the page listing all entries of that type — failing to display correctly, showing the wrong layout, or erroring out usually comes down to a missing or incorrectly named template file, or a conflict between the theme’s expected template hierarchy and how the post type itself was registered.
Check which actual template file is being used for the archive
Many themes and page builders show which template file is currently rendering a given page, often in a debug bar or by checking the theme’s template hierarchy documentation. Confirming the archive is using the template you actually expect it to use is the fastest way to narrow this down.
Post type archive template errors
A custom post type's archive using the wrong template, traced to the actual template hierarchy.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| A custom post type’s archive page displays incorrectly, uses the wrong layout, or errors out | This fix covers it |
| The post type itself isn’t registering correctly, separate from its archive template specifically | Custom post type registration errors |
| The issue is with individual post pages of this type, not the archive listing | Worth describing the specific issue — likely a related but distinct template concern |
| You want the archive’s content or structure changed as a design decision, not an error fixed | A different, design-focused task rather than a technical fix |
What you are seeing
- The archive page displaying using the wrong template or a generic fallback
- A blank page or error where the archive should display
- The archive showing content but with broken or missing layout elements
- The issue possibly only appearing after a theme change or update
Common causes
- The post type registered without correctly enabling has_archive, so no archive template is expected to exist
- A template file named incorrectly for WordPress’s template hierarchy to find it automatically
- A theme update removing or renaming a template file the site depended on
- A conflict between a page builder’s own template system and WordPress’s native archive template hierarchy
- A pre_get_posts query modification elsewhere in the theme or a plugin altering what the archive actually shows, independent of the template file itself
What we do
- Confirm the post type’s archive is correctly enabled in its registration
- Identify which template file WordPress is actually attempting to use
- Correct or create the template file with the correct naming for the hierarchy
- Verify the archive displays with the correct, intended layout
- Test the fix across pagination and any archive-specific features (filtering, sorting)
- Check for the same issue on other custom post type archives if the site has more than one
What is included
- The archive template issue identified and corrected
- Verified correct display with intended layout
- Testing across pagination and archive-specific features
- The pre-fix backup, kept for 30 days
Not included
- Registering the custom post type itself, if that’s a separate, more fundamental issue
- Designing a new archive layout from scratch, a separate, design-focused task
- Individual post template issues for this post type, a separate, related fix if also affected
- Ongoing maintenance as the theme or page builder updates in future
Questions about this fix
Why would a theme update break this if the post type itself wasn't touched?
If your archive relied on a specific template file structure and the theme update renamed, restructured, or removed that file, WordPress's template hierarchy would fall back to a different, often generic template, producing an unexpected display even though nothing about the post type's own registration changed.
Does every custom post type need its own archive template?
Not necessarily — some post types are registered without an archive at all (has_archive set to false), which is a valid, deliberate choice; this fix is specifically for a post type that's meant to have an archive but isn't displaying it correctly.
Will this fix affect individual post pages of this type, not just the archive?
No, this specifically addresses the archive listing template — individual post display is governed by a separate template file and would need its own diagnosis if that's also an issue.
Could a page builder be the actual source of this conflict?
Yes, some page builders manage their own template system that can conflict with WordPress's native template hierarchy for custom post type archives — we'd identify this specifically if that's what's happening in your setup.
How do I know if my post type even has has_archive enabled?
This is set in the post type's registration code, which we'd check directly rather than relying on assumption — it's one of the first things worth confirming when an archive isn't behaving as expected.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.