A passenger opens Google Maps, types "Lviv — Krakow" and selects the "Transit" tab. The map shows trips, departure times and carriers. If your trips are not there — for this passenger you do not exist, even if your bus goes exactly there and exactly then.
Presence in Google Maps is a free sales channel that works at the moment a person has already decided to travel. They don't need to be persuaded by advertising — they only need to be shown your trip. In this article we break down how to get there: what Google requires, what the process looks like step by step, and why most carriers do not go through it on their own.
How Google learns about bus routes
Google does not collect schedules manually and does not "find" them on carriers' websites. Public transport data gets into Maps in one standard format — GTFS (General Transit Feed Specification).
A GTFS feed is a set of structured files that describe your operations:
- stops — names and exact coordinates of each one;
- routes — which trips you operate;
- timetable — departure and arrival times at every stop;
- calendar — on which days of the week and in which periods the schedule applies;
- carrier information — name, website, time zone.
This format is used by more than 10,000 transport operators worldwide. The same feed, by the way, is read not only by Google Maps but also by Apple Maps and dozens of transit apps — one piece of work opens several channels at once.
Path one: doing everything yourself
Formally, the process is open to any carrier. It looks like this.
Step 1. Create a GTFS feed
You need to assemble all routes, stops with coordinates and timetables into files of the prescribed format. This is technical work: an error in a stop's coordinate, a time-zone mismatch or a gap in the calendar — and the feed will not pass the check.
Step 2. Run the feed through a validator
Google requires the feed to pass automatic validation with no critical errors. Typical problems at this stage: stops "jumping" off the route, night trips crossing midnight incorrectly, duplicate trips.
Step 3. Register with the Google Transit Partners programme
Next comes an application to Google's partner programme for transit data providers. You will need to confirm the right to the data: Google must be sure the schedule is submitted by the carrier itself or by a company it has authorised. If the feed is submitted not by the carrier directly but by a platform or aggregator, a Letter of Authorization (LOA) is required, by which the carrier officially authorises the submitter.
Step 4. Pass Google's review
Google's team checks the feed and the data manually. The process is not instant — from several weeks to several months, and correspondence is in English.
Step 5. Keep the feed up to date
And this is the most important part: getting into Maps is half the job. Changed the schedule, added a trip, cancelled a stop — the feed must be updated. Outdated data is the main reason carriers are removed from the listings: a passenger who came to a stop according to a Google schedule and never saw the bus will not trust that schedule again.
Why the do-it-yourself path rarely reaches the end
None of the steps is impossible. But together they require what a small or medium carrier usually does not have:
- a technical specialist who can figure out the GTFS format and validators;
- weeks of correspondence with Google in English;
- a process that updates the feed every time the schedule changes — for years, not once.
In practice, solo attempts most often stop at step 1 or get stuck at step 4. And those who did make it into Maps drop out within half a year because of an outdated schedule.
Path two: through a platform
The second option is a platform that is already integrated with Google Transit and does all of the above automatically.
The logic is simple: if your routes, stops and schedules already live in a ticket sales system, a GTFS feed can be generated from them automatically. Change the schedule in the admin panel — the feed updates itself. No manual files and no risk of "stale data".
In this model, registration with Google Transit Partners is handled by the platform operator: the carrier signs a Letter of Authorization (LOA) — and from then on the technical part, validation and communication with Google are handled by the platform. For the carrier, the process comes down to a single signature.
This is exactly how it works in BUSPORTAL: the system builds the GTFS feed from your data, keeps it correct and current, and the platform team handles registration with Google. In addition, every route gets its own SEO page — so passengers find you not only on the map but also in regular Google search.
Frequently asked questions
How much does it cost? Google does not charge for listing schedules in Maps — it is a free channel. The costs are only in preparing and maintaining the feed (yourself or through a platform).
How long does connection take? Technical preparation of the feed — from a few days. Google's review — usually from several weeks to several months. This is the longest and least predictable part of the process.
Do I need my own website? For Google Maps — no, a valid feed and confirmed data rights are enough. But the link from the route card leads to a website — if a ticket can be bought there right away, the channel works at full strength.
What happens if the schedule changes but the feed doesn't? Passengers will see the wrong times, complain, and Google may remove your data from the listings. Feed freshness is the main condition for long-term presence.
My routes are international. Does that change anything? No, GTFS supports international routes; what matters is correctly specifying the stops' time zones and trips crossing midnight.
Conclusion
Any carrier can add routes to Google Maps — the process is open and free. But between "can" and "did it and maintains it" lie the technical GTFS format, English-language moderation and the duty to update the data with every schedule change.
So the practical question is not "is it possible" but "who will do it continuously". If your schedules already live in your sales system, the feed should be generated from them automatically rather than assembled by hand. Then presence in Google Maps stops being a one-off project and becomes a permanent channel that brings passengers every day.
Note. BUSPORTAL automatically builds a GTFS feed from your routes and schedules, keeps it up to date and handles registration with Google Transit — from the Letter of Authorization to your trips appearing on the map. The first 30 days are free, with full launch support. Learn more at busportal.app.