Tower 28 Beauty
https://www.tower28beauty.comrobots.txt.AggregateRating with real review counts.FAQPage or HowTo schema on checked pages.sameAs array (9 profiles).What needs fixing
The top 9-criterion grid shows all checks. Detail below covers only items that need action.
- Checked
Tower 28 Beauty/sitemap.xml- Found
- Sitemap missing, invalid XML, or has no
<lastmod>timestamp within the past 90 days. - Fix
- Generate a valid sitemap that includes product URLs with accurate
<lastmod>timestamps, and keep it current. Shopify emits this automatically for standard themes.
- Checked
- Homepage and discoverable FAQ / how-to-use / about pages
- Found
- No
FAQPageorHowToJSON-LD detected. If your store publishes how-to / routine content, it's currently invisible as structured data. - Fix
- Wrap existing FAQ content in
FAQPageJSON-LD and any routine / tutorial content inHowToJSON-LD. These map directly to the "how do I use X" queries AI shopping agents handle. schema.org/FAQPage / HowTo.
- Checked
- 5 PDP titles sampled from the sitemap
- Found
- Only 2/5 titles include specific use-case, target audience, or differentiator cues. Examples: "Tower 28 The Complexion Trio | Foundation, Concealer + Powder Set", "Secret Sample | Tower 28 Beauty".
- Fix
- Expand generic titles ("Brand Name Face Cream") with specific differentiators ("Retinol Alternative Night Serum for Sensitive Skin"). Titles match the natural-language shopper queries AI agents parse.
- Checked
- 5 sampled PDPs — full description text
- Found
- 2/5 descriptions cover 3+ of: target skin/fit type, comparison to similar products, ingredient/material rationale, sizing reasoning, usage guidance, counter-indications. Most are spec-heavy with limited buyer context.
- Caveat
- Evaluation via rendered-response text. Descriptions may include buyer-context content in expandable sections or tabs that weren't surfaced.
- Fix
- Add a structured "Why you'll love it" block to every PDP — who it's for, how it compares, when to use, what it isn't for. At catalog scale this is a content pipeline (LLM-assisted generation from existing spec sheets is plausible).
View complete check log (all 9 criteria)
robots.txt allows all 8 tested bots (GPTBot / PerplexityBot / ClaudeBot / anthropic-ai / Google-Extended / Amazonbot / CCBot / FacebookBot).
<lastmod> within 90 days.
Product JSON-LD (name, image, brand, offers, identifier).
ratingValue and reviewCount.
Organization JSON-LD with name, url, and sameAs (9 profiles).
Fix priority
Ranked by leverage on agent discoverability, highest first.
-
Wrap FAQ / how-to content in
FAQPageorHowToJSON-LDMaps directly to "how do I use X" queries AI shopping agents handle. Lightweight if the FAQ template has Q&A as structured data; heavier if mixed with presentational HTML.
-
Expand PDP descriptions with buyer-context cues
Who it's for, how it compares, when to use, what it isn't. The largest content project but touches every product, so compounds across the catalog. LLM-assisted generation from existing spec sheets is viable.
-
Generate a fresh, valid
sitemap.xmlInclude product URLs with accurate
<lastmod>timestamps. Standard Shopify themes emit this automatically; custom builds may need a plugin.
Implementing the top fixes would move this brand materially upward on this framework. Final score depends on implementation quality and broader content improvements.
The real story
Tower 28 Beauty is around the category median — not yet agent-ready, but not structurally behind.
A 5/9 score sits in the middle of premium DTC beauty. Implementing 2-3 targeted fixes would lift this brand into the top tier.