You cover twenty airports. You would like somebody searching for your service at any one of them to find you. So you go to claim a Google Business Profile for each base, and almost none of them qualify.
This is not a technicality you can argue your way around, and it is worth understanding before you spend money on the wrong fix.
Why the profiles do not exist
A Business Profile wants a location a customer could walk into, with your name on it, at an address that can be verified. Aviation locations are usually none of those things.
- Your space is inside somebody else’s FBO or hangar, under their address and their signage.
- The base is covered by a mobile team that arrives when there is work, so nobody is sitting there to answer a door.
- The address on file belongs to a landlord who also hosts two of your competitors.
- The field is remote coverage from another city, which is a real service and not a location.
Inventing an address to get the listing is the one move to rule out completely. It is a suspension risk, it takes the whole profile with it when it goes, and it is a lie told to an industry that checks things for a living.
What that actually costs you
Be precise about the loss rather than vague. On a local intent search the map pack sits above the organic results and takes a large share of the clicks. Losing it is real.
What it does not do is remove you from the results. The organic listings underneath are still there, they are still clicked, and in a market with five credible vendors rather than five hundred, the people clicking them are the ones who matter. The volume is small enough that a single call can justify the whole exercise, which is the arithmetic this industry runs on and the opposite of how most agencies are used to thinking.
One page per base where you have people
The instinct is to build a page for every airport you could theoretically reach. Resist it. A page you cannot fill with something only you could have written is a page that will not rank and should not exist.
So the line is staffed coverage. If you have people based at a field, it gets a page. If you reach it by sending a team, it gets a mention on a regional page and a line in a coverage table, not a page of its own.
That is the same argument as ten thin location pages losing to three good ones, and it applies harder here, because your audience can tell immediately whether the person who wrote the page has ever been to that field.
What goes on the page
Everything on this list is something a competitor cannot copy without lying:
- Who is actually based there, and how many of them.
- Hours of coverage, and whether that includes after hours and weekends.
- Which terminals, FBOs or hangars you operate out of at that field.
- What you can do there and what you cannot, stated plainly. The honesty reads as competence.
- Typical response time for a call at that field, and what changes it.
- Which nearby fields the same team covers, with the travel arrangement described.
- Anything specific to the airport: ramp restrictions, badging, environmental rules, curfews.
A page built from that list is long, specific and impossible to generate. A page built by swapping a city name into a template is the thing everybody else did, and it is why their location pages do nothing.
The one office you probably can claim
Most operations have exactly one location that does qualify. A real office, with your name on it, at an address you can receive mail at. Claim that one properly and treat it as the anchor of the whole thing.
It will not rank you at the other nineteen fields, and nobody should pretend otherwise. What it does is give you one verified, consistent business record that everything else can point back to, which matters more than people expect for how search engines and AI answers decide you are a real company rather than a page.
Structure: one hub, then the bases
The shape that works is a coverage page that owns the whole footprint, with the staffed bases hanging off it as their own pages and the remote fields named on the hub rather than given pages.
The hub earns the broad searches, the ones with a region or no place at all in them. The base pages earn the narrow ones with a field name in them. Each base page links up to the hub and across to the two or three fields the same team covers, which is how somebody searching the wrong field still lands somewhere useful.
That linking is not decoration. It is the mechanism by which a page nobody links to from outside can still be found, which is most of your pages.
Name the field the way people name it
Use the ICAO code, the IATA code and the common name, because your buyers use all three and they do not agree with each other. A page about Palm Beach should contain KPBI, PBI and Palm Beach International, and a page about Teterboro should contain KTEB and TEB. This is the identifier problem in miniature, and it has an article of its own.
The URL should use the plain name rather than the code, because the code means nothing to a search engine’s understanding of place, and put the codes in the page title and the first paragraph where they carry weight.
Structured data without fake addresses
You can describe coverage honestly in schema. An organization with an areaServed list, naming the fields and the regions, says exactly what is true without claiming a storefront you do not have. What you must not do is publish a LocalBusiness block with an address you cannot stand behind, which is the schema equivalent of the thing that gets profiles suspended.
The page still has to survive being read
Ranking a base page is half the job. Somebody arriving on it has a specific question, usually whether you can actually help them at their field this week, and the page either answers it or sends them back to the results.
That is the same standard every page on an aviation site is held to, and it is the subject of a separate piece on what these buyers are checking.
How to tell whether it worked
Not by a ranking average across twenty terms, which will move for reasons that have nothing to do with you. Look at the named fields one at a time and ask whether the page is on the first screen for the two or three phrases a customer at that field would actually type.
Then look at the calls. In a market this size, the honest measure is whether people arrive already knowing what you do at their field, which is a thing you can hear in the first thirty seconds of a phone call and cannot see in a dashboard.
Questions
If you want somebody to go through your coverage map and work out which fields deserve a page and which do not, that is the first thing I do on local search work for a multi base operation. Tell me which fields you are staffed at and I will tell you what I would build.
