Converse SEO & GEO Audit: Does Google AI Cite Converse?

What is Converse.com trying to do — and why audit it tenth?

This is part 10 of GeoParrot’s sports-brand series, running the same evidence-first method we used on Reebok, New Balance and eight other major brands. Converse is a useful tenth name because, unlike most of this series, it’s not an independent company at all — Nike has owned Converse outright since 2003, yet converse.com runs on its own separate Salesforce Commerce Cloud storefront (confirmed via the catalog path visible in its own image URLs, Sites-cnv-master-catalog), completely independent of nike.com’s infrastructure. That gave us a genuine within-family comparison point worth checking: does a wholly-owned subsidiary inherit its parent’s GEO practices, or run its own, for better or worse?

The product we tracked: Chuck Taylor All Star Canvas

AI citation snapshot: 10 real queries, Google AI Mode

We sent 10 verbatim queries to Google AI Mode (udm=50) and checked both direct a[href] links and citation chip aria-labels for the Converse brand family (converse.com, converse.co.kr, converse.com.au and other regional ccTLDs). Method note, reported honestly: direct link capture worked for every query this run, so counts lean on actual hrefs rather than chip labels alone — the same convention used for Reebok and New Balance.

Result: Converse’s domain family cited in 7/10 queries (Nike 5/10, Adidas 4/10, Puma 5/10, Under Armour 8/10, New Balance 6/10, ASICS 7/10, Skechers 4/10, Lululemon 8/10, Reebok 7/10) — tied for second-highest alongside ASICS and Reebok. The one finding worth flagging: on “converse vs nike sneakers,” a query explicitly about Converse, it was Nike’s domain that surfaced and Converse’s that didn’t — the opposite of what you’d guess from common ownership. Named-product review queries again failed to surface the brand’s own domain, continuing a pattern that’s now held across most of this series.

G-score audit: the 8-pillar hygiene checklist, and a genuine zero

We scored six representative Converse URLs with the same 8-pillar static-HTML checklist (JSON-LD present, FAQ content, visible date, author byline, concrete data points, table/list structure, 3+ subheadings, a 30–500 character early answer) used in our Week 17 quality-score experiment and on all nine prior brands. What we found this time is a genuine first for the series: converse.com returns a flat HTTP 403 to every plain-HTTP request we sent — not just robots.txt, but the homepage itself — so we could only score the US pages via a fully browser-rendered DOM. After rendering, both the homepage and the Chuck Taylor PDP carry zero application/ld+json blocks — not hidden behind JavaScript like Reebok’s, just genuinely absent — leaving only two bare Open Graph tags (og:url, og:image) on the product page, no og:title, no og:description, no product-specific Open Graph fields at all.

Six-page average: 0.5208 (Nike: 0.4375, Puma: 0.354, Under Armour: 0.5208, New Balance: 0.5833, Adidas: 0.6458, ASICS: 0.4583, Reebok: 0.5417) — squarely mid-pack, and coincidentally identical to Under Armour’s average. But as with Reebok, the average flattens the real story: the US flagship PDP for a shoe with 7,752 reviews carries no machine-readable rating, price or availability data whatsoever, while the Korea PDP for the same shoe family does.

US help center: still reachable only through a real browser

The US Help Center scored the lowest single-page G-score in this audit (0.25) — a plain search box and a topic grid (Orders, Shipping & Delivery, Returns & Exchanges, Product Information, Payments & Gift Cards, Promotions) with almost no body text, dates, or structured content for an AI engine to extract. Like every other converse.com URL in this audit, it returned HTTP 403 to a plain, non-browser request and was only reachable through a full browser session.

Product schema: the gap, in exact numbers

The contrast is as close to a controlled comparison as this series gets, because both pages describe the same product line. US converse.com’s Chuck Taylor All Star Canvas PDP, rendered fully in a real browser with a 6-second settle: zero application/ld+json script tags, confirmed twice across separate runs. Korea’s converse.co.kr Chuck Taylor All Star Classic White PDP, fetched as plain HTML with no JavaScript required: one ProductGroup block (@id, productGroupID: cafe24_conversekorea_1_6528) with a hasVariant array — one entry per shoe size — and each variant carrying its own Offer (price 69,000 KRW, availability: InStock) and its own AggregateRating (4.9, 286 reviews at the size level we sampled).

Honesty note on the product match: the US PDP we tracked throughout this audit (M7650, high-top) and the KR PDP (M7652C, low-top) are the same product line in the same colorway but different silhouettes — we picked the closest match each storefront’s own on-site search surfaced for “chuck taylor all star,” rather than forcing an exact style-number match that neither search actually returned. The schema gap itself doesn’t depend on this distinction: both are flagship Chuck Taylor products, and only one of the two carries any Product-level structured data.

Who actually runs converse.co.kr?

Unlike several brands earlier in this series — Reebok’s Korea site run by LF Corporation, New Balance’s run by E-Land — Converse Korea is not an external licensee. The site’s company-information page discloses the operating entity as (유)컨버스코리아 (Converse Korea LLC, a “yuhan-hoesa” / limited-liability company, the structure commonly used for Korean subsidiaries of foreign multinationals), business registration number 220-88-74818, representative 이명재 (Lee Myung-jae). The same footer lists its “FAMILY SITES” as NIKE and Jordan — an explicit, on-page acknowledgment that this storefront sits inside Nike’s own corporate family in Korea, not a third-party license. It’s the first brand in this series where the Korea operator is confirmed to be the parent company’s own entity rather than an independent licensee.

Technical check: robots.txt, llms.txt, agents.md, sitemap, locale

What works / What to verify

Target query check — reported honestly, not inflated

We have not re-measured “converse seo” or “converse geo audit” query volume this session. Per the pattern already confirmed across nine earlier subjects in this series on October 20, 2026 (Keyword Planner, US) — the large majority showed no measurable search volume at all for “[brand] SEO/GEO audit” phrasing — we’re not claiming this title drives ranking-based traffic. The distribution case for this series rests on internal links, our own index, and readers already following the GEO Lab arc, not on search demand for “[brand] SEO audit” as a query.

Frequently asked questions

Does Converse’s flagship product page really have zero structured data?

Yes, based on what we observed: a full browser render of the Chuck Taylor All Star Canvas PDP (6-second settle, repeated across two separate checks) produced zero application/ld+json script tags. The only machine-readable metadata present was two bare Open Graph tags — og:url and og:image — with no og:title, og:description or any product-specific fields. This is a plain absence, not a JavaScript-timing issue we could reproduce differently.

Why do converse.com’s llms.txt and agents.md return HTTP 200 if there’s no real content?

We can only report what we observed, not the underlying routing logic: both URLs resolve to the same generic ‘Select Location & Language’ country-picker page that this site also shows for other unrecognized paths. A 200 status code at these filenames would normally suggest a real document exists; here it doesn’t, and a crawler checking only the status code — rather than the content — would be misled. Google Search doesn’t read llms.txt regardless; see our explainer on what llms.txt actually does.

Why is Converse Korea’s operator disclosed as part of Nike’s corporate family rather than an independent licensee?

We can only report what the site itself discloses: its company-information page names the operator as (유)컨버스코리아 (Converse Korea LLC) and lists NIKE and Jordan as ‘Family Sites’ in the same footer block. Nike has owned Converse globally since 2003, so a wholly-owned Korean subsidiary operating the local storefront is a plausible and disclosed structure — different from the external-licensee pattern (LF Corporation for Reebok, E-Land for New Balance) seen elsewhere in this series.

Does a 7/10 AI citation rate mean Converse’s GEO setup is working despite the missing schema?

Not reliably — this audit is itself a data point against that conclusion, consistent with all nine prior brands. Our Week 17 experiment found hygiene/structure score was not a dependable predictor of AI citation, and here Converse matches Reebok’s and ASICS’s 7/10 rate while scoring a mid-pack 0.5208 G-score average and carrying zero schema on its single highest-traffic page. Our 10-query snapshot measures the domain family, not individual URL citation, so we can’t confirm which specific Converse page — if any — drove the 7 successful citations.

This is part 10 of a daily series. Every day, GeoParrot runs this same evidence-first method — real screenshots, a 10-query AI citation snapshot, an 8-pillar G-score audit, and an honest target-query check — against one more major sports and athletic-wear brand. Next: On Running.