How to file a product story so readers can find it later
Categories, titles, and permanent URLs — how a product story stays useful after it leaves the day’s homepage.
How do you file a product story so it stays findable?
Give it a stable URL, a title that names the product and the job, and one category a stranger would browse. Then leave the page up after it drops off the day’s index. Findability is the filing, not the hour it went live.
The URL is the filing cabinet
A product story that only lives in a homepage module will be gone when the next day publishes. Readers, and the systems that recommend pages, need a URL that does not change when the index rolls. Put the story at a path you can send in an email next month.
Slugs should say what the page is. A slug made of random characters is a filing system that requires the homepage to translate it. Include the product name if the name is public. Keep the slug stable after publication. Changing it to chase a keyword breaks every place the old URL was shared.
Title the page for a stranger
The homepage title and the page title can be the same sentence. Write it for someone who did not see the rest of the edition. “Fieldnote — a morning brief for support leads” still works in a search result and in a category list. “We shipped a new way to align” does not.
Put the product name first or immediately after a short label. People search names. People also search jobs: “morning brief for support.” A title that contains both is doing the filing work of two pages. Do not stuff a third job in. One page, one job.
Pick a category a reader would open
Categories are browse paths, not marketing tags. “Customer support” is a category. “Game-changing” is not. If you cannot imagine a reader clicking the category to see more products like this one, it is the wrong folder.
One primary category is better than five weak ones. Extra tags can mark a narrower fact — “standup,” “help desk” — without turning the story into a member of every list. A story filed everywhere is filed nowhere, because no list feels specific.
Write the deck as a second title
The deck is the sentence under the title in an index. It should add the person or the limit that the title did not fit. If the title names the product and the job, the deck can name the hour or the team. It should not repeat the title in longer words.
Decks get cut off in indexes and in search snippets. Front-load the useful part. A 140 to 160 character deck is a reasonable ceiling if you also want the sentence to survive a preview. The deck fitter on this site shows the cut before you publish.
Leave a trail inside the story
The body should repeat the product name, the job, and the person in the first paragraph, even though the title already said them. People land mid-site. They should not have to go back to the homepage to learn what the page is about.
Name the category in prose only if it helps. “This is a support tool” is weaker than showing the support lead’s morning. Internal links to the category, and to closely related stories, help a reader continue. They also tell a crawler which folder the page belongs in, without a block of keyword text.
After the edition day
When the story leaves today’s index, nothing about the filing should change. The URL, title, category, and deck stay. If the product’s job changes later, update the page and keep the URL. A correction on a stable address is more useful than a new post that orphans the old one.
Check the page the way a stranger would: search the product name, open the category, open the URL directly. If any of those three fail to explain the product in the first screen, the filing is incomplete. The day’s homepage was only the announcement. The file is the publication.
Questions
Should every story have its own URL?
Yes. The homepage is a day. The story is a document. Documents need addresses that survive the next edition.
How many categories should one story use?
One primary category that a reader would browse, plus a few narrow tags if you have them. Five primary categories make every category list noisier.
What if the product name is obscure?
Keep the name in the title and put the job next to it. People who know the name can find it. People who know the job can still tell whether to open the page.
Can I change the slug after publication?
Avoid it. If you must, redirect the old URL. A slug change without a redirect throws away the filing you just did.