Somebody needs a part. They do not search for “aircraft interior components supplier”. They search for the number stamped on the old one.
Somebody needs service at Teterboro. They do not search for “aviation services New Jersey”. They search KTEB, because that is how the field exists in their head.
This is the single most common thing I see wrong on aviation websites, and it is usually the result of somebody doing their job properly. A copywriter is taught to remove jargon and write for a general reader. In most industries that is correct. Here it deletes the exact strings your buyer is typing.
The identifiers that matter
- Part numbers, including superseded and alternate numbers.
- Airport codes, ICAO and IATA, which are different and both used.
- Airframe designations, in every form people write them.
- TSO and PMA references where they apply.
- AD and service bulletin numbers, when you have something useful to say about one.
- Engine and APU model designations.
None of these are decorative. Each one is a string somebody types when they have a specific problem and a reason to solve it today.
Aircraft get written three different ways
A Phenom 300 is also a Phenom 300E and also an EMB-505, and the person searching uses whichever one they learned first. If your page only says one of them, you are invisible to the people who say the others.
The fix is not to spray all three into every sentence. Put the common name in the heading where a human reads it, and put the full designation in a specification line or a parenthesis where it is natural. That covers the searches without making the page unreadable.
The parts catalog problem
This one is worth being technical about, because it is where the largest amount of value quietly goes missing.
A catalog where part numbers only appear after somebody types into a search box is a catalog that does not exist as far as search is concerned. The numbers are in your database, not on any page. There is nothing to index and nothing to rank.
The same is true when numbers are baked into images, or rendered by script after the page loads. Traditional crawlers will often cope with the second case. AI crawlers frequently will not, which is a problem worth understanding on its own.
What works is ordinary, boring and durable. Each part gets a real URL with the number in the page title, in a heading and in the body text. Alternate and superseded numbers are listed on the same page, because the person searching may only have the old one. Product structured data carries the manufacturer part number in the field built for it. None of this is clever. It is just present rather than absent.
Where an identifier earns its place
Position matters more than repetition. An identifier in the page title and an H1 or H2 is doing real work. The same identifier repeated eleven times in body copy is doing none, and is making the page worse to read.
The order I would use on a part page: page title carries the primary number, the H1 carries it in human form, a specification table carries the alternates and supersessions, and the body explains what the thing is for. That covers the exact match searches and still reads like a page written by somebody who knows the part.
Search boxes and filters are not URLs
A related failure is a catalog where everything is reachable, but only through filters that generate addresses nobody can link to and search engines will not keep.
This produces two problems at once. The pages that matter are not indexed because they have no stable address, and thousands of filter combinations are discovered and then abandoned, which is the discovered, currently not indexed pattern showing up in Search Console. A real URL per part solves both.
The line between useful and stuffed
There is an obvious way to overdo this and it is worth naming so nobody swings too far. A page listing four hundred part numbers it has nothing to say about is spam, and both Google and your reader will treat it that way.
The test is whether the identifier is on the page because the page is genuinely about that thing. A part page that carries its own number, its alternates and its specifications is about that part. A services page with a footer of two hundred codes is about nothing.
A test you can run in five minutes
Take the ten things customers ask you about most often, whether that is parts, fields or airframes. Write down the exact string a customer would type for each one. Then search your own site for that string, using your own site search.
If your own search cannot find it, no search engine can either, because you have just proven the string is not in your content. That is usually a much shorter conversation than a full technical audit, and it tends to find the same problem faster.
Airport codes deserve the same treatment
The same rule applies to fields. A page about a base should carry the ICAO code, the IATA code and the name people say out loud, because those three are used by different people for different reasons and they do not substitute for each other.
Which fields deserve a page at all is a separate and more consequential question, and it is the subject of its own article.
One thing not to publish
Not every identifier belongs on a public page. Export controlled information, anything under a customer confidentiality agreement, and pricing you have agreed not to publish all stay off. The point here is that legitimate public identifiers keep getting removed by accident, not that everything should go up.
Questions
If your catalog or your service pages are missing the strings your buyers type, that is usually a structural fix rather than a writing one, and it is the kind of thing I look at first on an aviation site. Send me a link and I will tell you what is and is not findable.
