Your Blog URL Is a Promise About What the Article Becomes

Use a simple descriptive slug for most new evergreen articles. Put a date in the URL when chronology is part of the resource’s identity, such as news, an event record or a genuinely separate annual edition. Put a category in the path only when that taxonomy is stable enough to remain true for the life of the article.

The important decision comes before any of those formats: will the content be maintained as one continuing answer, preserved as a dated record or published again as a distinct edition?

A permalink does not need to carry every label visible in WordPress. Publication dates can appear on the page. Taxonomy can live in navigation, archives and breadcrumbs. The URL should carry only the identity the publisher is prepared to preserve.

Every path segment creates an editorial debt

Folders look harmless when a site is new. Their cost appears later, when the marketing strategy changes but hundreds of external links, campaign records and analytics reports still depend on the old addresses. Compare the commitments:

Any of these can resolve to a useful page. The question is which promises survive normal editorial change. Google recommends logical URL structures with readable words and hyphens between concepts where possible (Google’s URL structure guidance). WordPress describes permalinks as the permanent URLs used to link to posts, pages, archives and other resources (WordPress permalink documentation). Neither source can choose the publishing model for the business.

The shortest URL is not automatically the best. The cleverest taxonomy is not automatically useful. Every segment must earn the cost of keeping it accurate.

Classify the resource by how it ages

I use a simple three-part lifecycle test before approving a blog address:

Ask four questions:

• If the date disappeared, would the resource become a different or misleading object?
• Will future work revise this answer or create another legitimate item?
• Must the earlier version remain available after the next version exists?
• Do representative pages in the proposed family age in the same way?

Do not turn the answers into a fake precision score. If the content’s future or owner is unknown, the URL decision is not ready. If examples within the same blog produce different answers, the word blog is concealing several publishing families. This lifecycle classification is the article’s practical asset. It chooses the identity before anybody argues about slug length, keywords or aesthetics.

Maintained references usually need stable, simple slugs

A maintained reference has one continuing job. Its evidence, examples, screenshots, recommendations and visible update date can change while the publisher maintains one canonical resource. Suitable patterns might include /blog/how-to-choose-an-seo-agency/, /guides/local-seo-audit/ or /resources/website-migration-checklist/. The folder identifies a durable resource family. The slug names the subject. Publication and meaningful update dates remain visible in the article.

An original year describes history, not necessarily identity. A guide first published in 2024 can remain the same maintained resource in 2026 after a substantive revision. Putting /2024/ in its path is not fatal, but the address advertises a fact that may no longer help the reader understand the page.

Do not call something evergreen merely because nobody intends to maintain it. A reference needs an owner, an update rule and a review trigger. Otherwise the clean slug hides neglect instead of supporting continuity. For growth marketing, this matters because a maintained guide can accumulate recognition, links, citations and buyer familiarity at one address. The value comes from continued ownership, not from the absence of a date folder.

Dated records should remain dated

A dated record describes something that happened or applied at a particular time. Press releases, event reports, incident updates and historical announcements fit this model. The record can be corrected or annotated without becoming next year’s event. Removing its period may make two legitimate records indistinguishable. Examples include /news/2026/07/new-office-opens/, /events/2026/sussex-business-conference/ and /updates/2026-07-service-interruption/.

Chronology earns its place because it changes the identity of the object. It is not there to manufacture freshness for AI SEO or conventional search. This does not mean every newsroom needs year and month folders. A descriptive slug may uniquely identify an event while the visible publication date carries chronology. The lifecycle explains why time matters; the site’s URL rulebook decides how to express that meaning consistently.

A year in the slug is an edition promise

Putting 2026 into a slug can mean “this is the current guide” or “this is the 2026 edition.” Only the second meaning gives the year a durable job. Separate editions make sense for annual benchmark data, tax-year information, recurring event programmes, dated market reviews, annual awards or directories, archived policies or specifications, and meaningful software or product releases.

If the 2025 and 2026 resources must coexist because they contain different evidence or govern different periods, the year identifies each one. A stable series page can provide the continuing route while individual editions retain their own addresses. If there is only one maintained answer, changing 2026 to 2027 every January creates avoidable production and redirect work. Updating screenshots and evidence does not automatically create a new edition.

Before I approve a year in a URL, I want two answers: what makes this edition distinct, and why should the previous edition remain available? If nobody can answer both, the year is probably decoration.

A category is a shelf, not a lifecycle

A category describes a collection. It does not decide whether the article is maintained, historical or editioned. A category segment may be useful when the collection represents a durable audience or information job; editors agree on one primary owner; category names are governed rather than changed with every campaign; the CMS does not casually alter the permalink when classification changes; archive pages are useful and maintained; and the hierarchy remains understandable.

It becomes fragile when technical-seo is likely to become digital-growth, when articles move between teams or when the CMS selects one of several assigned categories through a rule editors do not control. WordPress supports date, post-name and category tokens in custom permalink structures. Its documentation explains that category-based structures interact with the site’s assigned categories (WordPress permalink documentation). Software capability is not proof that an editorial taxonomy belongs in a permanent address. Decide the shelf separately from the life of the book.

Taxonomy should be able to evolve around the article

An article can belong to useful categories without carrying one in its path. Readers and editors can discover those relationships through hubs, archives, breadcrumbs, navigation, filters, related-content modules and search. That separation lets the resource keep one address while discovery routes evolve around it. A guide can move from an SEO navigation label to an AI Search Optimisation or Customer Acquisition hub without becoming a different guide.

The URL does not need to mirror every menu level. Public hierarchy and technical paths can overlap without being identical. For branding and website design teams, this removes a common source of conflict. The information architecture can respond to a new positioning strategy without forcing a sitewide migration merely because the navigation language changed. If taxonomy is expected to change more often than content identity, keep it out of the permalink. This is not an argument for a flat site. It is an argument for separating changing classification from stable resource identity.

Visible dates explain freshness better than calendar folders

A year in the URL does not prove that an article is current. It may describe first publication, a historical event, an edition or nothing more than an old CMS default. Google says its systems may display a date when they can determine a page’s publication or substantial update time. Google recommends prominent user-visible dates, accurate labels and consistency between visible and machine-readable values (Google’s publication-date guidance). Use clear labels such as Published 14 March 2024 and Last updated 9 July 2026 after a meaningful revision.

Do not refresh the date because somebody corrected punctuation or wants the result to look newer. Do not use the date of an event as the article’s publication date. Do not expect /2026/ to communicate freshness when the calendar reaches 2027. AI readiness depends on accurate, legible publishing signals, not on repainting an old timestamp. The path identifies the resource. Visible dates explain its publishing history.

One blog may contain several publishing systems

A single WordPress post type often conceals different content lives:

If representative pages produce different lifecycle answers, split the publishing family before choosing the route rule. The shared post label tells the CMS how to store them. It does not tell the organisation how they should age. The clean operational answer may require distinct templates, content types or publishing workflows. That decision belongs upstream of bulk production.

An ugly existing URL is not automatically an SEO emergency

An evergreen article at /2021/05/technical-seo-audit/ can still serve readers, attract links and appear in search. The date folder may be inelegant. Inelegance alone does not authorise a move. Changing a live address creates dependencies across internal links and navigation; external links and bookmarks; canonicals and sitemaps; analytics and performance marketing reports; email, social media and paid campaigns; feeds, caches and server rules; and recrawling and reprocessing.

Google treats URL changes as a site move. Its guidance recommends mapping old URLs to relevant equivalents, deploying redirects, testing the new site, updating links, submitting the new sitemap and monitoring both old and new URLs. Google also warns that search visibility can fluctuate while a move is processed (Google’s site-move guidance). Do not convert a design preference into infrastructure work merely because the replacement looks cleaner in a spreadsheet.

If the pattern changes, treat it as infrastructure

A sitewide permalink change can alter every article address through one WordPress setting. The ease of clicking that control bears no relationship to the scale of the consequence. A responsible migration needs:

Do not redirect every old article to the blog homepage. A redirect should lead to a genuine successor. When no relevant replacement exists, an honest not-found response can be better than a misleading journey. The lifecycle test may expose a mismatch between the old pattern and the current content model. It does not prove that migration benefits outweigh migration cost. That requires a separate release decision.

Write slugs for identity rather than headlines

Headlines can change as an article improves. Slugs should retain the durable concept. An article titled Your Blog URL Is a Promise About What the Article Becomes might use /blog/blog-url-structure/. The slug does not need to reproduce every phrase in the headline or carry a list of SEO modifiers. For a new article:

• Use lowercase words
• Separate words with hyphens
• Remove language that adds no identity
• Retain important product, service or concept names
• Avoid dates unless they are intrinsic
• Check for current URL and redirect collisions
• Settle page ownership before publication
• Freeze the address before promotion

A tidy slug cannot rescue overlapping content. Two beautifully named articles can still compete if both answer the same decision. Content ownership comes first; the URL expresses the settled result.

Give the article an address it can keep

Use a simple descriptive slug for a new maintained reference. Use a date when chronology defines the record. Use a year or version when separate editions must coexist. Use a category folder only when the taxonomy is stable enough to become part of the permanent identity. Keep publication and update dates visible and accurate. Let categories, hubs and navigation explain discovery paths that may evolve. Do not force every marketing label into the address.

For existing articles, preserve a serviceable URL until a material benefit justifies controlled migration. I would rather accept an inelegant address with years of dependencies than commission a risky migration to satisfy a taste for tidiness. That preference changes when the old structure causes a measurable operational, user or consolidation problem and the organisation can execute the move properly.

Choose the content’s future before choosing its address. The right blog URL is not the shortest or newest-looking. It is the clearest promise the publisher can keep while everything around it changes.