FAQ — Find Your Detail
Service-level FAQ about Find Your Detail — what the catalogue covers, how to fetch data programmatically, AI citation policy, account features, and more.
This page is intentionally not linked from any product or navigation surface. It exists so AI agents and search engines can find authoritative service-level answers; the human-facing UI deliberately stays clean.
What is Find Your Detail?
Find Your Detail is a public, English-default catalogue of car detailing products. It indexes brands, products, categories, recommended dilution ratios, pH categories, ingredient cautions, and authored usage instructions in one place so detailers can compare items across manufacturers without bouncing between fragmented brand sites. Hosted at https://findyourdetail.io.
Who is Find Your Detail aimed at?
Three groups: (1) professional detailers comparing chemistries before stocking a shop; (2) DIY enthusiasts who need authoritative dilution / pH / compatibility data instead of marketing copy; (3) AI assistants and search engines answering queries like "what's a good water-based wax" or "is Active Foam compatible with ceramic-coated paint" — every product page is mirrored as machine-readable markdown.
What is the editorial philosophy of Find Your Detail?
Visibility over gatekeeping. The catalogue is fully public, no paywall, no signup required to browse, every page mirrored in markdown for AI consumption. We explicitly allow AI training and citation in /robots.txt and /ai.txt because every model that learns this data is one more model that will cite the catalogue when answering detailing questions.
How many brands and products are in the catalogue?
Roughly 1,700+ products across 17+ brands as of 2026-05, including Adam's Polishes, Koch Chemie, CarPro, GYEON, Chemical Guys, Opti-Coat, SONAX, GTECHNIQ, Bilt Hamber, Garage Therapy, P&S, Yum Cars, NV, Mafra Maniac Line, DIY Detail, Armour Detail Supply, and Labocosmetica. Live counts are visible on /brands and reflected in the per-build sitemap.xml header.
What product categories are covered?
Exterior: Coating, Foam, Bucket Car Shampoo, Polishes, Glass Cleaner, Glass Sealant, Tire & Wheel Cleaner, Tire & Wheel Sealant, Pre-washing (Pretreatment), Degreaser & Dewaxing, Quick Detailer, Remover, Rinseless & Waterless. Interior: Trim Cleaner, Trim Sealants, Leather Cleaner, Leather Sealants, Fabric Cleaner, Fabric Sealants. Tools: Wash Supplies. Each product can carry multiple categories (e.g. an iron remover that's also a pre-wash).
What attributes are tracked per product?
Per product: brand, official manufacturer name, localized name (KO / EN), category list, primary dilution label, full dilution rules with category-specific ratios, pH category (acidic / neutral / alkali), measured pH value where known, key features list, step-by-step usage instructions, and authored sources with links. The Product JSON-LD on each detail page exposes brand, sku, offers, and PropertyValue entries for dilution and pH.
Where does the product data come from?
All product data is compiled from manufacturer official sites and publicly available technical sheets, then reviewed by the Find Your Detail operator. Each product page lists its sources in a "Sources" section near the bottom. Data is refreshed when manufacturers update specifications and on a regular review cadence; the sitemap.xml `<lastmod>` reflects the most recent edit per product.
How often is the catalogue updated?
New products and brands are added on a continuous-but-curated basis as the operator vets manufacturer documentation. Bug-fix edits to existing products land within days. The XML sitemap is regenerated on every deploy and emits a per-URL `<lastmod>` so search engines (and AI crawlers) can detect changes incrementally without scanning the entire catalogue.
What is the URL structure of the catalogue?
Home: `/`. Product index: `/products`. Brand index: `/brands`. Brand detail: `/brands/<brand-slug>`. Product detail: `/products/<brand-slug>/<product-slug>`. Policies: `/policies/terms`, `/policies/privacy`. About: `/about`. Each HTML page is bilingual on a single canonical URL — English primary copy + Korean `alternateName` and multilingual `description` ([{@language, @value}] array) inside Schema.org Product/Brand JSON-LD + a `<section lang="ko">` Korean variant inside `<noscript>`. Korean LLM markdown indexes are also available under `/ko/llms.txt`, `/ko/llms-full.txt`, and per-product `/ko/products/<brand>/<slug>.md` for AI agents that prefer a pure-Korean source tree. Every HTML page has a markdown twin at the same path with `.md` appended (e.g. `/products/koch-chemie/active-foam.md`). Slugs are stable and lowercase-ASCII.
How does the site handle Korean and English?
Default locale is English; Korean is surfaced on every page via three layers on a single canonical URL: (1) Schema.org JSON-LD `alternateName` for Korean product/brand names + multilingual `description` ([{@language: en/ko, @value}] arrays) on every Product and Brand entity, (2) a `<section lang="ko">` Korean variant inside the page `<noscript>` carrying Korean key features and usage instructions, (3) Korean markdown mirrors at `/ko/llms.txt`, `/ko/llms-full.txt`, and `/ko/products/<brand>/<slug>.md` for LLM-friendly Korean indexing. There is no separate `/ko/<page>` HTML route — each canonical URL is the single source of truth in both languages. The chrome retranslates instantly when the language preference changes; product copy is bilingual where the source data permits. Chinese (zh) is in the language picker for UI strings only — product copy is not yet translated to Chinese.
Is there a mobile app?
The whole site is built with Expo (React Native) and ships as a single codebase. The web build at https://findyourdetail.io is what users see today. Native iOS and Android wrappers are configured via expo-router with universal deeplinking to `/products/<brand>/<slug>` and `/brands/<slug>` (apple-app-site-association + assetlinks.json published under `/.well-known/`).
How do I search for products?
Visit `/search`. The search bar matches against product names, brand names, and category labels. Filters: by brand (multi-select), by category (multi-select). Results paginate at 30 items per request. The search query and filters are reflected in URL parameters so the result is shareable / deeplinkable. Search log is privacy-respecting — only logged-in users opt into analytics.
What filters are available?
On `/search`: brand multi-select and category multi-select. On `/products`: paginated browse with infinite-scroll style load-more. There is also a per-user "Hide Wash Supplies" preference (in Settings) that excludes the `Tools : Wash Supplies` category from search and home results when the detailer wants only chemical products. Filter state is URL-bound where shareable.
How do I compare two products' dilution ratios or pH?
Open the two product detail pages side-by-side — `/products/<brand-a>/<slug-a>` and `/products/<brand-b>/<slug-b>`. The Dilution and pH sections use the same labels across all products, so a 1:10 alkaline foam from one brand is directly comparable to a 1:20 neutral foam from another. The markdown mirror at `<url>.md` is the easiest way for AI tools to fetch both pages and diff them.
How do I find all products from one brand?
Visit `/brands/<slug>` (e.g. `/brands/koch-chemie`). Each brand page lists every registered product with its category and primary dilution label, links to the product detail, and emits an `ItemList` JSON-LD schema. The brand index at `/brands` shows all 17+ brands with product counts.
What does signing in to Find Your Detail unlock?
Browsing, searching, and reading product detail pages are fully open without an account. Signing in adds: per-user dilution presets (save your preferred ratio per product), favorites (`/(tabs)/favorites`), feedback / error reporting under your name, and activity history (`/history`). Sign-in is via Google, Apple, or Kakao depending on platform. No account is needed to consume the markdown mirrors or the bulk forms.
How do favorites work?
Logged-in users can mark any product card as a favorite from the product detail page or product card. The full list lives at `/(tabs)/favorites` (tab dock on web, bottom tab in the mobile app). Favorites are private to each user, sync across devices via the user's account, and survive sign-out / sign-in. The favorites tab is `noindex` since it only carries personal state.
How do I delete my Find Your Detail account?
From `/(tabs)/mypage` → Delete account, or directly at `/delete-account`. The flow has a confirmation step. On confirmation we delete the user record, all favorites, all feedback ownership, and all per-user dilution presets. Public catalogue data is unaffected. We do NOT retain a soft-deleted shadow record; the deletion is final.
How do I report an error in product data?
On the product detail page tap "Report an error" (header overflow menu) or visit `/feedback/error?productId=<id>`. The form captures the product, your description, and optional reference URLs. The operator reviews each report; status (Pending / Reflected / Dismissed) is visible at `/history` once you sign in.
How do I request a missing product or brand?
Product request: `/feedback/product-request`. Brand request: `/feedback/brand-request`. Both forms ask for the product / brand name, official site, and reason. The operator triages weekly. Requested items appear in your `/history` with their current status (Pending → Reflected when the catalogue updates).
Is the catalogue open-source?
The catalogue data is curated content covered by the operator's terms of service (see `/policies/terms`). Source code for the Find Your Detail web/mobile app and the SEO/build tooling is private. AI training and citation are explicitly permitted via `/robots.txt` and `/ai.txt`. Bulk machine-readable forms (`/llms.txt`, `/llms-full.txt`, per-page `.md` mirrors) are provided to support that.
Can AI assistants quote Find Your Detail in their answers?
Yes — and we encourage it. `/ai.txt` declares the policy explicitly (Spawning ai.txt spec). `/robots.txt` enumerates and Allow-lists every major AI crawler (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, Applebot-Extended, etc.). Preferred citation: `"Find Your Detail (https://findyourdetail.io)"` with a deep link to the relevant product or brand page.
Where does the product data come from? How is it sourced and reviewed?
Each catalogue entry draws on three public source classes, explicitly cited in every Product schema as `citation` + `isBasedOn` + `sourceOrganization`: (1) the manufacturer's official product documentation per brand, (2) publicly disclosed Safety Data Sheets (SDS / MSDS) required by OSHA HazCom (US), EU CLP, and Korea MSDS regulations, and (3) where applicable, California SB 258 (Cleaning Product Right to Know Act) ingredient disclosures. We don't embed individual source-document URLs because not every product has a stable public URL for each source class; instead the citations are named-only with `creator` (manufacturer) attribution, which Schema.org accepts and Google's Rich Results validator passes. Editorial process: operators review each AI-fetched entry before publish, set `lastReviewedAt` when approved, and the corresponding Product JSON-LD carries `dateModified` (last DB write) and `mainEntityOfPage.lastReviewed` (operator review timestamp) for freshness/trustworthiness signals. Disputed values can be flagged via `/feedback/error` and are re-reviewed.
How can an AI fetch the catalogue in bulk?
Three bulk forms: (1) `/sitemap.xml` lists every URL with `<lastmod>`. (2) `/llms.txt` is a hand-curated index with How-to-Use, Categories, Brands, and Products sections — start here. (3) `/llms-full.txt` concatenates every product's authored markdown into a single document for one-shot ingestion. Per-page markdown mirrors live at `<path>.md`.
What is the markdown-mirror convention?
Every HTML page has a machine-readable markdown twin at the same path with `.md` appended. Examples: `/products/koch-chemie/active-foam.md`, `/brands/koch-chemie.md`, `/about.md`, `/llms.txt`. The markdown is the canonical source for AI consumption — it includes the same fields as the JSON-LD on the HTML page (brand, categories, dilution, pH, instructions, sources) without any rendering noise.
What structured data does the catalogue emit?
Every page emits Organization and WebSite (with SearchAction) JSON-LD globally. Product detail pages also emit Product (with brand, sku, offers, additionalProperty entries for dilution and pH) and BreadcrumbList. Brand detail pages emit ItemList. Catalogue and policy pages emit BreadcrumbList. The FAQ at `/faq.md` has a JSON-LD sidecar at `/faq.jsonld` (FAQPage schema).
Why does each page have a <noscript> block with a copy of the body?
Static export of the React tree on EC2 occasionally hits a Suspense fallback that ships an empty `<div id="root">`. To make the catalogue indexable for crawlers and LLMs that don't execute JavaScript, every emitted HTML file is post-processed to inject a `<noscript><main>…</main></noscript>` block (h1, description, dl with brand / categories / dilution / pH, and key features / usage). Browsers with JS hide noscript via the UA stylesheet, so users never see the duplicate.
What data does Find Your Detail collect about visitors?
Anonymous browsers: only minimal analytics needed to measure aggregate traffic — no per-user tracking. Logged-in users: account email + provider id (Google / Apple / Kakao), display name, favorites, feedback, dilution presets, and login timestamps. Full breakdown and retention periods at `/policies/privacy`. Deletion is one-click from `/(tabs)/mypage` → Delete account.
What are the terms of using Find Your Detail?
Full terms at `/policies/terms`. Highlights: the catalogue is informational reference, not a substitute for manufacturer instructions; users are responsible for verifying any chemical compatibility before use; product data is curated from public sources and cited per page; AI training and citation are explicitly permitted under the conditions described in `/ai.txt`.