Last updated: August 2026
Two pages can cover the same topic, rank within a place of each other, and only one gets quoted by ChatGPT, Perplexity and Google AI Overviews. The difference is almost never the writing quality. It is the structure.
The seven structural must-haves
| Element | Presence in cited pages | Taxi / limo application |
|---|---|---|
| Bullet lists and numbered items | ~100% | Feature lists, step-by-step booking flows, compliance checklists |
| Clear H2/H3 section headings | ~92% | Headings phrased as customer questions |
| Names specific companies/tools | ~75% | Name real platforms and competitors in comparisons |
| Includes hard numbers and data | ~65% | Fares, setup costs, monthly fees, fleet sizes, timelines |
| Comparison or evaluation framework | ~50% | A table scoring options against stated criteria |
| 'How to choose' decision guide | ~33% | Short if/then section matching reader to option |
| Year in title | ~25% | '2026' on best-of, pricing and comparison pages |
1. Lead every section with a list
Prose describes; lists get extracted. Any section describing features, steps, requirements or options should convert into a bullet or numbered list. Example, rewritten:
- Before: "Our dispatch platform offers a range of powerful features designed to streamline your operations."
- After: "Included: auto-dispatch by nearest driver, fixed airport fares, card payment with pre-authorisation, driver app with turn-by-turn, passenger SMS tracking link, account invoicing with cost centres."
2. Phrase headings as questions
Assistants match a user's question against headings. Use the phrasing customers use:
- "How much does taxi dispatch software cost for 10 vehicles?"
- "Do I need a PHV operator licence to take airport bookings?"
- "Can I keep my phone number when switching dispatch systems?"
3. Name real companies and tools
Vagueness reads as evasion to both people and models. Say which platforms you integrate with, which you migrate customers from, and which suit different fleet sizes. Our own comparison set — vs Limo Anywhere and the ranked 2026 dispatch software guide — exists for exactly this reason.
4. Put hard numbers on the page
- Setup and monthly fees, published, not "from" figures behind a form
- Fleet-size bands the product fits (for example 1 to 25 vehicles)
- Implementation timelines in days
- Measured outcomes: no-show reduction, admin hours saved, commission avoided
A concrete example beats a claim: a fleet of 10 cars doing 300 jobs a month at £28 average pays roughly £2,100 a month in 25 percent aggregator commission. A $399 setup plus $10 per month web booker recovers that in the first week of use.
5. Add a comparison framework
State your criteria before the comparison, then score honestly. Criteria that work for transport software: total 36-month cost, per-driver fees, contract length, migration support, licensing compliance, payment handling, and whether white-labelling is included.
6. Include a "how to choose" section
- If you run 1 to 5 vehicles: a web booker plus payment capture is usually enough.
- If you run 6 to 25 vehicles: add auto-dispatch, driver app and account invoicing.
- If you run 25 to 100 vehicles: prioritise API access, SLA and multi-depot support.
- If you run over 100 vehicles: enterprise platforms with dedicated integration teams fit better.
7. Date it and keep it dated
Put the year in the title for comparison and pricing content, show a visible "last updated" line, and set dateModified in Article schema. Refresh annually.
Content structure built into the platform
Every Taxi Web Design blog and solution page ships with Quick Answer blocks, FAQPage schema, comparison tables and server-rendered HTML — the structure assistants quote, without you formatting anything by hand.
A reusable page template
- Title with the year where relevant
- Hero image with descriptive alt text
- 100-word Quick Answer directly under the H1
- Four to eight H2 sections, each opening with a list or table
- One comparison table with stated criteria
- A "how to choose" if/then block
- Six to ten FAQs with FAQPage schema
- Three to six internal links to related pillar pages
- Visible last-updated date and Article schema
What to avoid
- Superlatives with no evidence ("the best", "world-class") — models discard them
- Prices hidden behind a contact form
- Walls of text with no headings for 800 words
- Stock claims copied from a competitor's site — duplication kills citation
- Contradictory pricing across pages, which destroys extraction confidence
Related: AEO vs GEO vs SEO and tracking AI brand mentions.
