Tiket.com AEO|SEO Audit by Novastacks AI
Executive Summary
What It Is Costing tiket.com — and Why the Gap Is Closable
We audited 7 core page types across tiket.com, Traveloka, and Trip.com. tiket.com drives 4.9 million estimated monthly visits in Indonesia — a strong foundation. But Traveloka pulls 7.4 million from the same market, and that 2.5 million visit gap translates directly to bookings tiket.com is not capturing.
The gap is not about brand or product. On 187,890 keywords where both domains compete for the same traveler, Traveloka's average position is 11.4. tiket.com's is 21.9. A 10-position difference across nearly 200,000 keywords represents significant lost market share — and the findings point to three specific causes:
Lost rich results and AI visibility. Multiple high-traffic page types are missing structured data that both competitors already have. Traveloka and Trip.com are eligible for rich snippets, FAQ carousels, and AI-generated recommendations on queries where tiket.com is invisible — even when tiket.com has the better product.
Weakened conversion signals to Google. Several of tiket.com's highest-traffic pages send incorrect or incomplete signals about what they offer. When Google cannot confidently identify a page's purpose, it ranks competitors who make that identification easy. tiket.com is effectively asking Google to guess.
Content depth disadvantage on key categories. On destination and route pages, competitors serve 2-3x more content — travel guides, airport information, local recommendations. Google and AI systems treat these richer pages as more authoritative answers. Travelers researching trips are landing on competitor pages instead.
What makes this closable: tiket.com has 260 keywords in positions #2 and #3 — closer to the top than either competitor. These are high-intent travel queries where tiket.com is already visible but not winning the click. The revenue is right there.
3 core pages serve "Blibli tiket group" as title tag Critical
Homepage, Hotel Homepage, and Hotel Destination pages all display "Blibli tiket group" instead of travel related titles.
Homepage and Hotel Homepage have ZERO structured data Critical
No Organization, WebSite, or SearchAction schema on either page.
5 page types missing FAQPage schema Critical
tiket.com is the only OTA without FAQPage schema on Flights, Route, and Destination pages.
Destination page has 73% thinner content High
3 content sections vs Traveloka's 8+. Missing travel guides, airport info, and attractions content.
Homepage serving English content to Indonesian market High
The /id-id path serves English meta description and H1 tag.
| Domain | Ranked Keywords | Est. Traffic (ETV) | #1 Positions | #2 to 3 | #4 to 10 |
|---|---|---|---|---|---|
| traveloka.com | 402,150 | 7,423,100 | 173 | 217 | 105 |
| tiket.com | 248,825 | 4,916,247 | 69 | 260 | 157 |
| trip.com | 266,492 | 1,718,041 | 46 | 165 | 262 |
Page Level Health
How each page type performs across title tags, structured data, FAQ schema, and content depth
| Page Type | Title Tag | Structured Data | FAQ Schema | Content Depth | Overall |
|---|---|---|---|---|---|
| Homepage /id-id | Wrong | ZERO | None | English content | Needs Fix |
| Flights /pesawat | Good | ItemList only | Missing | 795K chars, 8 H2s | Partial |
| Route /rute/jakarta-ke-bali | Good | Product + Breadcrumb | Missing | 460K (competitors 2.5x) | Partial |
| Destination /tujuan/bali | Good | Product + Breadcrumb | Missing | 3 H2s (competitors 8+) | Needs Fix |
| Airline /maskapai/garuda | Good | FAQ + Product + Breadcrumb | Has it | 616K chars, 8+ H2s | Strong |
| Hotel Homepage /hotel | Wrong | ZERO | None | Listing only | Needs Fix |
| Hotel Destination /hotel/.../bangkok | Wrong | Local + FAQ + Breadcrumb | Has it | 1,080K chars, 8 H2s | Fix Title Only |
Only 2 out of 7 page types are fully healthy (Airline and Hotel Destination). The other 5 have gaps that directly reduce visibility in both Google search results and AI generated answers.
See the full page-by-page breakdown
Detailed health scores with competitive benchmarks for all 7 page types
Book a CallTechnical Issues
Critical rendering and structured data issues impacting search visibility and AI indexing
Three of tiket.com's most important pages serve "Blibli tiket group" as their title tag instead of travel relevant titles.
The title tag is the first thing Google reads. It is like the headline of a newspaper article. "Blibli tiket group" tells Google nothing about flights, hotels, or travel. Traveloka's hotel page title says "Booking Hotel Murah & Penginapan Terdekat" — immediately signaling to Google and AI what the page is about.
| Page | Current Title | Expected Title |
|---|---|---|
| Homepage | "Blibli tiket group" | "tiket.com - Satu Aplikasi Kebutuhan Liburanmu" |
| Hotel Homepage | "Blibli tiket group" | "Booking Hotel Murah Online Harga Promo - tiket.com" |
| Hotel Bangkok | "Blibli tiket group" | "Hotel di Bangkok Harga Murah Promo - tiket.com" |
No JSON LD schema at all. No Organization, WebSite, or SearchAction.
Without Organization schema, Google and AI treat tiket.com like a stranger who forgot to introduce themselves.
Zero JSON LD blocks. However, all three OTAs fail here — first mover advantage opportunity.
8 FAQ ready H2 sections but NO FAQPage schema. Traveloka has both Product and FAQPage schema.
Both Traveloka and Trip.com have Product + FAQPage + BreadcrumbList. tiket.com is the only OTA without FAQPage on route pages.
Same pattern as route. Both competitors have FAQPage markup on destination pages.
Traveloka has HowTo schema on route, destination, AND airline pages. tiket.com has none.
See the full technical breakdown
8 technical issues with competitive comparisons and fix recommendations
Book a CallMissing Features — Content Gaps
Content and feature gaps where Traveloka and Trip.com outperform tiket.com
tiket.com's Bali destination page has only 3 H2 sections. Traveloka has 8+ with rich guide content. Traveloka's page is 2.5x larger.
Traveloka's storefront has a full window display. tiket.com's has a price list and a search box. Google and AI favor pages that answer more questions in one place.
| Content Feature | tiket.com | Traveloka | Winner |
|---|---|---|---|
| H2 sections | 3 | 8+ | Traveloka |
| Travel guide | NO | YES | Traveloka |
| Airport info | NO | YES | Traveloka |
| Content size | 444K | 1,131K | Traveloka (2.5x) |
6 H2 sections vs Traveloka's 8+. Traveloka's page is 2.6x larger by content volume.
H2s are hotel names instead of editorial content. Traveloka has content sections with trust signals.
/pesawat links 96% to itself. Almost no links to /hotel, /kereta, or /explore.
See detailed content gap analysis
4 content gaps with page-by-page competitive data
Book a CallSEO Title & Meta Description Issues
Irrelevant or misconfigured title tags and meta descriptions
Meta description reads: "Book tickets for plane, train, hotel, car rentals & fun trip only at tiket.com." — English despite /id-id Indonesian locale.
H1: "tiket.com - One app for your holiday needs." Should be Bahasa Indonesia.
Good keywords but missing "tiket.com" brand. Traveloka includes brand in every title.
See full SEO audit with fix recommendations
Title tag and meta description fixes for every page type
Book a CallContent Issues
Irrelevant content and geo-targeting mismatches
Indonesian homepage H2 sections include Singapore hotels: "Quest Vibe Dewi Sri Bali", "BEAT. Arts Hostel @ Chinatown", "A Hotel Joo Chiat".
H3s include promotional slogans instead of informational content headings. Dilutes topical signals.
See full content audit
Geo-targeting fixes and content strategy recommendations
Book a CallOther Issues
Semantic HTML gaps and competitive observations
Missing <nav>, <article>, and <footer> elements across key pages.
Trip.com implements Product + FAQPage + BreadcrumbList on all three page types. tiket.com is the only competitor without FAQPage on route and destination pages. However, Trip.com has zero internal links — tiket.com's strong internal linking (181-240 links) is a genuine advantage.
See competitive intelligence details
Semantic HTML audit and Trip.com schema analysis
Book a CallCompetitive Feature Matrix
Full page-by-page comparison across tiket.com, Traveloka, and Trip.com
| Feature | tiket.com | Traveloka | Trip.com |
|---|---|---|---|
| FLIGHTS HOMEPAGE | |||
| Schema: Product | NO (has ItemList) | YES ✓ | NO |
| Schema: FAQPage | ✘ NO | YES ✓ | NO |
| Internal Links | 350 | 134 | 1 |
| ROUTE PAGE | |||
| Schema: FAQPage | ✘ NO | YES ✓ | YES ✓ |
| Schema: HowTo | ✘ NO | YES ✓ | ✘ NO |
| DESTINATION PAGE | |||
| Schema: FAQPage | ✘ NO | YES ✓ | YES ✓ |
| H2 Sections | 3 | 8+ | 8 |
| AIRLINE PAGE | |||
| Schema: FAQPage | YES ✓ | YES ✓ | YES ✓ |
| HOTEL HOMEPAGE | |||
| Title Optimized | ✘ NO | YES ✓ | YES ✓ |
| HOTEL DESTINATION | |||
| Title Optimized | ✘ NO | YES ✓ | YES ✓ |
| HOMEPAGE | |||
| Language Match | ✘ NO (English) | YES | YES |
See the complete 40+ point matrix
Full feature comparison across all 7 page types
Book a CallScore Impact & Recommendations
How fixing these issues improves the AEO score and projected outcomes
Quick Fixes 1-2 Weeks
Content Investments 1-3 Months
See your full roadmap & score projections
Prioritized action plan with implementation timeline
Book a CallReady to close the gap with Traveloka and Trip.com?
tiket.com has strong foundations on airline and hotel destination pages, plus superior internal linking. Extending quality across all 7 page types positions tiket.com for AI visibility leadership.
Book Your Free Discovery Call30 minutes · Free · No commitment