GEO Specialist

Why it matters

You can't optimize for something you can't picture. The engine doesn't rank ten blue links. It fetches a few pages it can read, stitches an answer, and cites a couple. What gets you in changes by business. A distributor wins on spec data the engine can quote cleanly. A roofing company wins on clear, location-specific service pages. A dental group wins on consistent facts about each office. Same mechanism, different raw material.

In the field

A hydraulics distributor ranked page one on Google for a thread-size question but never showed up in the ChatGPT or Perplexity answer for it. The engine was lifting a manufacturer's PDF and a forum thread instead, because the distributor's own answer was buried in a spec sheet no crawler could read.

Edge cases

• Ranking well on Google but getting skipped by every AI answer for the same question.
• An engine citing a competitor or a generic blog for a fact you state better on your own site.
• Confusing the bot that trains a model with the bot that fetches live pages to ground an answer. They are different and behave differently.

Why it matters

Most teams have no idea what AI says about them. They assume Google rankings carry over. They don't. A prompt audit turns a vague worry into a list of specific gaps, and the gaps differ by business. A distributor checks part-substitution and spec questions. A roofing company checks 'best roofer in [city]' prompts. A dental group checks 'who does same-day crowns near me.' You can't pitch or plan a fix until you've seen the answer the buyer sees.

In the field

A four-office dental group asked ChatGPT and Gemini 'best Invisalign provider in [their city]' twenty different ways. They got named once. A single-location competitor with a tidy site and consistent reviews got named in almost every answer. That one audit was the whole case for the project.

Edge cases

• Answers that change run to run, so a single test misleads. Sample each prompt several times.
• Logged-in or personalized results that flatter you. Test signed out, ideally from a clean session.
• Treating one engine's answer as all of them. ChatGPT, Perplexity, Gemini, and AI Overviews disagree often.

Why it matters

The best page in the world is invisible if the bot gets turned away at the door. Two things commonly block it. One is the robots.txt file, the note at your site root that tells bots what they may visit. The other is a WAF, the security layer in front of your site that filters traffic. The mistake repeats across businesses. A distributor's anti-scraping rules block scrapers and the AI crawlers along with them. A roofer's host turns on a 'block all bots' default. A dental group's new site ships with crawler-blocking left on from the test version.

In the field

A roofing company stopped showing up in Perplexity answers overnight. A WAF rule set to block 'all bots' was blocking the AI crawlers too. Allowing those specific bots back in brought the citations back within a couple of weeks. Nothing about the content had changed.

Edge cases

• robots.txt allows the bot but the WAF blocks it. The two settings disagree and the WAF wins.
• Blocking the training bot (GPTBot) but meaning to block the live-answer bot (OAI-SearchBot), or the reverse.
• A rule that only blocks data-center traffic, which is exactly where these bots live.
• Spec sheets or prices behind a login or a customer portal, which no anonymous bot can reach.

Why it matters

Engines read the page as it arrives, and many don't run JavaScript (the code that fills in details a moment after the page loads). If your specs, prices, or compatibility data only appear after that code runs, or live inside a downloadable PDF, most AI crawlers see a blank or a link they won't open. The trap looks different per business. A distributor hides specs in PDF datasheets and JS spec tabs. A home-services site loads its service-area list with JavaScript. A dental group puts hours and treatments in a booking widget that renders late.

In the field

A distributor's product pages showed a rich spec table to a human, but the table loaded from JavaScript. With JavaScript off, the page was a title and a buy button. Moving the same spec data into plain HTML tables got those specs quoted in AI answers for the first time, across the whole catalog, because it was one template fix.

Edge cases

• The whole spec table living in a downloadable PDF the engine treats as a link, not text.
• Cross-reference or interchange data ('equivalent to part X') trapped in a JS lookup tool.
• Content pulled in by a third-party widget the bot can't load.
• Later pages of a long list that only appear after a click or scroll the bot never does.

Why it matters

Engines assemble a picture of you from your site plus other sources they already trust, then they trust the version that agrees with itself. Thin or contradictory signals get you skipped for a marketplace or a louder competitor. What needs to line up changes by business. A distributor needs the same brand and product names across its site, the manufacturers' sites, and trade directories. A multi-location roofer needs the same name, address, and service list everywhere. A dental group needs each office's details consistent across its site, Google, and health directories, not just the head office.

In the field

A multi-office dental group listed slightly different practice names and hours on its own site, Google, and two health directories. AI answers kept naming the wrong office or saying it was closed. Once every source said the same thing, the engines started naming the right office for 'dentist open Saturday near me.'

Edge cases

• One generic company description instead of distinct, accurate detail per location or office.
• An old address or phone number lingering on a directory you forgot you had a listing on.
• Manufacturer pages naming a product one way and your catalog naming it another.
• Review or rating claims on your site that don't match the public profiles, which engines distrust.

Why it matters

Structured data tells an engine 'this is a product, a local business, a service, a review,' which feeds rich results and helps AI answers quote you correctly. The right type and scale depend on the business. A distributor needs Product schema with part identifiers (MPN and GTIN, the manufacturer and global codes that pin down an exact part) across hundreds of thousands of SKUs, which only works template-side. A roofer needs LocalBusiness and Service markup per location. A dental group needs a LocalBusiness block per office, not one generic Organization block for the whole group.

In the field

A distributor added Product schema with MPN and GTIN to its product template. Because it was one template, the markup landed on every SKU at once instead of being hand-coded per page. Engines started returning the correct part and price in answers, and the work was a single change, not a hundred-thousand-page slog.

Edge cases

• Markup that claims something not visible on the page, which is against Google's rules and can get you penalized.
• One Organization block for a multi-location business instead of a LocalBusiness block per location.
• Schema generated by JavaScript that the bot never runs, so it sees no markup at all.
• Self-serving or fake review markup, which gets penalized rather than rewarded.

Why it matters

You can't lean on rankings here. Only about 12% of AI-cited URLs rank in Google's top 10 for the same prompt (Ahrefs), so a page can be quoted without ranking at all. That means a new scoreboard: mention rate, citation share, and AI share of voice, sampled from a set of prompts you keep stable so the trend means something. The prompt set differs by business, the method doesn't. A distributor tracks spec and substitution questions. A roofer tracks city-and-service questions. A dental group tracks treatment-and-location questions. Tools like Ahrefs Brand Radar, Profound, and Otterly automate the sampling.

In the field

A roofing company built a 25-prompt set of real homeowner questions and ran it monthly across four engines. Its citation share for 'storm damage roof repair in [city]' went from near zero to leading two named competitors over a quarter. That was the first hard proof the GEO work was paying off.

Edge cases

• Treating one run as the truth when answers shift between runs. Sample each prompt several times.
• Changing the prompt set every month, so you can't compare across time.
• Counting a mention where the brand is named but not credited as the source. Mention and citation are different.
• Reading a single engine and calling it your AI visibility. Track several.

Why it matters

Someone has to make the calls nobody below them can. How much goes to ranking vs getting cited. Which prompts and competitors define success. What to do when an engine states a brand fact wrong. The stakes change by business. For a distributor selling pressure-rated or chemical-compatible parts, an engine confidently stating the wrong rating is a safety and liability problem, not a marketing one. For a dental group, a made-up price or service is a trust problem. For a roofer, a wrong service area sends real leads to the wrong place. Because the field is new, the senior person also spends real time explaining it to leadership and the wider team. The Caterpillar posting for this role called that teaching part out directly.

In the field

A senior GEO lead at an industrial distributor found ChatGPT repeatedly stating a higher pressure rating for a fitting than the spec allowed. They ran it as a correction campaign: fixed the source page, corrected the manufacturer and directory data feeding the error, and tracked the answer until it came back right. That's governance, not optimization.

Edge cases

• Over-investing in GEO while the SEO that still drives most traffic quietly slips.
• No owner for accuracy, so a dangerous or false AI claim about the product goes unwatched.
• Claiming credit you can't prove, since attribution from AI answers is genuinely hard to measure.
• Keeping GEO as one person's secret instead of teaching it, so it dies when they leave.