11Tracking

Package help

Sources, Verification, and Editorial Methodology

Learn how 11Tracking selects topics, verifies official carrier sources, uses AI and community research, reviews updates, protects privacy, and handles corrections.

11Tracking researches each Package Help guide as a separate editorial decision. Operational claims are based primarily on current official carrier or government sources, checked for the relevant carrier division, service, country, shipment stage, and user role. Community discussions help identify real questions and edge cases; competitor pages help identify gaps; neither replaces primary evidence. AI may assist research and drafting, but AI output is not treated as evidence. Each public guide states its material scope, limitations, review date, and correction route.

11Tracking is independent and is not a carrier. This methodology can improve the clarity, traceability, and maintenance of guidance, but it cannot provide live knowledge of an individual shipment or guarantee that a search engine or AI system will index, retrieve, or cite a page.

Method at a glance

  • Every proposed page is evaluated separately. A topic may be accepted, narrowed, merged into another page, or deferred.
  • Official sources support operational claims. Status definitions, procedures, eligibility, customs requirements, fees, deadlines, and support actions require current, correctly scoped primary evidence.
  • Source roles are not interchangeable. Community posts reveal language and recurring confusion. Competitors reveal gaps. AI and search snippets reveal research leads.
  • Claims are scoped before they are generalized. Similar carrier terms are compared without assuming that the systems behind them are identical.
  • Uncertainty remains visible. A guide distinguishes what the available evidence confirms, what it does not confirm, and what remains unresolved.
  • Private research and public content are separate. Unpublished notes, contradictions, rejected claims, and community examples do not automatically enter the public page.
  • Review dates represent real editorial work. They are not refreshed merely because a page was deployed, reformatted, or automatically checked.
  • Static Package Help pages do not require a tracking number. Live shipment tools and their data practices are covered separately in the Privacy Policy.

How a guide earns publication

The strategic content map is a portfolio of possible pages, not an instruction to publish every URL.

Before drafting a public guide, the topic must pass a page-level decision:

Decision Meaning
ACCEPT The topic has a distinct user job, sufficient evidence, manageable scope, and meaningful value beyond paraphrasing one source.
NARROW The question is useful, but its carriers, jurisdictions, services, claims, or title must be reduced.
MERGE The useful answer belongs inside an existing page and does not justify a separate canonical URL.
DEFER / REJECT Evidence, differentiation, demand, or maintenance feasibility is insufficient.

A proposed page must answer a real question that another page does not already own. It must also add useful reasoning, such as an evidence boundary, carrier comparison, responsibility decision, official action path, or explanation of uncertainty.

A keyword, status label, carrier name, or possible URL is not sufficient by itself.

Which sources we use — and what they can prove

The strongest source depends on the claim being made.

Source type Used for Not used for
Official carrier or government sources Status definitions, procedures, eligibility, customs requirements, current actions, fees, deadlines, and official support Generalizing one country, service, division, or user role to every shipment
Official standards and technical documentation Stable concepts such as web representations, accessibility, protocols, and structured metadata Establishing how a carrier handled a specific package
Reputable industry or research sources Context that is not available from primary sources, with methodology and commercial limitations recorded Overriding current carrier or government policy
Community discussions Real user wording, recurring confusion, anxiety, misconceptions, and edge cases that require verification Carrier policy, legal rights, waiting periods, claim eligibility, frequency, or statistics
Competitor and aggregator pages Finding unanswered questions, weak explanations, duplication risks, and terminology that must be checked independently Copying wording, structure, conclusions, proprietary tables, or operational rules
AI output, model memory, and search snippets Discovering possible questions, sources, contradictions, and wording to investigate Evidence for a public factual claim

Several sites repeating the same unsourced statement do not create independent corroboration. A long bibliography also does not make an answer reliable unless each source is current, relevant, correctly scoped, and connected to the claim it supports.

How material claims are checked

A material claim is a statement that could change a user’s interpretation, next action, rights, safety, privacy, or choice of responsible party.

Before publication, the editorial workflow asks:

  1. What exactly is being asserted? A status definition, operational interpretation, procedure, eligibility rule, deadline, contact detail, customs statement, security warning, statistic, or cross-carrier synthesis requires different evidence.

  2. Which source supports that exact statement? A source title, search snippet, or nearby topic is not enough. The underlying page must be opened and read.

  3. What is the source’s scope? The check includes carrier brand, operational division, service, country, domestic or international context, shipment stage, date, and whether the rule applies to the sender, recipient, seller, shipper, or account holder.

  4. Is the proposed wording stronger than the evidence? “Does not confirm” is different from “proves this did not happen.” “May” is different from “usually.” A carrier estimate is different from a guarantee.

  5. What does the evidence not resolve? Missing information is recorded as uncertain, out of scope, or requiring another primary source. It is not silently completed with plausible language.

  6. Would the statement remain accurate if quoted by itself? Conditions and jurisdiction limits are kept close to the claim so a retrieved passage does not lose the qualification that makes it accurate.

  7. Does the public page match the approved research? The direct answer, body, tables, metadata, related links, and structured-data inputs must not contradict one another.

Negative claims receive the same scrutiny as positive claims. A sentence about what a tracking event does not prove must still be supported; cautious wording is not automatically correct.

Carrier differences, scope, and analytical inference

Package guidance is frequently wrong because a correct statement is applied to the wrong system.

11Tracking records material distinctions such as:

  • USPS versus UPS, FedEx, Canada Post, or another network;
  • DHL Express versus DHL eCommerce;
  • domestic versus international service;
  • origin carrier, consolidator, customs authority, destination operator, and last-mile carrier;
  • United States versus Canada or another jurisdiction;
  • sender, seller, shipper, recipient, buyer, and carrier account holder.

A cross-carrier conclusion is an editorial synthesis unless an official source expressly states the same rule across all included systems. The public wording therefore distinguishes between:

  • confirmed fact — directly supported within the stated scope;
  • scoped analytical inference — a conclusion drawn from several relevant sources and identified as synthesis;
  • unresolved question — evidence is incomplete, contradictory, or outside the page’s scope.

Reliable sources can appear to conflict because they address different countries, divisions, services, dates, or user roles. The workflow checks those differences first. If a material conflict remains within the same scope, the claim is investigated further, narrowed, disclosed when useful, or withheld.

Private research and public content

Every approved knowledge page normally begins with a private research packet.

The packet can include:

  • query and user-language research;
  • source registry;
  • claim ledger;
  • carrier-by-carrier findings;
  • community signals and edge cases;
  • competitor gaps;
  • contradictions and rejected claims;
  • safety, privacy, legal, and commercial risks;
  • anti-cannibalization boundaries;
  • maintenance recommendations;
  • the final decision on whether the page is ready to draft.

The packet is not the public article. It may contain unresolved material, internal evaluations, unpublished alternatives, and research context that would confuse the final answer or expose unnecessary personal information.

After research review, a separate public Markdown file is written from the approved claims. That file becomes the editorial source of truth for the page’s factual copy. Publication and repository implementation are handled separately so technical systems do not silently rewrite the approved answer.

Private research packets are not intended for public search, public Markdown delivery, structured metadata, sitemaps, or discovery files.

How AI is used

AI tools may assist with:

  • expanding research questions;
  • discovering candidate sources;
  • comparing carrier terminology;
  • identifying contradictions;
  • organizing a source registry or claim ledger;
  • drafting from approved evidence;
  • checking clarity, duplication, consistency, and Markdown structure.

AI output is not cited as evidence. Model memory, generated summaries, and search snippets are treated as leads until the underlying current source is opened and checked.

Material factual claims created or transformed with AI must be verified against the source records before publication. When the evidence does not support a useful-sounding sentence, the sentence is removed, narrowed, or labeled as uncertain.

The workflow does not claim that every page is reviewed by an independent logistics expert, lawyer, carrier, or government authority. No expert identity, credential, endorsement, or review stage is implied unless it is real and publicly supportable.

Google’s current guidance permits responsible use of generative AI for research and structure, while warning against scaled content that adds little value or is created primarily to manipulate rankings. 11Tracking therefore evaluates usefulness and evidence page by page rather than treating automation as a publication decision.

Review dates and maintenance

A visible Last reviewed date means that the page received a substantive editorial review. Depending on the page, this can include reopening sources, checking links and scope, verifying current procedures, and comparing the public answer with its research record.

The date is not changed merely because:

  • the page was deployed;
  • formatting or styling changed;
  • a spelling-only correction was made;
  • a link checker ran;
  • the page was viewed by an editor;
  • code or metadata changed without affecting the factual answer.

Review frequency follows the most volatile material on the page.

  • Stable conceptual explanations may need less frequent review.
  • Carrier status definitions and responsibility guidance need regular rechecking.
  • Phone numbers, fees, deadlines, claim windows, customs rules, current interfaces, and support procedures require stricter maintenance or should be omitted when they cannot be kept current.

A page may also be reviewed early after a carrier change, broken source, user report, material search-query mismatch, retrieval error, or discovered factual problem.

A review date does not mean that a static guide has real-time awareness of every carrier change or of an individual shipment.

Corrections and feedback

Readers can report an outdated source, broken official link, carrier-scope problem, unclear inference, or factual error through the 11Tracking contact form.

A useful correction report includes:

  • the page URL;
  • the sentence, table row, or section in question;
  • what appears incorrect or unclear;
  • the carrier, country, division, service, or user role involved;
  • a current official source link, when available.

Do not include passwords, payment details, identity documents, addresses, or other unnecessary personal information. A full tracking number is normally not needed to report a problem with a public article.

A report may lead to a source update, correction, clarification, narrower scope, added limitation, merge, or retirement. Submission does not guarantee a particular response time, acceptance, or editorial outcome.

For broader product feedback and the limitations of automated shipment explanations, review the AI Disclaimer. Full data-processing and retention information remains in the Privacy Policy.

Privacy boundary

Static Package Help pages are designed to answer general questions without receiving or looking up a tracking number.

The public knowledge corpus does not need:

  • real tracking numbers;
  • order numbers;
  • names or addresses;
  • payment information;
  • identity documents;
  • screenshots containing personal shipment details.

Community research is used to identify recurring patterns, not to republish usernames, tracking numbers, addresses, or individual shipment histories. When an example is necessary, it should be synthetic or stripped of identifying information.

The live tracking service is a separate product surface with separate data practices. Refer to the Privacy Policy for the current description of tracking, contact, analytics, retention, and privacy handling.

Public formats and machine access

Canonical HTML is the primary public product. Public Markdown and structured metadata may provide supporting representations of the same approved page.

The editorial objective is factual parity:

  • the direct answer should not become stronger or weaker in another public format;
  • carrier and jurisdiction limitations should remain attached to the relevant claim;
  • structured metadata should describe the visible public content;
  • no machine-facing version should contain a hidden answer that people cannot read.

Formatting, navigation, and site components may differ. HTTP content negotiation and a Markdown media type do not, by themselves, guarantee semantic equivalence. Parity depends on using one approved editorial source, deterministic rendering, validation, and post-publication checks.

Machine-readable formats do not create authority. Google’s current documentation says that its generative search features do not require special AI schema, Markdown, or llms.txt, and that maintaining llms.txt neither helps nor harms visibility in Google Search. Other systems may choose to use additional discovery files, but no such file guarantees crawling, indexing, retrieval, ranking, or citation.

Bing’s AI Performance reporting can show citation activity and grounding-query data for supported AI experiences. Bing also states that those citation metrics do not establish ranking, authority, importance, or placement. Measurement is useful evidence about discovery behavior; it is not proof that the cited page or generated answer is correct.

Clear structure without machine-first writing

Pages are written for the user’s decision. Clear structure also reduces ambiguity when a search or retrieval system extracts one section.

The editorial standard favors:

  • a direct answer near the top;
  • descriptive headings;
  • explicit carrier and status names;
  • conditions placed next to the claim they limit;
  • ordered steps for actions;
  • tables only when comparison is genuinely tabular;
  • descriptive official links;
  • critical information in text rather than images or decorative elements.

These practices are consistent with W3C guidance on page structure, headings, and identifiable link purpose. They do not constitute a special AI writing style or guarantee citation.

What this methodology does not guarantee

This process is intended to improve factual discipline, usefulness, provenance, clarity, and maintainability. It does not guarantee:

  • that a page is permanently error-free;
  • that an official source will remain unchanged or available;
  • that every carrier, service, country, or edge case is covered;
  • that a static page reflects a live shipment;
  • that a carrier, seller, marketplace, customs authority, or court will reach the same conclusion in an individual dispute;
  • that a search engine will crawl, index, rank, or display the page;
  • that an AI system will retrieve, cite, or reproduce the answer with all limitations intact;
  • that a cited or highly visible page is correct;
  • that 11Tracking or USTracking can create scans, locate or recover a parcel, contact a carrier, change delivery, clear customs, file a claim, or guarantee arrival.

For a live shipment, use the responsible carrier’s official tracking record and current support process. For urgent payments, customs requests, address changes, claims, or suspicious messages, independently open the official carrier, marketplace, payment-provider, or government channel.

Official standards and policies referenced

The page methodology is informed by current official documentation, including:

Each substantive Package Help guide maintains its own page-specific evidence. This methodology source list does not replace the sources needed to support an individual carrier status, procedure, deadline, customs rule, or action.

Scope and limitations

  • This page explains the editorial methodology for the 11Tracking Package Help knowledge corpus.
  • It does not explain how package tracking works or diagnose a shipment.
  • It does not accept or process a tracking number.
  • It does not replace the Privacy Policy, AI Disclaimer, Terms of Use, or official carrier documentation.
  • Carrier and government procedures can vary by division, service, country, shipment stage, and user role.
  • Current public formats and implementation details should be verified after deployment.
  • The methodology and its external references may change as the editorial workflow, product, standards, and search systems evolve.

Last reviewed: July 21, 2026 Next scheduled review: October 19, 2026 Correction contact: contact form Evidence basis: Official project policies, current search-platform documentation, web standards, accessibility guidance, and the approved private research packet