LoQo (wearloqo.com) — AI SEO / Answer Engine Optimization (AEO) Audit

1. Executive Summary

LoQo is unusually well-prepared for agentic / machine-readable commerce compared to a typical sub-scale Shopify brand — Shopify has auto-generated llms.txt, agents.md, and a live .well-known/ucp discovery profile, and robots.txt does not block any AI crawler (GPTBot, PerplexityBot, ClaudeBot, Google-Extended, Bingbot are all allowed). That covers Pillar 3 (Presence for agents) above average.

However, three structural gaps cap LoQo's citation ceiling in AI-generated answers:

1. No aggregateRating in Product schema even though Judge.me star ratings render on the page → AI engines read every product as "unreviewed." This is the single biggest e-commerce AEO mistake and the top fix.
2. The documented MCP endpoint (/api/ucp/mcp) returns 404, while the UCP discovery doc and robots.txt both tell agents to use it. Agents following LoQo's own instructions hit a dead end at the catalog-search step. The underlying capability exists at the *.myshopify.com path, so this is a routing/reference mismatch, not a missing feature — but it breaks the documented flow.
3. Weak homepage metadata and entity graph: homepage has no usable <meta name="description"> (only og:description="LoQo"), its H1 is the logo image (no topical H1), and the Organization sameAs array is eight empty strings — so AI systems get no social/entity signals to build LoQo's knowledge-graph identity.

On content, LoQo ranks for branded + "alpargata" queries (D2C product #2 behind Amazon's LOQO listing, Myntra #3) but is absent from non-branded category/best-of queries ("best alpargata espadrille shoes men India under 3000" → top 5 are Amazon/Flipkart/TOMS, no LoQo). That is exactly the query class AI Overviews and Perplexity cite comparison/best-of content for. Closing that gap is the highest-leverage organic AEO play.

New finding vs. business-analysis.md: web search confirms an Amazon.in "LOQO" espadrille-loafers listing exists (B0GSRPRPTF, HTTP 200) — correcting the earlier "no Amazon presence" conclusion. Brand authorization is unconfirmed (could be a third-party seller); flag to upstream task.

AEO readiness score: ~6/10 (strong agentic infra, weak review/entity signals and category content).

2. AI-Readiness Scorecard (live checks)

3. Pillar-by-Pillar Findings

Pillar 1 — Structure (extractability)

Strengths

• FAQ page is genuinely AI-extractable: 11 natural-language Q&A pairs wrapped in FAQPage schema. Per the skill, FAQ schema boosts direct Q&A extraction.
• Blog posts are substantive (one post ~15K words, 5 H2 sections, Article schema with author). Far above typical thin D2C blogs.
• Product PDPs have clean H1 ("Alpari Bold Navy Slip-ons") and real Product/Offer schema with variant pricing.

Weaknesses

• No aggregateRating (see §4). Highest-impact structural fix.
• No BreadcrumbList on collection/product pages → AI can't infer category hierarchy ("slip-ons → men's casual → LoQo").
• Homepage has no descriptive H1 or meta description → the page AI systems most often land on for brand queries gives them almost no structured topic/summary signal beyond the title tag ("LoQo | The Thousand Mile Shoe").
• Collection pages lack H1 → category intent signal relies solely on <title> and meta description.
• Definition/comparison blocks for "What is an alpargata?" / "LoQo vs [competitor]" are not stand-alone extractable passages on the site (they live inside long blog prose). AI Overviews favor 40–60 word self-contained answer blocks; LoQo doesn't yet offer these as discrete, citable units.

Pillar 2 — Authority (citable)

• No original statistics or named-expert content surfaced. Blog posts use a podiatrist angle ("Do podiatrists approve LoQo Alps?") but contain no cited podiatrist quote, name, or credential — missing the +30% "quotation" and +25% "authoritative tone" boosts from the Princeton GEO study.
• Entity graph is empty (sameAs = 8 blanks). AI systems can't confirm LoQo's identity across Instagram, Facebook, Myntra, Amazon. Populating sameAs with the real profile URLs is a cheap, high-value fix.
• Reviews exist but aren't structured. Judge.me ratings show visually; without aggregateRating JSON-LD, AI sees no rating count — and review volume is a strong trust/citation signal for "best footwear" queries.
• Freshness: blog posts and homepage copy are recent (Alps banner updated 2026-07-19), but no explicit "Last updated" date is shown on content — AI recency weighting is weaker without it.

Pillar 3 — Presence (where AI looks)

• Agentic infra is ahead of the curve: llms.txt + agents.md + UCP discovery present. This positions LoQo for agent-driven buying (ChatGPT-with-search, Claude, Perplexity, and emerging "buy-for-me" agents). The /api/ucp/mcp 404 is the one blemish (§4).
• Marketplace presence helps indirectly: Myntra (confirmed) and Amazon.in (newly found) give AI systems additional indexed LoQo surfaces to cite.
• Third-party authority is near-zero: no Wikipedia page, minimal Reddit/Quora footprint, no PR/awards (per business-analysis.md §23). Brands are 6.5x more likely to be cited via third-party sources than their own domain — this is LoQo's structural weakness for non-branded queries.
• Social signals unwired: Instagram (@loqo.ofc) and Facebook are live but absent from sameAs; no YouTube/Twitter/LinkedIn.

4. Key Technical Issues (detail)

4.1 /api/ucp/mcp returns 404 (breaks documented agent flow)

• llms.txt, agents.md, and robots.txt all instruct agents: "MCP endpoint — POST https://wearloqo.com/api/ucp/mcp."
• Live check: curl https://wearloqo.com/api/ucp/mcp → 404.
• The UCP discovery JSON points the actual handler at https://cd0rvq-cf.myshopify.com/api/ucp/mcp (which is the functional Shopify path).
• Impact: an agent that follows LoQo's own /llms.txt instructions to search_catalog via MCP will fail at step 2. Read-only browsing (HTML + /products/{handle}.json) still works, so citation is unaffected — but agentic purchase flows are broken on the loqo.com domain.
• Fix: either proxy/route /api/ucp/mcp → the *.myshopify.com endpoint, or update llms.txt/agents.md/robots.txt to reference the working endpoint. Low effort, protects the brand's agentic-commerce investment.

4.2 Product schema missing aggregateRating

• Sampled PDPs (/products/alpari-bold-navy, /products/alpari-bold-olive) return Product + multiple Offer blocks but no aggregateRating / ratingCount / ratingValue.
• Judge.me star UIs render client-side, so the data exists — it just isn't emitted in JSON-LD.
• Fix: add aggregateRating (with ratingValue + ratingCount) to the Product JSON-LD, sourced from Judge.me. This is the highest-ROI single change for AI trust on product queries.

4.3 Organization sameAs empty

• Homepage Organization schema contains "sameAs": ["","","","","","","",""].
• Fix: populate with https://www.instagram.com/loqo.ofc/, https://www.facebook.com/p/LoQo-61575309347924/, https://www.myntra.com/loqo, and the Amazon.in store (once brand authorization confirmed).

4.4 Homepage metadata gap

• No <meta name="description">; og:description is literally "LoQo".
• Fix: write a 150–160 char description leading with the answer ("LoQo makes Mediterranean-inspired Alpargata slip-ons and men's comfort footwear in India, ₹995–₹4,199, with EMI") and set a real og:description.

4.5 Policy-handle mismatch in agent docs

• llms.txt/agents.md link /policies/returns-refunds (404). The live handle is /policies/refund-policy (200). Minor, but agents reading the doc get a broken trust link. Fix the URL in both files.

5. Query Opportunity Map

Why this matters: AI Overviews fan out from a single query into related sub-queries. A brand retrievable only for its own name misses the fan-out. Covering the cluster (definition + best-of + vs + where-to-buy + gifting) makes LoQo retrievable across the whole topic graph.

6. Recommendations (prioritized)

P0 — High impact, low effort (do first)

1. Add aggregateRating to Product JSON-LD (Judge.me-sourced). Biggest AI-trust lift; fixes "unreviewed" perception.
2. Fix /api/ucp/mcp 404 (route to working *.myshopify.com endpoint or correct the doc references). Restores the brand's agentic-commerce flow.
3. Populate Organization sameAs with real IG / Facebook / Myntra / Amazon URLs.
4. Homepage meta description + og:description (currently "LoQo" only).
5. Add H1 to collection pages (currently none) + a 200–400 word category description block per collection.

P1 — Medium effort, high strategic value

1. Add BreadcrumbList schema to collection + product pages.
2. Build best-of / comparison content ("Best Alpargata Shoes India 2026", "LoQo vs Red Tape / Asian") — the missing query class.
3. Create a "Where to Buy" page consolidating D2C + Myntra + Amazon (newly found) with direct links.
4. Add hreflang="en-IN" even as a single-market site.
5. Fix policy-handle mismatch in llms.txt/agents.md (returns-refunds → refund-policy).

P2 — Ongoing / lower urgency

1. Expand blog cadence (currently ~3 posts) with definition/FAQ/statistic-rich pieces; add explicit "Last updated" dates.
2. Pursue third-party presence: answer relevant Reddit/Quora footwear questions with depth; seek a Wikipedia mention if notability is established; light PR.
3. Add a /pricing.md (optional) summarizing the ₹995–₹4,199 range + EMI, for agent readability — though /products.json + UCP already expose pricing.
4. Verify Amazon.in LOQO listing brand authorization and, if official, wire it into sameAs and the Where-to-Buy page.

7. Citation Landscape (competitive)

• For branded "LoQo" queries, LoQo's own D2C site and Myntra already surface — favorable baseline for AI Overviews (which correlate with traditional rankings).
• For non-branded category queries, incumbents (Red Tape, Asian Footwears, Bata, TOMS, plus Amazon/Flipkart aggregators) dominate. LoQo is sub-scale on awareness (FB 0 reviews, no traffic rank) — consistent with the business-analysis SWOT.
• Actionable wedge: the "alpargata / espadrille" hero concept is distinctive and under-covered by mass-market Indian incumbents. Owning "best alpargata India" content is a realistic path to AI citation leadership in a narrow but high-intent niche.

8. Sources Cited (live, 20 Jul 2026)

• https://wearloqo.com/robots.txt — AI crawler allowlist verified
• https://wearloqo.com/llms.txt — agent instructions (200)
• https://wearloqo.com/agents.md — agent instructions (200)
• https://wearloqo.com/.well-known/ucp — UCP merchant profile (200)
• https://wearloqo.com/api/ucp/mcp — MCP endpoint (404, flagged)
• https://wearloqo.com/ (homepage) — title, H1, meta description, Organization schema
• https://wearloqo.com/products/alpari-bold-navy — Product/Offer schema, aggregateRating absence
• https://wearloqo.com/collections/casual-shoes-n (and loafers-n, sliders-n, alpargatas, espadrilles) — H1/meta/collection checks
• https://wearloqo.com/pages/faqs — FAQPage schema (11 Q/A)
• https://wearloqo.com/blogs/news/what-makes-loqo-alps-so-comfortable — Article schema, structure
• https://wearloqo.com/policies/{privacy-policy,refund-policy,shipping-policy,terms-of-service} — all 200
• https://wearloqo.com/policies/returns-refunds — 404 (mismatch vs llms.txt)
• https://wearloqo.com/sitemap.xml + sitemap_products/collections/pages/blogs — URL inventory
• https://www.myntra.com/loqo — confirmed marketplace presence
• https://www.amazon.in/LOQO-Espadrille-Loafers-Alpargata-Footwear/dp/B0GSRPRPTF — Amazon.in LOQO listing (HTTP 200; NEW vs business-analysis "no Amazon")
• Web search probes: "LoQo men footwear India alpargata slip-ons" (LoQo #2, Amazon LOQO #1, Myntra #3); "best alpargata espadrille shoes men India under 3000" (no LoQo in top 5)

Note on method: this is an AEO audit, not a replacement for the business analysis. It reuses that context and adds live AI-readiness signals. No figures were fabricated; where a signal could not be verified (e.g., Amazon brand authorization, exact review counts), it is explicitly marked unconfirmed.