Source checks

Source checks are live

Source work does not become article copy by default. It becomes a reviewed inventory: official pages are highlighted, secondary pages are rewritten carefully, and unclear records stay out of traveler guidance.

Source records

409

reviewed source inventory

Unique URLs

396

deduped before page-level review

Official sources

5

city tourism or scenic-site pages

Source owners

13

usable records after review

Resource kits

Pages that outside teams can cite without hiding the boundary

These packs are for maintained pages: university pre-departure notes, conference visitor pages, hotel arrival messages, DMC itineraries, and editorial resource lists. Each one links to a practical next action while keeping live rules with the official source.

University pre-departure teams

Student arrival readiness pack

Use this when a program office needs a compact China setup layer for students before the flight: phone data, payment, school or dorm address, first transfer, and support fallback.

Best placement: Pre-departure email, student handbook, orientation LMS, or travel-risk page

Boundary: Program-specific arrival instructions, campus check-in, visa documents, health rules, and emergency contacts remain with the school and official sources.

Conference and trade-show organizers

Visitor first-night and payment pack

Use this when attendees need to land, reach the hotel, pay for food or transport, and keep the first event day from being blocked by phone or wallet setup.

Best placement: Attendee travel page, badge-confirmation email, exhibitor manual, or hotel block page

Boundary: Badge rules, venue access, shuttle schedules, hotel blocks, invitation letters, and event support desks remain with the organizer.

Hotels, DMCs, and local operators

Arrival recovery reference pack

Use this when a guest or client arrives with a broken payment, data, ride-hailing, ticket, address, or language layer and needs the next safe move.

Best placement: Guest pre-arrival message, concierge note, arrival FAQ, or private itinerary PDF

Boundary: Live prices, pickup zones, hotel policies, driver terms, ticket windows, and emergency procedures remain with the operator and official channels.

Editorial and resource pages

Source-bound answer pack

Use this when a maintained resource page needs concise answers with visible boundaries for payment, eSIM, entry, first transfer, first meal, and support.

Best placement: Resource roundup, forum answer, newsletter, travel safety page, or internal trip note

Boundary: Do not cite a short answer as proof of live app screens, entry rules, fares, prices, hours, or eligibility without checking official or operator sources.

Content quality gate

Old source notes are useful only after they survive a rewrite

The expanded source library now contains more city material, but volume is not the goal. A note can help research; it cannot become public guidance until a person checks the claim, rewrites it for a traveler, and keeps changing details tied to an official or operator source.

Old notes scanned

1,706

kept as research memory, not copied into city pages

Detail records checked

1,047

reviewed before they can support a traveler-facing page

Held for rewrite

644

blocked because the source note is too messy for public guidance

Usable after checks

1,292

facts that can support a rewrite after official source checks

Use after source check

Official facts and reviewed city notes

Use these to support a city guide only after tickets, access rules, transport, and first-night details are checked against official or operator pages.

Rewrite first

Useful clues with weak travel wording

Keep them as leads for what travelers may ask about, then write the answer in plain language with a clear verification boundary.

Hold back

Broken snippets, hotel blurbs, and wrong-market listings

Do not publish these as travel advice or let them enter route discovery until a human review replaces the weak material.

Held-back examples

Hezuo and Mianyang

wrong-market tour listings mixed with broken itinerary fragments

kept out of city expansion discovery until rewritten from cleaner sources

Tangshan and Handan

foreign-language activity snippets that do not match the city decision

held as research memory, not used as public destination copy

Zibo

hotel and platform text mixed into attraction notes

blocked from traveler guidance until official and local source checks replace it

Link suggestions

Natural sentences for maintained resource pages

These examples are for editors, program offices, event teams, and community replies that already discuss the same China arrival problem. Use one only when it helps the reader make the next practical decision.

Link use

How to cite these pages without making the link feel planted

TravelerLocal works best when it helps a reader make the next safe move, while the final rule, booking, fare, or app behavior stays with the official source.

Link to the reader's next decision

Use one page when it helps a traveler decide what to do next: set up the phone, recover a payment, choose the first transfer, or slow down a route.

Keep the boundary visible

Do not use TravelerLocal as proof of live rules, prices, app limits, schedules, or eligibility. Link it as a practical setup aid, then keep official or operator checks close by.

Avoid forced anchor text

Natural text is better than search-keyword phrasing. A sentence like 'this checklist may help with the China app setup order' is usually enough.

Answer first in communities

In forum replies, solve the person's question in plain language before adding a link. If the link is not necessary, leave it out.

Editorial check

A useful source page should feel written for a person

Source coverage is only useful when it becomes plain travel guidance. These checks keep resource links specific, careful, and readable outside TravelerLocal.

Does the page answer a real travel decision before linking away?

Does the copy say what can change and where the traveler should verify it?

Would the link still be useful if the reader skipped the rest of the site?

Is the wording natural enough for a forum reply, student packet, or trip note?

Attractions

144

Attraction source records for city pages, especially Yunnan, Sichuan, Xinjiang, and scenic-site expansion.

143 low-risk records, 143 rewrite records

City Overviews

143

City overview records that help decide which destinations deserve first-pass pages.

143 low-risk records, 143 rewrite records

Festivals

69

Festival and public-holiday context that can improve seasonality notes after rewrite.

23 low-risk records, 60 rewrite records

Practical

32

Practical travel background for culture, weather, safety, and visitor expectations.

28 low-risk records, 32 rewrite records

General Travel

21

General travel context used only after source and copyright review.

18 low-risk records, 19 rewrite records

Use guardrails

Source checks improve coverage without importing bad prose

Records with usable facts move into planning notes. Anything quoted, broken, duplicated, or medium-risk stays as a research pointer until it is rewritten.

Official city, attraction, transport, entry, payment, and operator pages can support live travel claims.
Wikipedia and Wikivoyage-style references are useful for orientation but must be rewritten and attributed where needed.
Guidebook, media, and operator pages are facts-only or inspiration sources; TravelerLocal does not copy their prose.
Broken or unclear source records stay out of traveler-facing guidance until a cleaner source is found.

Claim boundaries

Match the source to the kind of travel claim

Some sources can anchor live travel decisions. Others are useful only after a rewrite, as background context, or as a prompt to find a cleaner official page.

Live prices, fares, reservations, and opening rules

Use TravelerLocal for setup order and risk framing, then verify the final price, schedule, and reservation rule with the official operator.

Use: Official attraction, transport, airport, rail, payment, and city-service pages checked close to publication.

Avoid: Community guides, commercial tour pages, copied snippets, or older research notes without a live operator link.

Payment, eSIM, app setup, and device compatibility

Treat setup pages as a checklist; test a small payment, data connection, or login before relying on it for arrival day.

Use: Official wallet help, carrier/device documentation, and operator support pages that describe the current setup path.

Avoid: Forum reports, product marketing pages, and generic app roundups when the claim depends on country, card, device, or account state.

City route shape, first-night planning, and itinerary pacing

Use city pages to choose a calmer route shape, not as proof that a venue is open or a ticket is available.

Use: Official tourism or transport context plus rewritten traveler notes that explain arrival friction, first meal confidence, and recovery options.

Avoid: Unfiltered attraction lists, hotel-heavy results, package tours, and generic things-to-do copy.

Safety, health, emergency, and visitor support

Keep official emergency, consular, and operator contacts available offline before departure.

Use: Official government, health, airport, transport, and consular pages with visible source dates or stable service contacts.

Avoid: Anecdotes, social posts, and travel blogs when the answer could affect medicine, emergencies, policing, entry, or personal safety.

Background culture, food rhythm, and destination feel

Use background context to reduce surprise, then keep live plans flexible.

Use: Rewritten secondary references and city observations that help explain what a traveler should expect.

Avoid: Copied guide prose or exact restaurant, price, and schedule claims unless a current official or operator page backs them.

Next move

Leave each page knowing what to do next.

Read enough to make the decision smaller, then open the checklist, search a specific question, choose a setup tool, or share the page with the person planning with you.

Official sources for rules, fares, payments, safety, and device setup.
Written around the day-one jobs: pay, connect, move, eat, get help.
Recommendations stay attached to a traveler task.

I need the next step

Use the checklist when the question has shifted from research to preparation.

Open checklist

I know the problem

Search by the actual problem: Alipay, eSIM, transit visa, first transfer, vegetarian food, or a city name.

Search the site

I am ready to choose

Open recommendations when the task is clear enough for a short list to be useful.

See recommendations