Expedify — The Full SEO Roadmap

Full Roadmap AI Strategy Live Comparison Copy-Paste Examples Snapshots

!The thing to fix first

Cut the indexable surface down to the pages that can actually compete. The binding problem is not missing content — it's that roughly 190 near-identical ~828-word driving guides drag down the site-wide quality signal on a brand-new, YMYL-adjacent domain. Google's scaled-content assessment is site-wide, not per-page: those thin pages suppress the ~202 genuinely good money pages that share the domain, and consume the small crawl allocation a new site gets.

The move (a few hours, reversible): consolidate the thin driving guides into a smaller set of deep guides (prune now, rebuild deeper in batches as each clears a depth gate) — then pour every content hour into the India nationality corridor, the one asset that can actually rank at this stage. The prune and the rebuild are the same asset: fewer, deeper driving guides, not fewer driving guides forever.

Where Expedify stands today

Measured baseline (pull date 2026-08-25) — the "from X" that every target in this roadmap is a "to Y" against. Figures are evidence from our research pulls, not estimates.

Metric	Value	Source	What it means for strategy
Competitor keywords analyzed	13,154	Ahrefs exports (visahq / cibt / ivisa)	The size of the winnable keyword universe we're working from
Money keywords (KD ≤45, vol ≥150)	710	Ahrefs exports	The realistic ranking pool, not all 13k
Distinct money pages	~202	Destination + nationality-tuple mapping	What "keep from the thin layer" protects
Low-KD pocket (KD 0–11)	e.g. indonesia-for-indians 10k/KD1	Ahrefs exports	The only pocket a low-authority site can rank in without links — the India corridor seed
Thin driving guides	~190 at ~828 words	Live-site review (25 Aug)	The prune-to-earn target; consolidated, not deleted
Money pages with schema	0 JSON-LD blocks	Raw-HTML fetch (25 Aug)	The cheapest fix — machine readability is missing
AI crawler access	Open (robots.txt allows all)	Live check (25 Aug)	Eligibility precondition already met — don't break it
Indexed-country-page count	Not yet measured	Needs Search Console	The one open gate — this is the hard P0 check

Baseline to be completed with Search Console data (indexed URLs, sessions, rank positions) as the first Phase 0 action; those are marked "not yet measured" above rather than assumed.

All the channels, ranked by newcomer-applicability

Tier 0 = do now · Tier 1 = the engine · Tier 2 = multipliers · Tier 3 = later.

Tier	Channel	Now	Outcome	Time / effort
0	Index-quality gating (prune to earn) — keep only pages that can rank	High	Defense	Weeks / low
0	Technical / indexation foundation — crawl, sitemaps, canonicals, depth, IndexNow	High	Defense	Weeks / low
0	Classic organic on low-KD keywords (KD 0–11 first, never head terms)	High	Traffic	Months / medium
0	Nationality-tuple moat (the /for-indians/ corridor)	High	Traffic	Months / medium
0	Schema on money pages — machine readability	High	Trust	Weeks / low
0	E-E-A-T / entity / brand identity — the trust layer	High	Trust	Weeks / low
1	Hub-and-spoke + corridor internal linking	High	Authority	Months / low
1	Driving-guide depth remediation	High	Traffic	Months / medium
1	Freshness / rule-change changelog	Medium	Trust	Months / medium
1	Conversion optimisation on money pages	High	Trust	Weeks / low
1	Cannibalisation control (destination vs tuple)	High	Defense	Weeks / low
1	GSC / log-driven prune-and-double-down flywheel	Medium	Defense	Months / low
2	Proprietary data asset as link bait (Requirements Index)	Medium	Authority	Months / high
2	Digital PR / editorial link building	Medium	Authority	Months / high
2	AIO / GEO citation optimisation — multiplier, not substitute	Medium	Trust	Months / low
2	Off-site corroboration / community distribution	Medium	Trust	Months / medium
2	BOFU / comparison / trust-gap pages	Medium	Traffic	Months / low
3	Vertical / local entity pages (embassies, VFS)	Low	Traffic	Months / high
3	Internationalisation / non-English corridors	Low	Traffic	Months / high
3	Head-term / hub-page ranking	Low	Traffic	Months / high

The milestone path — now, and what "done" looks like

Weeks 0–2 · Foundation sprint

Foundation & prune

Focus: prune the thin layer · ship schema across all 202 good pages · build the trust layer (HK entity, IDA disclosure, fee-vs-service fee, named reviewer, not-a-government notice, Trustpilot) · technical setup (segmented sitemaps, canonicals, depth, IndexNow) · instrumentation (GSC + rank tracking on the top 200 keywords, revenue-per-1000-sessions by page type).

Done when: indexable URL count ≤250 and matches sitemaps · ≥90% submitted URLs indexed · 100% money pages validate with zero schema errors · trust block live on every template · 14 days rank-tracking baseline.

Next: build the India corridor.

Weeks 3–12 · Month 1–3

Win the India corridor

Focus: ship 60–100 genuinely differentiated /for-indians/ tuple pages from the KD 0–11 pocket (start indonesia-for-indians 10k/KD1, then Australia, UAE, Thailand, Vietnam, Singapore, Malaysia). Each carries India-specific facts a competitor can't fake (INR fees, ECR/OCI notes, VFS cities, India processing times). In parallel: corridor internal linking, cannibalisation rules, driving-guide remediation in batches, the rule-change changelog, CRO on money pages.

Done when: first 1,000 monthly sessions · ≥50 keywords top 50 and ≥10 top 20 · ≥1 tuple page top 10 · ≥60 corridor pages live · ≥60 driving guides remediated and re-indexed · measured baseline conversion per page type.

Next: replicate the corridor to nationality #2 and #3, start earning authority.

Month 3–6

Replicate + start building authority

Focus: corridors #2/#3 chosen by proven revenue-per-session (not volume) · foundational citations (IDA, Trustpilot, Crunchbase, LinkedIn, HK registry, Wikidata) · build the proprietary Visa & IDP Requirements Index with methodology + Dataset schema · AIO/GEO becomes an explicit track now that pages rank · BOFU comparison + fee-transparency pages · start the monthly GSC prune-and-double-down cycle.

Done when: 5,000 monthly sessions · ≥25 keywords top 10 · ≥30 referring domains · Index asset live with first 5 unsolicited editorial links · first tracked AI citations · corridors #2/#3 ≥40 pages each.

Next: scale authority until domain rating stops being the constraint.

Month 6–12

Break the authority ceiling

Focus: digital PR off the Index (2–3 per quarter) · expert commentary · community presence (r/india, expat forums, Quora) · YouTube for visual queries · systematic AIO/GEO — rewrite pages that rank top-10 but are never cited · open KD up to ≤25 as authority rises · finish all 190 driving guides · begin a non-English corridor's plumbing.

Done when: domain rating 20–25, 100+ referring domains from ≥40 sites earned editorially · 20,000 monthly sessions · cited in AI answers for ≥50 tracked queries · branded search trending up · all driving guides indexed and passing the depth gate.

Next: expand surface area now that authority can carry it.

Month 12+

Expansion and defensibility

Focus: attack the hub head terms deliberately skipped · launch passport, apostille and civil-records verticals · a curated embassy/consulate/VFS entity set · Hindi and Arabic translation of corridors that already rank (human-reviewed) · moat maintenance — the changelog, the Index cadence, the freshness pipeline.

Done when: diversified revenue across ≥3 verticals · no single corridor more than 40% of organic revenue · the Index cited by third parties without outreach · incumbent-level rankings on a few hub head terms.

Next: defend freshness, defend the entity, keep the index clean as we scale.

AIWhere AI Overviews fits

Classic organic ranking is the mechanism; AIO citation is the yield. AI Overviews and chat assistants draw their citations overwhelmingly from pages that already rank in the top ~10, and from entities corroborated across the open web — a low-authority site with no rankings cannot be cited no matter how well-structured its markup is.

The free, dual-purpose GEO work (schema, extractable answer blocks, question-shaped headings, named sources, honest dates) happens in Phase 0. The genuinely GEO-specific work — citation tracking across AI Overviews/ChatGPT/Perplexity/Copilot, and off-site corroboration — starts in Phase 2 once we have rankings to be drawn from.

The risks, and how we avoid each

Scaled-content classification — the top existential risk. Avoid: a hard per-page uniqueness gate before indexing; ship in batches of 20–30 and watch indexation; keep named reviewers, sources and last-verified dates on every page.
Index bloat — 190 countries × documents × nationalities compounds fast. Avoid: treat indexation as a budget; cap the set per phase (≤250 now, ~400 by end of Phase 1); never auto-generate a URL for a keyword with no measured demand.
Cannibalisation — destination and tuple pages fight each other. Avoid: enforce separation in the template; distinct titles/H1s; self-referencing canonicals; monthly GSC audit for URL swapping.
YMYL trust gap — a Hong Kong lead-gen middleman in immigration. Avoid: over-disclose (entity, registration, IDA role, fee itemisation, refund policy, named reviewers, not-a-government notice); Trustpilot in Phase 0; own the "Is Expedify legit" answer.
Wasting effort on unwinnable head terms. Avoid: a written KD ceiling tied to authority (DR<10 → KD≤10; DR 10–20 → KD≤20; DR 20–30 → KD≤25); sort by volume/KD, not volume.
Template-wide regression — a bad change hits 190 pages at once. Avoid: canary on 10–20 pages, hold 14–21 days, compare against control, then roll out; version and date every change; keep a rollback.
Schema-content mismatch — a manual-action vector. Avoid: generate schema from the same data source that renders the visible page; validate in Rich Results Test; no review/aggregateRating markup on our own pages; represent variable fees as ranges.
Aggressive link buying on a young domain. Avoid: earn foundational citations first, then build only editorially (data asset, PR, commentary); no paid placements, no PBNs; cap velocity.
Duplicate / partner-derived content. Avoid: cite with links but write every requirement in our own structure and voice; add a layer no source has (processing-time observations, local-currency fees, denial patterns); don't be a near-duplicate of IDA's site.
Premature pivoting on noisy data. Avoid: set phase-complete thresholds in advance; evaluate corridors on a 90-day window; only a sitewide indexation/impressions collapse justifies immediate action.
Optimising for sessions instead of revenue. Avoid: instrument revenue per 1,000 sessions by page type and corridor from Phase 0; pick Phase 2 corridors on that metric alone.

The Complete SEO Plan — Ranked for a Newcomer, Milestone-Driven