Articles of Style has 297 "Look" pages in its sitemap, and each one is named by a number: Look 1012's search title is "Articles of Style | Look 1012" and its description is just "Look 1012". 234 of them have no description and none of the photos have alt text. Yet the tags show exactly what they are: 105 date-night looks, 99 business casual, 42 wedding looks, 14 formal. Look 1012 is a Super 180s tuxedo with a honeycomb crossover shirt and a bowtie. Nobody searches for "Look 1012"; people do search for "black tuxedo wedding look" or "business casual blazer outfit".
First action
Rename the 42 wedding looks this week, using the products in "Shop the Look".
How to measure it
Organic sessions landing on look pages
- Now
- –
- Target
- +300%
- By
- 90 days
Steps
Export the looks
Handle, tags and Shop the Look items for all 297.
E-commerce Manager 1 day
Write a naming rule
Main garment + colour/fabric + occasion.
Content Lead 1 hour
Rename wedding looks
Titles, descriptions and alt text for the 42.
Content Lead 3 days
Rename business looks
The 99 business casual and 77 business looks.
Content Lead 1 week
Build occasion hubs
Wedding, date night, business casual and formal pages.
E-commerce Manager 3 days
Link the hubs
From capsule pages, the wedding page and the menu.
E-commerce Manager 1 day
Check indexing
Search Console for the renamed pages.
E-commerce Manager 2 weeks
Finish the rest
Date, casual and formal looks.
Content Lead 2 weeks
Why it works
Rename each look by what it shows ("Black Super 180s Tuxedo with Honeycomb Crossover Shirt: Wedding Look"), write a two-sentence description with the occasion and the fabrics, add alt text to every photo, and group the looks into indexed hubs by occasion (wedding, date night, business casual, formal). Start with the 42 wedding looks and the 99 business casual looks. Link each hub from the capsule pages and the wedding page.
These pages already exist and already show real, styled outfits. Naming them turns 297 dead pages into long-tail entry points for buyers who are planning an outfit, and image search and Pinterest need the alt text to show them at all.
Ready to use
CopyLook page template
Title: [Main garment] in [colour/fabric] with [second piece]: [Occasion] Look | Articles of Style Description: A [occasion] look built around our [garment] in [fabric], paired with [shirt] and [accessory]. Every piece is custom made to your measurements. Alt text: Man wearing a [colour] [garment] with [shirt] and [accessory], [setting] Hub: /collections/[occasion]-looks
Risks and how to handle them
Changing handles breaks links
Keep the handles and change only titles, descriptions and alt text.
Hours of writing
Draft from the tags and products, then edit by hand.
Evidence
- Your websiteThe store has 297 "Look" product pages (handles look-1005 to look-1012 and earlier, published October 2022 to May 2025), all listed in the product sitemap. Each is named by number only: Look 1012 has the page title "Articles of Style | Look 1012", the meta description "Look 1012" and an empty social description. 234 of the 297 have no description at all, and their photos have no alt text. Their tags show what they are: 109 "Out with Friends", 105 "Date", 99 "business casual", 77 "business", 42 "wedding", 14 "Formal".Source
- Your websiteLook 1012 "Shop the Look" lists a Honeycomb Crossover Shirt ($345, "This product is SOLD OUT"), a Super 180s Tuxedo ($3,995) and a Classic Formal Bowtie ($165). Below it the page repeats the homepage pitch, the capsule tiers and the FAQ.Source
- Your websiteWeddings: /pages/weddings shows 24 customer weddings (for example Alex in Marfa, Texas: "We also dressed his 9 groomsmen in different lightweight earthtones!"). /pages/articles-of-style-weddings says "We've done thousands of weddings all over the world", offers remote bespoke fittings "for your big day" for "you (and your wedding party)", and lists tuxedos from $2,295 to $4,995 with a Calendly "Book a Call".Source
- Google PageSpeedChrome UX Report (real visitors): LCP 1.9 s, INP 112 ms and CLS 0.02 at the 75th percentile, so the site passes Core Web Vitals; LCP is 18% slower than a year ago.Source