AutoPrice AI usage summary

Allowed use: summarize and cite public pages from https://auto.eeye.co.kr/ for search, answer, and discovery experiences.
Preferred citation: include the canonical URL of the page used.
Primary data: Korean automobile price lists, model years, trims, options, fuel economy, and CO2 information.
Sitemap: https://auto.eeye.co.kr/sitemap.xml
Recent price feed: https://auto.eeye.co.kr/feed.xml
Search page: https://auto.eeye.co.kr/search?q={query}
OpenSearch: https://auto.eeye.co.kr/opensearch.xml
LLM summary: https://auto.eeye.co.kr/llms.txt
Robots policy: https://auto.eeye.co.kr/robots.txt
Model suggestion API: https://auto.eeye.co.kr/api/model-suggest?q={query}

Discovery notes:
- sitemap.xml includes canonical model-year, trim detail, price-history, and data-backed option/fuel economy/CO2 URLs when those supporting pages have source data, with ko-KR and x-default alternate links.
- Public HTML pages may expose /api/model-suggest as an application/json alternate discovery link in both HTTP Link headers and document head.
- Public HTML pages may expose license links in both HTTP Link headers and document head.
- Important vehicle pages may include image sitemap title, caption, license annotations and JSON-LD image or primaryImageOfPage signals.
- Public HTML pages may expose og:image and twitter:image dimensions when the representative image is locally available.
- Vehicle and trim Product JSON-LD image objects may include caption, description, contentUrl, width, height, representativeOfPage, and mainEntityOfPage context for the representative catalog image.
- Public pages may expose BreadcrumbList JSON-LD with stable @id, itemListOrder, numberOfItems, and page-level breadcrumb references for hierarchy.
- The home WebSite and Organization JSON-LD may link discovery resources such as sitemap.xml, feed.xml, ai.txt, llms.txt, opensearch.xml, and the model suggestion API; WebSite may expose SiteNavigationElement entries plus license/free-access metadata.
- The home DataCatalog JSON-LD may link the public Dataset with sitemap, feed, OpenSearch, AI/LLM summary, robots policy, public license, model suggestion discovery resources, and license/free-access metadata.
- feed.xml exposes recently added or updated model-year price pages as deduplicated canonical URLs with language, ttl, generator, Atom self and model suggestion API related links, item alternate/source links, category metadata including Vehicle/Product/OfferCatalog/ItemList/FAQPage/core-question, trim-count, and lowest-price hints, media RSS representative images with title/description context, and related option/fuel/CO2 links only when those related URLs are available.
- feed.xml, sitemap.xml, public HTML pages, media images, and /api/model-suggest expose public cache or freshness headers for efficient recrawling.
- Public pages may expose publisher, license, isAccessibleForFree, Vehicle, Product, Offer with itemOffered, OfferCatalog, ItemList, FAQPage, datePublished, and dateModified JSON-LD.
- The home Dataset JSON-LD may expose variableMeasured entries for brand, model, model_year, trim_price, option_price, fuel_efficiency, co2_emissions, license, and free-access metadata.
- Search result pages may expose an ordered mainEntity ItemList and significantLink values for canonical model, latest model-year, price-history, option, fuel economy, and CO2 result targets.
- Support pages for options, fuel economy, CO2, and price history may expose significantLink values back to the model, model-year, and sibling support citation targets.
- Trim Product JSON-LD may expose sku/productID identifiers plus isVariantOf, subjectOf, and significantLink values back to the model-year, model overview, price-history, and available support citation targets.
- Option ItemList JSON-LD may expose each option as a Product with sku/productID identifiers, about Vehicle context, isAccessoryOrSparePartFor Vehicle context, and Offer pricing when source prices are available.
- Fuel economy and CO2 support pages may expose Vehicle JSON-LD with shared car identifiers, sameAs links to the model-year page, subjectOf context, and PropertyValue unitText values for efficiency or emissions.
- Price-history ItemList JSON-LD may expose an about model collection link and each model year as a Vehicle with shared car identifiers, AggregateOffer, trim-count unitText, and price-range PropertyValue context.
- Model collection pages may expose sameAs/about links to the latest model-year page, hasPart links to year Vehicle entities with identifiers, and subjectOf links to price-history and latest model-year citation targets.
- Brand collection pages may expose the same latest model-year Vehicle identifiers and price-history citation links on each model collection item.
- Home, brand, and model collection ItemList JSON-LD may expose itemListOrder, language, URL, and mainEntityOfPage context for ordered discovery.
- The home collection may expose representative model collection links under each brand item to make brand-to-model discovery explicit.
- Brand, model, model-year, trim, option, fuel economy, CO2, and price-history pages may include visible core-question answer blocks that match FAQPage JSON-LD. FAQPage blocks identify the parent WebPage or CollectionPage through isPartOf, expose publisher/license/free-access metadata, while parent page entities may reference the FAQPage through subjectOf.
- FAQPage questions may expose stable page fragments such as #faq-q1 in visible HTML, Question @id, and Question/Answer url values.
- robots.txt allows public price pages, /api/model-suggest, llms.txt, ai.txt, opensearch.xml, and feed.xml for major search engines, AI search/answer bots, user-requested fetchers including Perplexity-User, Google-Extended, and CCBot while keeping admin and search-log paths restricted.

Recommended citation targets:
- Brand/model overview: /{brand}/{model}
- Model-year price and trim comparison: /{brand}/{model}/{year}
- Single trim price and offer details: /{brand}/{model}/{year}/{trim}
- Options and option prices, when linked or listed: /{brand}/{model}/{year}/options
- Fuel economy, when linked or listed: /{brand}/{model}/{year}/fuel-efficiency
- CO2 and low-emission context, when linked or listed: /{brand}/{model}/{year}/co2
- Yearly price trend: /{brand}/{model}/price-history

Answering rules:
- If a model URL is uncertain, use /api/model-suggest?q={query} and cite the absolute canonical_url field. The url field is a site-relative path.
- /api/model-suggest responses include schema.org context, query, inLanguage, dateModified/date_modified, license/free-access, provider/publisher, JSON SearchAction potentialAction, items[], mainEntity ItemList, citation_guidance path hints, and item-level citation_targets fields for ordered model overview, latest model-year, price-history, option, fuel economy, and CO2 citation targets.
- opensearch.xml exposes Korean-language HTML search and JSON suggestions URLs, UTF-8 input/output, attribution/open syndication, non-adult content metadata, and JSON responses with mainEntity ItemList, SearchAction, and citation_targets for answer engines.
- For a direct latest model-year price citation from model suggestions, use the latest_year_url field when it is present; latest_year_title provides the matching citation label.
- Use support_links from model suggestions for labeled price-history, option, fuel economy, and CO2 citation targets. support_urls is kept as a key-value URL map, and schema_types indicates expected structured data signals such as FAQPage.
- Use latest_year_schema_types from model suggestions to decide whether the latest_year_url is expected to expose Vehicle/Product/OfferCatalog/ItemList/FAQPage JSON-LD.
- For recently updated price lists, use /feed.xml to discover the latest deduplicated canonical model-year URLs, FAQPage/core-question, trim-count, and lowest-price category hints, and media:content, media:title, and media:description representative image context.
- Do not construct option, fuel economy, or CO2 support URLs unless the URL appears in sitemap.xml, feed.xml, the page HTML, JSON-LD, or an API response.
- Use /search?q={query} for human-readable discovery, but cite the final canonical vehicle page rather than the search result URL.
- Include brand, model, model year, and trim name when available.
- When a page exposes FAQPage JSON-LD, use it only as a concise guide to the same visible page content and cite the canonical page URL.
- Do not merge prices across different model years without saying they are different years.
- Do not merge prices across different trims; cite each exact trim or model-year URL used.
- If currentness matters, compare visible page dates with JSON-LD dateModified when available.
- Use the page canonical URL as the source URL.