The Archive Inventory tab shows the archive-style pages that MinimalCSS can optimize.
Archive pages are different from regular pages and posts because they are generated by WordPress automatically. These may include blog archives, category pages, tag pages, author archives, date archives, WooCommerce shop archives, product category archives, and other custom post type archives.
The Archive Inventory helps you review, generate, test, and manage optimized CSS for these important listing pages.
What the Archive Inventory Tab Is For
The Archive Inventory is used to manage CSS optimization for archive templates across your site.
Depending on your WordPress setup, the inventory may include:
- Blog index pages
- Category archives
- Tag archives
- Author archives
- Date archives
- WooCommerce shop pages
- Product category archives
- Product tag archives
- Custom post type archives
- Custom taxonomy archives
The exact archives shown depend on your theme, plugins, permalink settings, and public content types.
Why Archive Optimization Matters
Archive pages often use different layouts than individual posts or pages.
For example, a blog post may have a simple content layout, while a category archive may include post cards, pagination, filters, sidebars, featured images, excerpts, and template-specific styling.
Because of this, archive pages should be reviewed separately from regular pages.
Optimizing archive CSS can help improve performance on pages such as:
- Blog listing pages
- Category pages that receive organic search traffic
- Product category pages
- Resource libraries
- Portfolio archives
- Service listing pages
- Location listing pages
These pages can be important for both SEO and user navigation.
Archive Pages vs. Regular Pages
Regular pages are usually created and edited directly in WordPress.
Archive pages are usually generated automatically by WordPress based on your theme templates and content structure.
For example:
- A service page is a regular page.
- A blog post is a regular post.
- A category page that lists posts in that category is an archive.
- A product category page that lists products is an archive.
- An author page that lists posts by one author is an archive.
Because archives are template-driven, changes to your theme, templates, sidebars, filters, or post card layouts may affect many archive pages at once.
Understanding Archive Statuses
Each archive in the Archive Inventory may show a status that helps you understand whether it has been optimized.
Common statuses may include:
Not Optimized
The archive has been detected, but optimized CSS has not been generated yet.
This is common after the plugin is first installed or when new taxonomies, categories, tags, products, or custom post types are added.
Optimized
Optimized CSS has been successfully generated for the archive.
After optimization, you should still test important archive pages on desktop and mobile.
Excluded
The archive has been excluded from optimization.
Excluded archives will not use optimized CSS generated by MinimalCSS.
Which Archives Should You Test First?
Start with archive pages that are important for traffic, SEO, or conversions.
Good candidates include:
- Main blog page
- Popular category pages
- Product category pages
- Shop page
- Resource or article archives
- Portfolio archives
- Location archives
- Service archives
- Custom post type archives that receive traffic
You do not need to start by optimizing every archive on the site. Begin with the most important archive templates, confirm that they display correctly, and then continue with the rest.
Testing Optimized Archives
After generating CSS for an archive, test it carefully.
Review the archive on desktop and mobile, and check elements such as:
- Header and navigation
- Archive title
- Breadcrumbs
- Post or product cards
- Featured images
- Excerpts
- Pagination
- Filters and sorting controls
- Sidebar widgets
- Category or taxonomy descriptions
- Calls to action
- Footer
- Mobile layout
If the archive includes AJAX filters, infinite scroll, faceted search, product sorting, or other dynamic behavior, test those features before relying on the optimized version.
When to Exclude an Archive
Some archive pages may not be good candidates for optimization.
You may want to exclude archives that are highly dynamic, low-value, duplicate, thin, or difficult to test.
Examples may include:
- Empty category or tag archives
- Low-value tag archives
- Date archives
- Author archives on single-author sites
- Archives with complex filters
- Archives with infinite scroll
- Archives that change significantly based on user input
- Private or membership-related archives
- Search result pages, if listed
- WooCommerce archives with complex filtering or personalization
If an archive is not important for visitors or search engines, excluding it may be simpler than optimizing and testing it.
WooCommerce Archive Considerations
WooCommerce archive pages can be especially important because they may affect product discovery and sales.
If your site uses WooCommerce, test these archive types carefully:
- Shop page
- Product category pages
- Product tag pages
- Sale or promotional archives
- Filtered product listings
- Product sorting controls
- Pagination or load-more buttons
Be cautious with pages that use layered navigation, AJAX filtering, currency switchers, personalization, or dynamic product display rules.
When to Regenerate Archive CSS
Regenerate optimized CSS when archive templates or archive content layouts change.
This may be needed after:
- Updating your theme
- Editing archive templates
- Changing blog or product card layouts
- Updating WooCommerce templates
- Adding or removing sidebar widgets
- Changing pagination style
- Adding filters or sorting tools
- Updating taxonomy descriptions
- Changing global styles
- Modifying header or footer layouts
- Updating page builder templates used by archives
Because one archive template can affect many archive URLs, regenerating CSS after major template changes is important.
Bulk Archive Generation
The Archive Inventory may include options to generate CSS for multiple archives.
Bulk generation is useful once you have tested your most important archive templates and are comfortable with the results.
For a new setup, start with a small number of important archives first. Once those have been reviewed, you can generate CSS for additional archives in larger batches.
Best Practice Workflow
A safe Archive Inventory workflow looks like this:
- Open the Archive Inventory tab.
- Identify the most important archive pages on your site.
- Generate CSS for the main blog archive, shop page, or key category archives first.
- Test the optimized pages.
- Check desktop and mobile layouts.
- Test filters, pagination, sorting, and dynamic features.
- Exclude archives that should not be optimized.
- Generate CSS for additional archive pages.
- Review any failed or skipped archives.
- Regenerate archive CSS after major template or layout changes.
This approach helps you improve archive performance while reducing the risk of layout issues.
Troubleshooting
An archive is missing from the inventory
Check whether the archive is public, enabled, and accessible from the frontend. Some archives may not appear if they are disabled by your theme, SEO plugin, WooCommerce settings, or custom post type configuration.
An archive failed during generation
Try generating CSS again. If it continues to fail, check whether the archive redirects, returns a 404, requires login access, has no public content, or blocks normal frontend requests.
The optimized archive looks different
Compare the optimized and bypassed versions. If the issue only appears with optimized CSS, regenerate CSS for that archive. If the issue remains, exclude the archive while you review the layout.
Filters or sorting do not look right
Dynamic archive features may require extra testing. Test filters, sorting controls, pagination, and load-more buttons on both desktop and mobile. If the archive depends heavily on dynamic behavior, consider excluding it.
I changed my archive template
Regenerate CSS for affected archives so MinimalCSS can create optimized CSS based on the current layout.