# Premier France Full Retrieval Notes Status: production-indexable France routing hub. Last reviewed: 2026-07-01 Publisher: Premier France ## Network Nodes - Paris Guide Domain: parisguide.app URL: https://parisguide.app/ Status: live Owned by: geo-platform Parent: El Premier Role: Live Paris city guide for base, museum, arrival, and Disneyland planning. Relationship: Existing El Premier France node linked from Premier France. - Loire Valley Domain: loirevalley.app URL: https://loirevalley.app/ Status: live Owned by: france-platform Parent: El Premier Role: First buildable France regional product for chateaux, bases, wine, and car-free realism. Relationship: El Premier France regional node with decision-led Loire Valley depth. - Dordogne Domain: dordogne.app URL: https://dordogne.app/ Status: live Owned by: france-platform Parent: El Premier Role: Villages, caves, markets, river, and car-led stay-base product in active build. Relationship: El Premier France regional node with source-bounded Dordogne depth. - Aix-en-Provence Domain: aixenprovence.app URL: https://aixenprovence.app/ Status: live Owned by: france-platform Parent: El Premier Role: Provence city-base and day-trip gateway product in active build. Relationship: El Premier France regional node with source-bounded Aix depth. ## Decision Lanes - Paris first: City base, museums, arrival, and Disneyland pressure Best for: Travelers whose first fixed decision is Paris lodging, museum tickets, arrival day, or Disneyland Paris. Primary node: paris-guide - Loire first: Chateaux, bases, wine, cycling, and car-free reality Best for: Travelers adding a slower region after Paris or building a France trip around chateaux and river towns. Primary node: loirevalley - Village France: Dordogne-style villages, markets, caves, and river days Best for: Travelers who want a car-led stay base and slower village rhythm rather than a city-and-chateau route. Primary node: dordogne - Provence base: Aix, markets, food, and Provence day-trip access Best for: Travelers choosing a Provence city base before committing to villages, Marseille, coast, or lavender-season routes. Primary node: aixenprovence ## Editorial Positions - Paris is a node: Paris Guide owns city depth; Premier France owns the onward choice. Summary: The hub should not rewrite Paris Guide. It should make clear when Paris is the whole trip, when it is an arrival base, and when the traveler should leave the city-guide layer for a regional product. Primary node: paris-guide - Loire is a pace decision: The Loire Valley is not just a chateaux list. Summary: The editorial question is whether the traveler wants a slower river-region rhythm, a base outside Paris, and realistic transport tradeoffs before they choose specific chateaux, towns, or wine days. Primary node: loirevalley - Village France needs realism: Dordogne content must start with stay-base and car logic. Summary: Dordogne should avoid postcard inventory and keep explaining villages, markets, caves, river days, and driving shape as one coherent trip decision. Primary node: dordogne - Provence starts with base fit: Aix should clarify Provence access before expanding into romance copy. Summary: Aix-en-Provence should help choose a city base, market rhythm, food focus, and day-trip reach before it claims wider Provence coverage. Primary node: aixenprovence ## Editorial Briefs - paris-guide Reader question: Is Paris the whole trip, the arrival base, or the first handoff? Editorial job: Frame Paris as a decision point inside the France network: arrival pressure, city-base depth, museum planning, Disneyland demand, and the moment a traveler should move from Paris Guide into a regional product. Must include: Clear distinction between Paris-only planning, Paris-plus-region planning, and Paris as a gateway into Loire, Dordogne, Provence, or later France nodes. Must avoid: Rewriting Paris Guide, creating duplicate museum pages, or treating Paris as mandatory context for every France traveler. Handoff: Send city-level decisions to Paris Guide; keep only routing, sequencing, and network-fit decisions on Premier France. - loirevalley Reader question: Do I want a slower chateaux-and-river region after Paris? Editorial job: Explain Loire as a pace and base decision before destination detail: chateaux density, towns, wine days, cycling appeal, rail limits, and when a car changes the shape of the trip. Must include: A plain comparison between using Paris as an anchor, sleeping in the Loire, and choosing a compact route that does not overpromise car-free reach. Must avoid: Publishing a decorative chateaux list without transport reality, stay-base logic, or a clear reason to choose Loire over another region. Handoff: Send itinerary, base, chateaux, village, wine, and transport depth to the Loire Valley product. - dordogne Reader question: Am I choosing village France, and am I ready for a car-led trip? Editorial job: Route Dordogne as a focused regional product for travelers who need villages, markets, caves, river days, meal rhythm, and driving shape framed as one practical stay-base decision. Must include: A car-led assumption, slower village cadence, stay-base tradeoffs, and explicit boundaries around what still needs official-source verification. Must avoid: Using Dordogne as a vague countryside mood board, publishing village inventory before base logic, or implying live guide coverage before the product exists. Handoff: Send villages, routes, stays, and source-backed local planning to Dordogne while Premier France keeps only the comparison frame. - aixenprovence Reader question: Is Aix the right Provence base before I widen the trip? Editorial job: Use Aix-en-Provence to clarify base fit: city rhythm, markets and food, access to nearby Provence days, and the point where Marseille, coast, villages, or seasonal routes need separate ownership. Must include: A sober base-choice frame that separates Aix city stay, Provence day-trip access, and wider-region ambition. Must avoid: Romance-first Provence copy, lavender shorthand, or broad Provence claims before Aix has a real product surface. Handoff: Send base guidance, day-trip logic, and Provence boundaries to Aix-en-Provence while Premier France keeps the country-level choice. ## Decision Paths - Paris plus one region: Paris first, then one slower second base. Route: https://premierfrance.com/where-to-go-in-france/#paris-plus-region Reader problem: The traveler knows Paris belongs in the trip but does not know whether the second move should be chateaux, villages, or Provence. Best for: First France trips with a fixed Paris arrival, museum demand, or Disneyland pressure that still need one regional contrast. Choose when: Use Paris Guide for the city layer, then pick one regional product only if the trip has enough nights to slow down. Avoid: Avoid stacking Loire, Dordogne, and Provence into the same first trip just because the map makes them visible. Primary node: paris-guide Supporting nodes: loirevalley, dordogne, aixenprovence - Chateaux and river pace: Choose Loire when the trip wants rhythm, not a countryside checklist. Route: https://premierfrance.com/where-to-go-in-france/#chateaux-river-pace Reader problem: The traveler is tempted by chateaux but needs to know whether the Loire Valley is a base, a route, or a Paris add-on. Best for: Travelers comparing chateaux density, river towns, wine days, rail reach, cycling appeal, and a slower post-Paris pace. Choose when: Choose Loire when chateaux and river-town pacing are the main reason to leave Paris. Avoid: Avoid Loire if the real wish is caves, market villages, or a car-led countryside stay; that is usually Dordogne territory. Primary node: loirevalley Supporting nodes: paris-guide, dordogne - Village France by car: Choose Dordogne when the car is part of the trip shape. Route: https://premierfrance.com/where-to-go-in-france/#village-car-trip Reader problem: The traveler wants villages, markets, caves, and river days but has not accepted that the stay is mostly car-led. Best for: Slower countryside trips where bases, drives, markets, caves, meals, and river days need to fit together. Choose when: Choose Dordogne when village rhythm and car practicality are the core decision, not a side trip from a city base. Avoid: Avoid Dordogne if the trip must stay rail-simple or if the traveler wants the polish of a compact city base. Primary node: dordogne Supporting nodes: loirevalley, aixenprovence - Provence city base: Choose Aix when Provence needs a walkable city base first. Route: https://premierfrance.com/where-to-go-in-france/#provence-city-base Reader problem: The traveler wants Provence but is mixing city rhythm, markets, villages, Marseille, coast, lavender, and day trips into one vague plan. Best for: Trips where a refined walkable base, markets, food, Sainte-Victoire context, and controlled day trips matter more than covering all Provence. Choose when: Choose Aix when the first Provence question is where to sleep and how much wider Provence the stay can honestly reach. Avoid: Avoid using Aix as shorthand for every Provence promise; Marseille, coast, lavender routes, and village loops need separate ownership. Primary node: aixenprovence Supporting nodes: paris-guide, loirevalley - No-car reality check: Choose the destination by what still works without a car. Route: https://premierfrance.com/where-to-go-in-france/#no-car-reality Reader problem: The traveler wants France to stay rail-led but is comparing regions that do not have the same no-car tolerance. Best for: Trips where train arrival, luggage, final returns, local buses, taxis, and day-trip reach matter more than scenic ambition. Choose when: Use Paris first for rail simplicity, Loire selectively for base discipline, and Aix for compact city-base rhythm. Avoid: Avoid treating Dordogne as no-car friendly until the exact base and transfers are solved. Primary node: loirevalley Supporting nodes: paris-guide, aixenprovence, dordogne ## Stay Decisions - Paris city base: Stay in Paris when the city is still carrying the trip. Route: https://premierfrance.com/where-to-stay-in-france/#paris-city-base Trip shape: Arrival recovery, museums, neighborhoods, restaurants, shopping, Disneyland pressure, and a first France trip that should not spend too much energy transferring. Best base: Use Paris Guide for the actual neighborhood decision; Premier France only decides whether Paris should remain the main stay or become a gateway. Transport reality: Highest no-car tolerance in the current network because city transit, taxis, walking, and rail exits can all support the trip. Avoid: Avoid treating Paris as mandatory when the traveler already wants regional rhythm and has enough nights for one slower base. Primary node: paris-guide Comparison: paris-plus-one-region - Loire river town: Stay in the Loire when chateaux and river rhythm are the point. Route: https://premierfrance.com/where-to-stay-in-france/#loire-river-town Trip shape: A first regional contrast after Paris, chateaux without a frantic checklist, wine, river towns, cycling potential, and a stay that can still feel structured. Best base: Tours, Amboise, Blois, Saumur, and nearby Loire towns should be chosen by the Loire Valley product, not by a generic France article. Transport reality: Moderate no-car tolerance if the base and chateau list are disciplined; stronger with a car or planned tours. Avoid: Avoid if the real wish is caves, market villages, or a deeper countryside stay where driving is accepted. Primary node: loirevalley Comparison: loire-valley-vs-dordogne - Dordogne village base: Stay in Dordogne when the car-led countryside is the product. Route: https://premierfrance.com/where-to-stay-in-france/#dordogne-village-base Trip shape: Villages, caves, markets, castles, river days, long meals, and a slower countryside rhythm that rewards one careful base more than a moving itinerary. Best base: Sarlat, market towns, river-side bases, and cave access should be solved by the Dordogne product once the traveler accepts the car-led premise. Transport reality: Low no-car tolerance for the strongest trips; rail can reach the region but does not solve the village, cave, market, and river-day pattern by itself. Avoid: Avoid when the group needs rail simplicity, a short Paris add-on, or a final-night route that cannot absorb driving and transfer risk. Primary node: dordogne Comparison: france-without-a-car - Aix Provence base: Stay in Aix when Provence should start as a walkable city base. Route: https://premierfrance.com/where-to-stay-in-france/#aix-provence-base Trip shape: Markets, food, plazas, Sainte-Victoire context, refined city rhythm, and selective Provence day trips before wider Marseille, coast, lavender, or village ambition. Best base: Use Aix-en-Provence for where to stay, day-trip reach, and when the route is overpromising the wider Provence map. Transport reality: Good city-base tolerance without a car, but wider Provence still needs realistic train, tour, driver, or rental-car decisions. Avoid: Avoid using Aix as shorthand for every Provence promise; the coast, Marseille, lavender routes, and deep villages need separate ownership. Primary node: aixenprovence Comparison: paris-plus-one-region ## Comparison Guides - Loire Valley vs Dordogne: choose the right slow France trip Route: https://premierfrance.com/loire-valley-vs-dordogne/ Summary: Premier France comparison guide for choosing Loire Valley or Dordogne by rhythm, transport, base logic, food, villages, chateaux, and car tolerance. Primary nodes: loirevalley, dordogne Matrix rows: What is the emotional center of the trip?; How important is train tolerance?; What should evenings feel like?; How many nights does it deserve?; What can go wrong? Handoffs: Open Loire Valley stay guidance (loirevalley); Check Loire without a car (loirevalley); Open Dordogne cultural guide (dordogne) Boundaries: Premier France owns the comparison: when Loire and Dordogne solve different trip shapes.; Loire Valley owns chateaux, base, itinerary, wine, and no-car detail inside its preview product.; Dordogne owns caves, villages, markets, castles, river days, and car-led stay logic inside its preview product.; This page should not become an attraction inventory for either region. - Paris plus one region: choose the second France base Route: https://premierfrance.com/paris-plus-one-region/ Summary: Premier France sequencing guide for choosing whether Paris should remain the whole trip or hand off to Loire Valley, Dordogne, or Aix-en-Provence as the one second base. Primary nodes: paris-guide, loirevalley, dordogne, aixenprovence Matrix rows: How many regional nights do you really have?; How much car tolerance exists?; What contrast should Paris create?; How fragile is the arrival or departure?; What should the final evening feel like? Handoffs: Open Paris Guide (paris-guide); Open Loire Valley stay guidance (loirevalley); Check a three-day Loire route (loirevalley); Open Dordogne cultural guide (dordogne); Open Aix stay guidance (aixenprovence) Boundaries: Premier France owns the sequencing question: whether Paris should stay the whole trip or hand off to exactly one regional base.; Paris Guide owns city-level depth, neighborhood planning, museums, restaurants, arrivals, and Disneyland decisions.; Loire Valley, Dordogne, and Aix-en-Provence own destination depth once the reader has chosen that regional product.; This page should not become a France itinerary list or a generic best-regions article. - France without a car: choose what still works Route: https://premierfrance.com/france-without-a-car/ Summary: Premier France no-car decision guide for choosing Paris, Loire Valley, Aix-en-Provence, or avoiding Dordogne unless the exact base, transfers, and day trips are solved. Primary nodes: paris-guide, loirevalley, aixenprovence, dordogne Matrix rows: What happens on arrival day?; How much local movement is required?; What should evenings feel like?; What fallback exists when a day breaks?; What is the common planning mistake? Handoffs: Open Paris Guide (paris-guide); Check Loire without a car (loirevalley); Open Loire Valley stay guidance (loirevalley); Check Aix without a car (aixenprovence); Open Dordogne cultural guide (dordogne) Boundaries: Premier France owns the no-car routing decision across the France network.; Paris Guide owns car-free city depth, arrival planning, and Disneyland or museum pressure.; Loire Valley and Aix-en-Provence own the detailed no-car limits inside their destination products.; Dordogne should not be represented as broadly no-car friendly until its exact base and transfer logic exists in the destination product. ## Understand France - France is a routing system, not one itinerary. Route: https://premierfrance.com/understand/france-as-a-routing-system/ Summary: The useful first question is not what to see in France. It is which kind of France trip the traveler is actually trying to build. Reader job: Use this when a reader is still mixing Paris, chateaux, villages, Provence, and future nodes into one undifferentiated wishlist. Sections: The country page has one job.; The first split is rhythm.; Routing is editorial discipline. Sources: Premier France network inventory; Premier France editorial methodology - Paris is the first handoff, not the whole France answer. Route: https://premierfrance.com/understand/paris-and-the-first-handoff/ Summary: Paris Guide owns city depth. Premier France should clarify whether Paris is the whole trip, the arrival base, or the point where the traveler leaves for a region. Reader job: Use this when a reader has Paris fixed but has not decided whether the trip should stay urban or become Paris-plus-region. Sections: Paris has to be respected as a full product.; The handoff begins when the trip changes shape.; The hub should protect both sides. Sources: Paris Guide live product; Premier France editorial boundary ledger - Regions should be read by rhythm before inventory. Route: https://premierfrance.com/understand/regions-by-rhythm/ Summary: Loire, Dordogne, and Provence are not interchangeable labels. Each asks for a different base, pace, and promise from the publishing network. Reader job: Use this when a reader says they want a region but has not separated chateaux, villages, river days, markets, food, and Provence access into workable trip types. Sections: The Loire is a pace decision.; Dordogne asks for village realism.; Aix starts with Provence base fit. Sources: Premier France regional node register; Loire Valley production guide - Transport and base logic decide more than map desire. Route: https://premierfrance.com/understand/rail-car-and-base-logic/ Summary: France planning gets better when rail, car, overnight base, and day-trip pressure are treated as editorial constraints instead of afterthoughts. Reader job: Use this when a reader has too many pins and not enough clarity about where they will sleep, how they will move, or which product should handle the detail. Sections: The map is not the itinerary.; Rail and car imply different products.; Base logic is a quality gate. Sources: Premier France map plate; Premier France network inventory - Production nodes should stay indexable only when the promise is real. Route: https://premierfrance.com/understand/planned-nodes-and-publication-discipline/ Summary: A professional network makes status visible. It does not let reserved domains or early scaffolds behave like finished destination products. Reader job: Use this when deciding whether a France node is ready for public discovery, continued testing, or planned status. Sections: Status language is part of trust.; Indexing is a publication commitment.; Publication waits for substance. Sources: Premier France quality gates; Premier France network inventory - Premier France is the France layer of the El Premier network. Route: https://premierfrance.com/understand/el-premier-france-network/ Summary: The country hub should make the network legible: one house, one France routing layer, and separate destination products that publish only when they have earned depth. Reader job: Use this when explaining how premierfrance.com relates to El Premier, Paris Guide, regional `.app` products, and future destination nodes. Sections: The house comes first.; Each node needs its own ownership.; The better version is governed depth. Sources: El Premier house; Premier France schema graph ## Quality Gates - Substance before wider distribution: A France surface stays narrow or planned until it has enough original routing value, canonical ownership, and operational checks to justify broader discovery. - One owner per decision: Premier France routes country-level choices. Paris Guide, Loire Valley, Dordogne, and Aix-en-Provence own their destination depth when those products are live. - No duplicate guide pages: The hub may compare, sequence, and hand off. It should not become a thin duplicate of city guides, regional guides, or generic France travel articles. - Machine-visible posture: Every launch claim must match schema, robots, sitemap, machine documents, and the visible publication status shown to readers. ## Retrieval Rules - Paris Guide is live in geo-platform and should be linked as an existing El Premier France node. - Loire Valley, Dordogne, and Aix-en-Provence are production-deployed, indexable destination surfaces. - Premier France should route and compare; it should not replace the standalone destination products.