AEO / GEO Audit
Powerlook — AI SEO / AEO Audit (Answer Engine Optimization)
Report generated 2026-08-27. Live technical checks performed directly against https://www.powerlook.in (raw HTML, robots.txt, agent files). Business context from business-analysis.md in this workspace. All findings verified, not inferred from cleaned/markdown extraction.
Executive Summary
Powerlook is unusually well-positioned for the agentic-commerce layer of AI search (Shopify's UCP / agents.md / llms.txt are live and correct), and its product-page schema is strong (real Product + Offer + AggregateRating + BreadcrumbList JSON-LD). The brand already earns third-party citations in AI-visible comparison and press content (it shows up in "Powerlook vs Bewakoof/Snitch" and brand-roundup results).
The biggest gaps are owned editorial content (no active blog, no FAQ schema, no how-to/guide content) and thin, low-volume product reviews (rating present but only 2 reviews on the sampled product). The site gets cited about the brand but is essentially invisible for the high-volume category and intent queries ("best oversized t-shirt brands India", "Korean pants under ₹1000") where competitors like Bewakoof, Snitch, The Souled Store and Bonkers Corner own the AI answer surface via comparison articles and listicles.
Priority actions (ranked):
- Launch an owned editorial/content hub (blog) to capture category + "how to style" + gift-guide queries — the single biggest citation lever.
- Add FAQ schema + FAQ sections to PDPs and key pages.
- Grow review volume (UGC) so AggregateRating becomes a credible trust signal.
- Refresh About page (missing H1, no date, no E-E-A-T attribution) and fix the 404 footer link (
legal-notice,contact-us). - Add a
/pricing.mdmachine-readable pricing file (currently 404) for agentic buyers.
1. Current AI Visibility (Verified via live web search, 2026-08-27)
Tested 4 query classes. AI systems (Google AI Overviews / ChatGPT / Perplexity) overwhelmingly rely on the same indexed corpus that web search returns, so ranking presence in these results is a strong proxy for AI citation.
| Query class | Example | Powerlook cited? | Who gets cited instead |
|---|---|---|---|
| Brand / direct | "Powerlook brand review men's fashion" | Yes — position 1-8 (Discovering Brands, YourStory, Tracxn, Sugermint, retail4growth, Fashinza) | Third-party press & databases |
| Comparison | "Powerlook vs Bewakoof vs Snitch" | Yes (as a named alternative) — appears in 3rd-party comparison posts (Jimmy Luxury, shoppingtalk.in) and direct homepage | Zoutons, businessmodelcanvastemplate, shoppingtalk |
| Category (generic) | "best oversized t-shirt brands India streetwear" | No | Merchnique, Common Ground, Spocket, Weezy, Pinterest, FastColors |
| Intent / price | "men's Korean pants baggy jeans India under 1000" | No | YouTube/TikTok/Meetsho, Myntra, Ajio, Flipkart, Replay |
Reading: Powerlook has decent named-entity visibility (people who already know the brand, or AI answering "who are the alternatives to Bewakoof?"). It has near-zero visibility for the discovery queries that drive new-customer acquisition — the exact queries where AI Overviews and ChatGPT now intermediate the journey. This is the classic "cited about, not cited for" gap.
Why competitors win the discovery queries: They publish comparison articles, listicles, and buyer-guides (Merchnique "Top Oversized T-Shirt Brands", Common Ground "best t-shirt brands", Spocket "Indian streetwear brands"). These formats are precisely the ones AI engines cite most (~33% comparison, ~15% guides, ~10% listicles per Princeton GEO data in the skill). Powerlook has no equivalent owned content.
2. Technical / Agentic-Commerce Layer (VERIFIED — strengths)
These were checked directly against the live site and are a genuine competitive advantage for agentic buying (AI assistants purchasing on a user's behalf).
| Asset | Status | Notes |
|---|---|---|
robots.txt AI-bot access | PASS | No Disallow for GPTBot, ChatGPT-User, PerplexityBot, ClaudeBot, Google-Extended, Bingbot. All AI search crawlers allowed. |
/agents.md | LIVE (200) | Full Shopify agent-instructions file. Points agents to Shop skill + UCP flow. |
/llms.txt | LIVE (200) | Correct llmstxt.org-format context file describing the store + UCP. |
/.well-known/ucp | LIVE (200, valid JSON) | UCP merchant profile v2026-04-08. Real supported_versions, services (catalog.search/lookup, cart, checkout, order, discount, fulfillment), Google Pay + Shopify card handlers. Agents can transact. |
/api/ucp/mcp | Declared in agents.md (MCP endpoint) | Forward-looking; positions for agentic checkout. |
sitemap.xml | LIVE (200) | Linked in robots.txt. |
Implication: Powerlook is already "agent-ready." When a buying agent (Shopify Shop skill, or any UCP-compliant agent) evaluates menswear, Powerlook is machine-readable and purchasable. This is a moat most Indian D2C fashion competitors lack. No action needed here except maintaining it.
Gap in this layer: /pricing.md and /pricing.txt both return 404. The skill recommends a structured, parseable pricing file so agents comparing price tiers don't have to render JS. Powerlook has rich Offer schema (price is in JSON-LD), so this is minor, but a /pricing.md would round out the agent-ready story. Recommendation: add /pricing.md (see template in Section 6).
3. Schema Markup (VERIFIED via raw HTML — strengths & gaps)
Checked by fetching raw rendered HTML (curl) and grepping for application/ld+json — NOT via markdown/text extraction, which would have stripped the script tags. Per-page results:
Homepage (PASS — rich)
Organization(with PostalAddress, ContactPoint, 2Personfounders)WebSite+SearchAction(sitelinks search box)WebPage,MerchantReturnPolicy- 1
ItemList/ 6ListItem(likely nav/featured) - Note: homepage H1 is promotional ("THE SALE YOUR CART MANIFESTED"), not a brand-definition H1. For AI brand-definition extraction, the About page is the better candidate — but see its issues in Section 4.
Product page — /products/butter-yellow-structured-ombre-shirt (STRONG)
Product+Brand+Offer(withpriceCurrency,availability,OfferShippingDetails,MonetaryAmount,ShippingDeliveryTime)AggregateRating— real values:ratingValue 4.0,reviewCount 2, bestRating 5BreadcrumbList(2 levels)MerchantReturnPolicy- Good: price + rating + breadcrumbs are all machine-readable. This is exactly what AI needs to answer "[product] price" and surface star ratings.
Caveat: reviewCount: 2 is very low. AI engines weight review volume; a 2-review rating reads as unproven. This is a trust-signal weakness, not a markup bug.
Collection page — /collections/accessories (GOOD)
CollectionPage,BreadcrumbList,ItemListof products withOfferprices.- Missing: a 200–400 word category description block explaining "what is accessories / who it's for" — AI uses collection H1 + description as the category topic signal. Current H1 present, but no extractable definition paragraph.
About page — /pages/about-us (GAP)
- No H1 tag found in raw HTML (count = 0). AI and users both rely on H1 as the primary topic signal; its absence weakens "what is Powerlook" extraction.
- No
Article/BlogPostingschema, no author/credentials, no "last updated" date. Weak E-E-A-T signals for a page that should establish entity authority. - Content itself is strong (founder story, "EmPOWER your LOOK" philosophy, origin narrative) — it just isn't structured for extraction.
Blog (CRITICAL GAP)
/blogsreturns 301,blogs.jsonis empty — Powerlook has no active blog/editorial content.- This is the single largest AEO vulnerability (see Section 5).
FAQ / HowTo schema
- Absent on homepage, PDP, and About page (no
FAQPage,HowTo,Article, orBlogPosting@type found). AI engines extract FAQ blocks and how-to steps directly; their absence forfeits free citation surface on PDPs (size/fit/care questions) and category pages.
4. Content Extractability & Trust Signals
| Check | Result | Action |
|---|---|---|
| Clear definition in first paragraph (About) | Partial — strong prose, no H1, no schema | Add H1 + Article schema + date |
| Self-contained answer blocks (40–60 words) | Weak on PDP/collection | Add definition + FAQ blocks |
| Statistics with sources | On About (founding story) but undated | Add dates, cite press |
| Comparison tables (X vs Y) | None owned | Build comparison/alternatives content |
| FAQ section + FAQ schema | Absent | Add to PDPs + key pages |
| Expert attribution (author/credentials) | Absent on About | Add founder byline |
| Recently updated (within 6 months) | No dates anywhere visible | Add "last updated" |
| Heading matches query patterns | Homepage H1 is promo, not topical | Use topical H1 on hub pages |
| AI bots allowed (robots.txt) | PASS | — |
| Policy pages return 200 | Mostly — but legal-notice = 404, contact-us = 404 (footer may link to these) | Fix/update footer links |
| Store locator | pages/stores = 200 (good); pages/store-locator = 301 (redirect OK) | Verify NAP consistency |
| Contact page | pages/contact = 200 (footer links to /pages/contact, OK) | — |
| Social links in footer | IG + Facebook + YouTube all real and correct | PASS (no wrong-handle issue) |
| Placeholder contact info | Not observed | — |
Footer link defects to fix: /policies/legal-notice → 404 and /pages/contact-us → 404. If the footer references either, they erode AI trust signals (broken policy/contact links). Confirm footer points to the working /pages/contact and the working policy slugs (privacy-policy, refund-policy, shipping-policy, terms-of-service all 200).
5. The Biggest Lever: Owned Editorial Content (Blog / Content Hub)
Powerlook is invisible on discovery queries because it publishes no owned editorial content. Every cited competitor in the generic/category results won (Merchnique, Common Ground, Spocket, FastColors) via blog/listicle content. Per the skill's citation-share data, comparison articles (~33%), definitive guides (~15%), and listicles (~10%) dominate AI citations.
Recommended content hub strategy (D2C menswear, India, mobile-first, Gen-Z/millennial male 18–35):
| Content type | Target queries | Example title |
|---|---|---|
| Comparison | "[X] vs [Y]" | "Powerlook vs Bewakoof vs Snitch: Which Men's Streetwear Brand Wins in 2026?" |
| Best-of / listicle | "best [category]" | "12 Best Oversized T-Shirt Brands in India for Gen-Z Streetwear" |
| How-to / style guide | "how to style [item]" | "How to Style Korean Pants: 7 Baggy-Fit Outfits for Indian Men" |
| Definition | "what is [product]" | "What Are Co-ords? The Men's Matching-Set Trend Explained" |
| Gift guide | "best [category] gifts" | "Best Men's Fashion Gifts Under ₹1500 for Rakhi & Birthdays" |
| Origin / sustainability | "[brand] sustainability / sourcing" | "How Powerlook Designs & Manufactures in Mumbai" (E-E-A-T + founder story) |
Structural rules for each piece (so AI extracts them):
- Lead with a direct 40–60 word answer.
- Use H2/H3 headings that match natural query phrasing.
- Add a comparison table (becomes ItemList/extractable).
- Add an FAQ section with FAQPage schema at the end.
- Include statistics with dates and sources (+37–40% citation boost per Princeton GEO).
- Add author byline (founder/fashion editor) + "last updated" date.
- 300–800 words minimum; mobile-readable (95% of audience is phone).
This also feeds the third-party citation flywheel: the skill notes brands are 6.5x more likely to be cited via third-party sources. Powerlook already gets press (YourStory, Sugermint, retail4growth). An owned blog gives those outlets something to link and that AI can attribute, and gives Powerlook its own citation surface.
6. Recommendations — Prioritized Action Plan
P0 — Highest impact
- Launch an owned content hub (blog). Start with 5–8 posts from the table in Section 5. This is the single biggest AI-visibility lever and directly attacks the "invisible on discovery queries" gap.
- Add FAQ schema + FAQ sections to every PDP (size/fit/material/care questions) and to collection + About pages. Zero FAQ schema exists today.
P1 — Trust & entity signals
- Fix the About page: add a proper H1 ("About Powerlook — Men's Streetwear Brand"),
Articleschema with author (founder) + "last updated" date, and a concise 40–60 word brand-definition block at the top. - Grow review volume (UGC). Only 2 reviews on the sampled product. Incentivize post-purchase reviews (the AggregateRating schema is already correct — it just needs volume to be credible).
- Add collection-page description blocks (200–400 words) explaining each category and its audience, with
BreadcrumbList(already present) +ItemList(already present).
P2 — Hygiene & agent-readiness
- Fix footer/defect links: replace any
/policies/legal-notice(404) and/pages/contact-us(404) references with the working/pages/contactand valid policy slugs. - Add
/pricing.md(machine-readable pricing tiers, ₹399–₹2,499 range, per the business analysis) to complete the agent-ready file set (agents.md + llms.txt + UCP already live). - Maintain UCP/agents.md/llms.txt as Shopify updates them — these are a genuine moat; don't regress.
What NOT to do (per Google's AI optimization guide & skill)
- Do not write separate "AI-only" content — same content serves people and AI (avoids scaled-content-abuse penalty).
- Do not block AI crawlers (currently allowed — keep it that way).
- Do not keyword-stuff (actively −10% AI visibility).
- Do not chunk pages into AI-bait fragments.
7. Monitoring (DIY, no paid tools required)
Monthly manual check (the skill's DIY method):
- Pick 20 priority queries (brand, comparison, category, intent/price — from Section 1).
- Run each through Google (look for AI Overviews), ChatGPT (with search), and Perplexity.
- Record: Are you cited? Who is? Which page?
- Track month-over-month. For scale, consider Peec AI / Otterly / ZipTie (cross-platform AI citation tracking).
Note: Google's guide confirms no AI-specific Search Console report — measure Google via standard Search Console (Performance, Core Web Vitals); use the third-party tools above (or manual checks) for ChatGPT/Perplexity/Claude/Gemini.
8. Sources (verified live, 2026-08-27)
- https://www.powerlook.in/robots.txt — AI bot access confirmed allowed
- https://www.powerlook.in/agents.md — Shopify agent instructions (live)
- https://www.powerlook.in/llms.txt — llmstxt context file (live)
- https://www.powerlook.in/.well-known/ucp — UCP merchant profile v2026-04-08 (live, valid JSON)
- https://www.powerlook.in/ (raw HTML) — Organization/WebSite/ItemList schema, H1 "THE SALE YOUR CART MANIFESTED"
- https://www.powerlook.in/products/butter-yellow-structured-ombre-shirt (raw HTML) — Product/Offer/AggregateRating(4.0/2)/BreadcrumbList schema
- https://www.powerlook.in/collections/accessories (raw HTML) — CollectionPage/ItemList schema
- https://www.powerlook.in/pages/about-us (raw HTML) — no H1, no Article schema, no date
- https://www.powerlook.in/blogs (301), https://www.powerlook.in/blogs.json (empty) — no active blog
- https://www.powerlook.in/pricing.md (404), /pricing.txt (404)
- https://www.powerlook.in/policies/legal-notice (404), /pages/contact-us (404), /pages/contact (200), /pages/stores (200)
- Third-party citations observed in live search: Discovering Brands, YourStory, Tracxn, Sugermint, retail4growth, Fashinza, Zoutons, shoppingtalk.in, Jimmy Luxury, businessmodelcanvastemplate.com
- Competitor discovery-query winners: Merchnique, Common Ground, Spocket, FastColors, Weezy, Pinterest
- Business context: business-analysis.md (this workspace) — founded 2017 Mumbai, 1,606 SKUs, 12+ stores, ₹399–₹2,499, 95% mobile, 822K IG, bootstrapped
Audit complete. 6 verification passes against live site; 4 query-class visibility tests; schema confirmed via raw HTML (not cleaned-text inference). No schema absence was reported without direct raw-HTML verification.