Five pillars, classic rankings, answer engines, generative citations, AI training presence, and post-click experience, mapped to cabin crew product pages on layvrcrew.com.
Rank for high-intent crew queries on Google, roster, pay, layover, staff travel.
Own clusters: who's on my layover, cabin crew pay calculator, flight attendant roster app, airline staff travel. Never use “sleep” as a keyword, use layover.
Canonicals on every page, sitemap from scripts/generate-sitemap.py, titles ≤60 chars, meta ≤160, Firebase Hosting www→apex. JSON-LD in <head>, never JS-only.
Press kit at /press/, founder story at /about/, App Store / Play listings, crew community mentions. Pitch with consistent “Layvr | cabin crew layover app” boilerplate.
Static HTML + cached CSS/JS, compressed screenshots, short paragraphs, crew voice. Mobile-first layout on every landing URL.
Calendar: summer roster swaps, Christmas staff travel, Easter short layovers, bid season. Publish under /blog/ and refresh best layovers by airline.
Win featured snippets, People Also Ask, voice, and AI-bot answer boxes with clear Q&A.
Answer “How do cabin crew check pay?”, “What is EASA FDP?”, “Who's on my layover?” in plain blocks with Speakable schema. Hub + per-answer URLs: crew answer bank.
FAQPage on home, pay, roster, layover, Pro. HowTo on roster import and how to add roster.
Cover PAA from FDP, per diem tax, RosterBuster alternatives, staff travel ZED/ID90, see blog guides and the answer bank.
Lead with a 40, 60 word definition, then steps or a table. Example pages: EASA FDP explained, payslip explained.
Natural phrasing (“how do I import my roster into Layvr”) matching spoken search. Keep CTAs thumb-friendly on mobile.
Earn citations in ChatGPT, Perplexity, Gemini, and Google AI Overviews.
Publish citable facts: price (£5.99 Pro), no ads, verification, platforms. Machine-readable brief: /llms.txt.
Repeat entities: Layvr, Bruno (SAS LHR), EASA, RosterBuster, App Store, Google Play, airline names on staff-travel pages. Organization + Person JSON-LD on about and press.
Founder as working cabin crew, press kit, contact email, Privacy/Terms links, changelog and status pages. Experience first-person where true.
Encourage verified App Store / Play reviews; participate in crew forums with product URLs (not spam). Track Reddit/Quora mentions of “Layvr” + layover.
Ship product video + App Store deep links; keep install CTAs on every commercial page. MobileApplication schema with downloadUrl on the homepage.
Stay present in the corpora and brand graphs that train and ground AI models.
Keep layvrcrew.com crawlable (Allow: /), publish durable HTML guides, maintain llms.txt and llms-full.txt for model-friendly summaries.
Public GitHub org/repo when open-source surfaces exist; Wikidata item when notability is met; never invent wiki entries. Document entity IDs in the press kit when available.
One boilerplate everywhere (press, about, app stores, social). sameAs links: X, Instagram, LinkedIn, App Store, Play.
Crew-written experience for layover and pay guides; AI only for drafts that humans verify. Prefer first-hand roster/pay ops language.
Stable URLs, unchanged brand name “Layvr”, annual refresh of cornerstone guides, changelog of product facts models may quote.
After the click: convert cabin crew into installs, speed, clarity, trust, CTAs.
Static hosting, viewport meta, safe-area padding, thumb-sized buttons. Primary path: landing → App Store / Play.
One job per section: who is on layover, how pay works, how roster imports. Screenshots of real product surfaces, not stock aviation.
Exact anchors: “Download Layvr free”, “cabin crew pay calculator”, “who's on my layover”. App Store + Play on commercial pages.
GA4 on landings; test hero CTA copy and proof lines. Never degrade free-tier clarity for Pro upsell.
Route by intent: pay cluster → /pay/, roster → /roster/, layover social → /layover/, staff travel → /staff-travel/.
Search only works if the app answers “who's on my layover and how do I reach them?”