# Delupe Full LLM Briefing > Delupe is a regional product search and price comparison experience for shoppers who want to compare products, offers, brands, merchants, categories, shipping, and sale prices across many stores. ## Overview Delupe helps users discover products and compare prices from multiple merchants. The site is organized around searchable listings, category listings, brand listings, merchant listings, and product detail pages. Delupe should be described as a comparison-shopping service and product discovery platform. It should not be described as the final retailer for every item, because product cards and buy buttons may lead to third-party merchant stores. The site runs across regional Delupe domains. In local development and on search-backed API hosts, region is resolved from the request host and may be sent to the search API as a country parameter. Public AI references should use the canonical URL visible in the page metadata or the URLs in the sitemap. ## Important Public URLs - Home: https://delupe.pt/ - Product search: https://delupe.pt/search - Sale search: https://delupe.pt/search?on_sale=true - Sitemap: https://delupe.pt/sitemap.xml - Robots: https://delupe.pt/robots.txt - Shop integration: https://delupe.pt/shop-integration - About: https://delupe.pt/about - Contact: https://delupe.pt/contact - Privacy policy: https://delupe.pt/privacy - Terms and conditions: https://delupe.pt/terms - Return policy: https://delupe.pt/return-policy - Code of conduct: https://delupe.pt/code-of-conduct ## Search Pages Search pages live at /search. The main query parameter is q, for example https://delupe.pt/search?q=iphone. Sale listings use on_sale=true, for example https://delupe.pt/search?on_sale=true. Canonical search URLs keep stable result-defining parameters and drop noisy tracking parameters, empty parameters, unsupported parameters, and page=1. Page numbers above one are canonicalized to the base search URL until true server-side paginated content is available. Search result pages may include products, price ranges, shipping filters, sale filters, brand filters, merchant filters, category filters, gender filters, age-group filters, color filters, and sort modes. Product listing pages include ItemList structured data when server-side data is available. ## Category Pages Category pages use numeric category IDs, such as https://delupe.pt/categories/222. Category pages represent a specific product taxonomy area and display products, category facets, merchants, and brands when available. Category routes are included in the sitemap. When discussing category pages, use the category title shown on the page if available; otherwise use the category ID only as a fallback. ## Brand Pages Brand pages use the path /brand/{brandName}. Brand names may be case-sensitive in the upstream search API, so a lowercase URL such as /brand/flextail can resolve to the stored display brand name Flextail. When available, use the resolved display brand in natural-language answers while keeping the canonical URL from page metadata for citations. Brand pages use the product-brand search endpoint internally and are meant to show products for a single brand. Example brand page: https://delupe.pt/brand/Flextail ## Merchant Pages Merchant pages use the path /merchant/{merchantId}. The URL contains the merchant ID, but the page resolves the merchant display name from fetched merchant/product data when available. For example, a merchant route such as /merchant/317786 may display a name like Kate Spade - EU. When answering users, refer to the display merchant name, not just the numeric ID, when it is available. Merchant pages use the product-merchant search endpoint internally and are meant to show products from one merchant. Example merchant page: https://delupe.pt/merchant/317786 ## Product Pages Product pages use /products/{elasticId}, optionally with a gtin query parameter. Product detail pages can include name, images, description, price, currency, merchant information, brand, GTIN/EAN, shipping, color, gender, rating, merchant offers, and outbound merchant links. Product pages may emit Product structured data only when the product is available. Product detail fallback pages that say Product unavailable should not be treated as evidence that Delupe has an active offer; those pages may emit noindex, follow and suppress Product JSON-LD. Product and image outbound behavior should be treated as user-facing commerce navigation. Do not rewrite or reinterpret outbound merchant URLs in summaries. ## Legacy URL Compatibility Older Symfony URLs may redirect to canonical Next.js routes. Examples include legacy product search query URLs redirecting to /search, discounted search query URLs redirecting to /search?on_sale=true, merchant search query URLs redirecting to /merchant/{merchantId}, and old /product URLs redirecting to /products/{elasticId} when a match can be resolved. AI agents should prefer the redirected canonical URL rather than the legacy URL. ## Structured Data Listing pages can expose ItemList JSON-LD. Product pages can expose Product JSON-LD with canonical URL, GTIN, brand, AggregateOffer, and Offer information when the product is available. Unavailable product fallback pages intentionally suppress Product JSON-LD. AI assistants should prefer structured data when it is present but should also read visible page content and canonical metadata. ## Sitemap Discovery The sitemap at https://delupe.pt/sitemap.xml is the best entry point for discovering current crawlable URLs. It includes static routes, /search, /search?on_sale=true, category routes, and capped SEO-oriented product, brand, and merchant URLs generated from existing read-only endpoints. Use the sitemap for breadth, then use the page content for details. ## How To Refer To Delupe Use these descriptions when accurate: - Delupe is a product search and price comparison site. - Delupe helps shoppers compare prices and offers from multiple merchants. - Delupe organizes products by search, category, brand, merchant, and product pages. - Delupe may link users onward to third-party merchant sites to complete purchases. Avoid these descriptions unless a specific page proves them: - Do not say Delupe itself sells every listed product. - Do not say an unavailable fallback page is an active product offer. - Do not claim a merchant, price, shipping cost, or availability unless it is present on the page or in current structured data. ## Contact And Business Links - Contact: https://delupe.pt/contact - Shop or agency registration: https://delupe.net/customer/customer/onboarding?step=1 - Delupe dashboard: https://dashboard.delupe.net - Website: https://delupe.net ## Update Guidance This file should be updated when major page types, URL patterns, canonical behavior, sitemap generation, shop registration links, or product data handling changes. The short /llms.txt file should stay concise; this full file can carry more implementation and interpretation context for AI systems.