Google Package Tracking Early Access Is Closed to New Partners
Google's package-tracking Early Adopters Program no longer accepts new partners. Existing integrations still have documented latency, data, and privacy requirements.
Published August 9, 2026: Google updated its package-tracking documentation on July 14, 2026 to say the Early Adopters Program is no longer accepting new partners. The package-tracking feature still exists, and Google’s current page continues to document requirements for participating carriers.
The actionable distinction is between an existing integration and a new application. Existing participants should continue monitoring API quality and data accuracy; prospective partners should not follow old articles that still direct them to an open interest form.
What changed—and what did not
| Question | Current documented state |
|---|---|
| Does Google describe a package-tracking Search feature? | Yes |
| Is it available across Google Search languages and countries? | Google says yes |
| Can a new carrier join the Early Adopters Program? | No; new partners are not being accepted |
| Are API requirements still documented? | Yes, for the integration |
| Does structured data alone activate the feature? | Not documented as the integration route |
The closure is an intake change, not an announcement that existing package results have been removed. Do not rewrite it as “Google ended package tracking” unless Google publishes that broader change.
Why old implementation guides are now misleading
Google’s December 2019 announcement invited shipping companies to review eligibility requirements and submit an interest form. A guide built around that call to action is stale even if its technical description remains partly accurate.
Update carrier documentation, agency decks, integration roadmaps, and internal tickets that still describe the program as open. Preserve the original publication date and add a material update note instead of silently changing history.
Link to Google’s live documentation rather than copying the entire specification. Program availability can change faster than a static tutorial, and the live page is the appropriate source of truth for intake status.
Requirements existing partners should monitor
Google’s current page expects almost no API downtime, an average response within 700 milliseconds, and a 95th percentile not exceeding 1,000 milliseconds. It warns that package information may stop displaying when the API does not meet those requirements.
The response must include CurrentStatus with the date and time the status became valid and any error state. Recommended information includes delivered and promised dates, tracking number and URL, support phone numbers, transit events, creation and pickup dates, timestamp and location events, and whether rescheduling is available.
Google says not to send personal data or geographical information about the package recipient or sender. Treat privacy filtering as an API contract, not an editorial preference.
Build an operational checklist
- Verify whether your company is an existing participant before allocating integration work.
- Monitor availability, average latency, 95th-percentile latency, and error rate.
- Validate required fields and timestamp formats against the live specification.
- Test that no recipient or sender personal data leaves the carrier system.
- Compare displayed status with the carrier’s source of truth.
- Maintain an incident owner for stale status, API downtime, and schema changes.
- Subscribe to Google Search documentation updates and review program status regularly.
These checks apply to existing integrations. They do not create a path for a new partner while intake remains closed.
What prospective partners can do
Keep the carrier’s own tracking pages fast, accessible, indexable where appropriate, and accurate. Maintain stable tracking URLs, clear customer-support routes, and privacy-safe public status information. Those improvements help users regardless of Google’s partner intake.
Document readiness without claiming approval: API latency, supported fields, privacy controls, international coverage, and incident response. If Google reopens or replaces the program, a current readiness record reduces the time required to evaluate the new terms.
Do not submit personal shipment data through general Google feedback or public forums in an attempt to request access.
Ask a question or join the discussion