1. Separate an enduring need from a one-off launch
Summer linen, winter layers and occasionwear may return each year. A dated collaboration or limited event can have a different purpose. Record the page’s shopper question, country, language and place in the catalogue before deciding whether to reuse it. Avoid creating a fresh year-specific URL simply because the merchandising calendar has changed.
Read last season’s search queries alongside launches, weather-sensitive demand, promotions and stock gaps. Use a comparable country and device scope. Historical impressions show observed visibility, not next season’s guaranteed demand or the number of people who will buy.
2. Work backwards from a credible assortment
Merchandising confirms the products, size coverage and expected availability. Content then checks what the collection can honestly promise. Development reviews templates, filters and links. Set the review dates around your actual launch dependencies instead of copying a universal six-week SEO timetable.
A pre-launch page must explain its current state. Do not present unconfirmed items as available or leave last year’s delivery dates in place. If there is no useful selection yet, agree what information remains helpful and when the page will be reviewed again.
3. Release one consistent shopping journey
Review the collection title, introduction, product cards and linked buying advice together on mobile. Replace old products in editorial examples. Make the collection reachable from relevant navigation and connect it to its available products through ordinary links. Google’s e-commerce guidance describes a linked category-to-product structure; the folder name alone does not provide that structure.
Publish after the assortment and copy owners approve the same version. Record the release date and a small set of representative URLs. Check those pages again after the storefront cache updates, including a small screen and an unavailable size.
4. Close the season with a decision, not a deletion rule
At sell-through, review whether the page still serves a useful selection or recurring need. Temporary stock handling belongs in the out-of-stock guide; this seasonal plan owns the next assortment and content review. If the purpose changes permanently, review URL handling with the developer rather than redirecting every seasonal page to the homepage.
For the retrospective, compare the same page group over documented periods. Note changed prices, promotions and availability. Keep observations separate from conclusions about causality. Save the decisions, unresolved questions and next review date so next season starts with evidence rather than a copied page.
A linen collection through four review moments
Illustrative plan: the merchandising owner confirms the next linen assortment; the editor removes outdated care and delivery statements; the developer checks collection-to-product links at launch; the team records sell-through and plans the next review. The collection keeps its existing purpose. No assumed ranking gain or automatic annual URL change is part of this plan.
Use this at work
- Confirm the recurring customer need and current URL.
- Assign assortment, copy and release owners.
- Check one consistent mobile journey at launch.
- Record the retrospective and next review date.
Reference material
Platform guidance checked 3 October 2026. Examples and working checklists are Faccelerate editorial illustrations.