- Article
- 3 minutes read
- Reviewed August 3, 2026
WordPress permalinks define the public URLs used to access content. Archives are collection views that list records sharing a post type, date, author or taxonomy term.
For structured content, URLs and archives should be planned as part of the model rather than accepted as accidental plugin defaults.
Single Content URLs
A public custom post type can have single URLs such as /events/summer-festival/. WordPress resolves the path into a query for one entry and then selects a template.
The post slug identifies the individual record within the rewrite structure. Duplicate slugs may receive suffixes to remain unique in the relevant context.
Post Type Archives
A post type archive is a collection URL such as /events/. It can list entries, introduce the collection and support pagination or filtering.
The archive should exist because visitors need a collection page, not simply because registration provides an option. Some types are accessed only through relationships or custom landing pages.
Taxonomy Archives
A public taxonomy term can have its own archive, such as /event-type/conference/. The query lists content assigned to that term.
Taxonomy archives need useful titles, descriptions, canonical behaviour and indexation decisions. Empty tag-like archives can create thin content.
Permalink Settings and Custom Types
The general permalink setting controls common structures, especially posts. Custom post types and taxonomies define rewrite arguments when registered.
Saving the Permalinks screen refreshes rewrite rules, but it does not automatically repair a conflicting architecture.
Slug Conflicts
A page, post type archive, taxonomy base or endpoint may compete for the same path. WordPress chooses routes according to generated rewrite rules and query parsing.
Test exact single, archive, pagination, feed and term URLs before launch.
Changing Slugs
Changing a public base or individual slug changes the URL. Add permanent redirects from old addresses, update internal links, regenerate sitemaps and verify canonical tags.
Do not rely on search engines to infer every moved URL.
Nested and Hierarchical URLs
Nested URLs can communicate context but couple addresses to hierarchy. Moving content then changes the path and creates redirect work.
Use a shallow stable URL when the hierarchy changes frequently or exists mainly for administration.
Pagination and Filtering
Archive pagination needs stable canonical handling. Filter parameters can create many URL combinations, some of which should not be indexed.
Define which filters deserve crawlable landing pages and which are temporary user interface states.
Archive Design Requirements
- Clear collection title and introduction.
- Useful ordering and empty-state behaviour.
- Pagination or load strategy.
- Filter and search controls where justified.
- Consistent cards using structured fields.
- Canonical, sitemap and indexing policy.
- Accessible navigation and headings.
URL Planning Principles
- Prefer stable, readable slugs.
- Avoid unnecessary depth and implementation jargon.
- Check collisions before publishing.
- Plan redirects before changing existing URLs.
- Decide which archives provide independent visitor value.
- Test URLs under the real server configuration.
Frequently Asked Questions
Does every custom post type need an archive?
No. Enable an archive only when a public collection page supports the project and visitor journey.
Why does a new custom post type URL return 404?
Rewrite rules may need to be refreshed, or the slug may conflict with another route. Registration and server permalink support should also be checked.
Can archive and single slugs be different?
Yes, but the implementation and visitor experience should remain understandable and stable.