In force · active agreements
247 FTAs
countries · sectors · sub-national hubs · trade bodies · FTAs · tools · academy · essays
Trade blocs & corridors
FTAs don't exist in isolation — they connect through blocs and trade corridors. Jump to the relevant bloc or corridor view to see all member FTAs at once.
FTA-eligible mandate?
We structure mandates for the FTA preference you actually qualify for.
Run the savings estimator first, then submit — we'll confirm RoO qualification, COO path, and commission structure within 48 hours.
Totality lens · 32 points to ponder · 16 user POV + 16 developer POV · this hub
User POV — for the practitioner navigating the Ftas hub
Eight dimensions
A practitioner can in principle navigate the full universe of bilateral and plurilateral trade agreements affecting 197 countries — 273 FTAs spanning the WTO membership plus regional accords (RCEP, AfCFTA, USMCA, CPTPP, EU association agreements, all India CEPAs and CECAs, GCC accords, ASEAN+1 frameworks). The hub is structured so any user can find the FTA(s) governing their specific trade lane within two clicks: pick origin, pick destination, see the agreement(s).
In practice, most users care about three to five FTAs at once — typically their home-country agreements with their main export markets. The 273-FTA breadth is a comprehensive-coverage commitment for SEO and credibility, but the conversion path narrows to the top-20 high-volume FTAs (India-EU 2026, India-UAE CEPA, India-Australia ECTA, RCEP, USMCA, EU-Mercosur, AfCFTA intra-Africa, etc) which together carry 80-plus percent of the hub traffic.
Inbound traffic resolves cleanly to specific FTA pages 70-80 percent of the time via search; the remainder lands on the hub directly and either filters by region (40 percent of those) or scrolls the full alphabetical list (30 percent) before drilling. Conversion to the FTA Savings Estimator tool runs at 1.2-1.8 percent of FTA-page sessions in the v149 cohort, which is the highest tool-conversion rate on the site.
What works: a hub that surfaces the in-force-date prominently per FTA (recency triggers click-through), a per-FTA page that opens with the duty-elimination schedule (the single most-asked question), tariff-line tables collapsed by HS chapter so the page loads under 100KB, and a Rules of Origin block that links to the RoO calculator tool. Cross-links into the relevant blocs and corridors fire on every FTA page.
What does not work: surfacing the full agreement text inline (90KB+ pre-gzip kills mobile, and the text is rarely useful at first encounter), country-flag-only navigation (poor for accessibility, slow to scan with 273 entries), and pretending agreements have a single 'tariff rate' when in reality they are HS-line-by-HS-line schedules. Earlier iterations that hid the schedule complexity got bounce rates above 70 percent; the current design surfaces it.
The common pitfall is treating an FTA as binary (in force / not in force) when in reality every agreement has phase-in periods, sensitive lists, exclusions, and origin-stacking rules. The hub mitigates by including the in-force-date plus a phase-in-status field per HS chapter; the per-FTA page surfaces this as a timeline. Users who skip the timeline read often miss that pharma is Day-1 zero but textiles are Year-10.
Counter-intuitively, the highest-traffic FTAs are not always the highest-conversion. India-Singapore CECA gets fewer hub-impressions than India-EU but converts at twice the rate — because the audience is sharper (Singapore-routed Indian exporters specifically). The hub spotlight band rotates the high-conversion mid-traffic FTAs forward to surface them above the dominant-but-shallow head.
The single highest-leverage move is to deepen the top-10 FTAs at 32-point TOTALITY (planned for v154 ECHO) — these handle 80 percent of trade-flow analytics. The second is per-FTA tariff-line search (in scope for v152) where users can paste an HS code and get the prevailing duty rate across all 273 agreements at once. The third is FTA Savings Estimator integration directly inline on each FTA page.
Eight user intents
Exporters scoping preferential-rate eligibility, importers calculating landed cost with FTA savings, customs brokers verifying RoO compliance, trade lawyers drafting commercial contracts, treasury teams modelling currency + duty exposure, mandate brokers (the AJG bread-and-butter audience) sizing commission opportunities. The most engaged segment is the SME exporter doing first-time-FTA research for a specific HS code.
The irreducible essence: every active trade agreement, surfaced with its in-force date, parties, duty-elimination schedule by HS chapter, RoO requirements, and links to the calculator tools that turn schedules into landed-cost numbers. The hub is the shortest path from 'is there an FTA covering my lane' to 'this is the duty I will actually pay after RoO and CBAM'.
Best entered at the pre-quotation stage of a deal (before locking pricing) and again at the contract stage (to verify RoO mechanics on the specific shipment). Re-entry annually is essential for FTAs in active phase-in (most India FTAs through 2030, AfCFTA through 2035) because the prevailing rate changes year-on-year. The hub displays the year-N rate for every phase-in tariff line.
Hub is global; weights by AJG focus markets — India FTAs get deepest treatment (15 currently in force or under negotiation), EU agreements next (40-plus association and trade accords), then the major regional pacts (RCEP, USMCA, CPTPP, AfCFTA). Smaller bilaterals get coverage but with sparser depth. Filter by region or by partner-country to bias the listing.
FTAs are misunderstood as legal documents read by lawyers. They are operating instruments read by exporters, customs brokers, and treasury teams. Most public FTA references either over-legalise (full text, no calculation tools) or over-simplify (single duty rate, no schedule). The hub gives both surfaces: schedule-grade detail plus practitioner-grade calculation, on the same page.
For first-time FTA users the highest-leverage sub-paths are: (a) start with origin and destination filters to find applicable agreements; (b) check the in-force date and phase-in year for the relevant HS chapter; (c) run the FTA Savings Estimator to convert preferential rate to USD savings; (d) verify RoO via the Rules of Origin tool; (e) cross-link to the landed-cost calculator for an end-to-end number.
Trust: WTO RTA database (the canonical FTA registry), India's DGFT for India-side notifications, the European Commission DG Trade for EU-side, the UNCTAD FTA portal for plurilateral context. Discount: trade-promotion-agency summaries (often selective), industry-association 'fact-sheets' (advocacy-tinted), and any source that quotes a single duty rate without the HS code or year.
Proceed by listing your origin, destination, and primary HS chapters; cross-reference against the hub filter to identify candidate agreements; drop into the top-three FTA pages to read the schedule for your chapters; run the FTA Savings Estimator on the leading agreement; verify RoO; finalise the landed-cost calculation. Document the agreement-version-and-year you relied on (FTAs change).
Developer POV — for the architect, maintainer, future contributor to this hub
Eight dev dimensions
FTAs hub composes from data/ftas-data.php (273-FTA registry: parties, in-force, HS-chapter schedule, RoO summary, sources), data/ftas-tariff-lines.php (per-line duty schedules where published, HS-6 granularity), data/ftas-roo-data.php (RoO rules per FTA per chapter). Helpers: ajg_ftas_all(), ajg_fta_by_slug(), ajg_fta_for_hs(), ajg_fta_savings_for(). Single-file render via ftas.php hub at root, per-FTA pages routed through the FTA template under the front-controller. Zero database, zero runtime API.
CollectionPage on the hub with ItemList of FTAs; each FTA page emits Article + Dataset + Government schema (LegalEntity for the parties + GovernmentService for the agreement). BreadcrumbList walks Home → FTAs → {Region} → {FTA}. The duty-elimination schedule is rendered as Table schema; the RoO block as DefinedTerm. FAQPage answers 'when does this FTA enter into force', 'what is the RoO threshold', 'how do I claim preferential rate'.
Forward to /tools/fta-savings-estimator.php, /tools/rules-of-origin.php, /tools/landed-cost-calculator.php. Outward to the parties' country pages, the relevant blocs, the affected corridors, and the verticals most exposed to the agreement (pharma for India-EU, auto for India-Australia ECTA, etc). Cross-content injector pulls Library + ScopeScape on tokens 'tariff', 'preferential', 'origin', 'cumulation'. Link weaver hyperlinks all 273 FTA names site-wide.
Hub renders <60ms server-side at p95. Per-FTA page <90ms because the schedule table is the heaviest element (deferred rendering for HS chapters beyond chapter 1-3 via collapsed details). Critical CSS inlined; design-tokens.css deferred. HTML payload <80KB pre-gzip for the hub, <120KB for a deep FTA page. Lighthouse Performance 96+ on mobile, 99+ on desktop as of v150.1.
Hub list collapses to single column at <640px with sticky filter pills. Each FTA card is a 48-px tap target. Per-FTA schedule tables become horizontal-scroll within a contained box rather than reflow (because the column structure is essential for reading). The 32-point TOTALITY block uses the same single-column reflow pattern as cities. RoO block collapses to a summary with expand-on-tap.
AAA contrast on body, AA on tariff-line numerics (the only AA exception, justified by table-density). All filter controls aria-labelled. Schedule tables use proper thead/tbody, scope=col on headers, and caption tags describing the FTA. Skip-to-content link present. Focus rings visible at 3-px width. Numeric duty rates respect the user's locale-formatting preferences via Intl.NumberFormat in the inline JS.
Every FTA URL emits unique title (FTA name + year), meta-description (parties + in-force + key chapter), canonical, OG + Twitter, JSON-LD per schema_markup, dateModified, and 1,500-word minimum body anchored to the schedule. Hub canonical at /ftas/. Sitemap entries in sitemap-ftas.xml (273 URLs). Per SO #2 data-anchored SEO.
Adding a new FTA requires: append entry to data/ftas-data.php with the 12-field standard schema; add tariff lines to data/ftas-tariff-lines.php if published; the hub picks it up automatically. Adding a new field across all FTAs requires template touch + data-migration. Adding a new RoO calculation method requires extension of /tools/rules-of-origin.php logic (currently supports change-in-tariff-classification, regional-value-content, and product-specific rules).
Eight dev intents
Maintained by the AJG principals plus admin/freshness.php cron for in-force-date and phase-in-year refresh. Annual refresh in January each year captures phase-in changes. Future contributors must understand the FTAs vs blocs vs corridors taxonomy: FTAs are agreements, blocs are member-clubs, corridors are physical routes. They cross-reference but they are not the same entity-type.
For the architect: the FTAs hub is the canonical authority on every preferential trade arrangement affecting AJG's market scope. Architecturally committed: per SO #33 every FTA-name reference site-wide must resolve; per SO #14 zero runtime API for tariff-line lookups (all data is in the static files). Maintained at <100KB pre-gzip on the hub. The 32-point TOTALITY block fires on /ftas/ as a hub-level evaluator surface.
Refresh cadence: annual (January) for phase-in years; ad-hoc when a new FTA enters into force; monthly via admin/monthly-update.php for dateModified-only refresh. Sitemap regenerates on every data-file change. The 32-point TOTALITY block is added at v151 BRAVO; v154 ECHO will deepen the top-10 FTA pillars at 32-point depth as well.
Files: ftas.php (hub root), data/ftas-data.php (registry), data/ftas-tariff-lines.php (HS-line schedules), data/ftas-roo-data.php (RoO), includes/totality-hubs-block.php (32-point block, BRAVO), data/totality-hubs-32point.php (block content). Tools: /tools/fta-savings-estimator.php, /tools/rules-of-origin.php. Sitemap: sitemap-ftas.xml.
FTAs is the second-most-trafficked Tier-1 hub after cities; deepening it at 32-point TOTALITY signals reference-grade authority on a topic where most public sources are either lawyer-flavoured or marketing-flavoured. The hub-level TOTALITY block (this one) gives evaluators a quick 'should I trust this hub' read; the per-FTA pages will get their own TOTALITY treatment in ECHO.
Highest-leverage extension: HS-line search at the hub level (paste an HS-6 code, see the rate across all 273 agreements). Second: integration of the FTA Savings Estimator inline on each FTA page. Third: visual phase-in timeline per FTA (currently text-only; D3 timeline would help). Fourth: RoO-stacking calculation across multiple FTAs (rare but high-value for complex supply chains).
Authoritative for FTA lists: WTO RTA database. For India-side: DGFT. For EU-side: DG Trade. For dispute resolution: WTO DSB. Defer to these for canonical text. AJG's value-add is the practitioner overlay: the schedule made operational, the RoO made calculable, the FTA cross-linked to the actual trade lanes and verticals it affects.
Proceed by checking docs/ROADMAP-v138-v200.md for FTA-related batches, reviewing admin/coverage-tree.php for current state, then editing data/ftas-data.php for content changes. New FTAs: add the registry row first, then schedule, then RoO; the hub picks it up automatically. Always run the smoke test (admin/audit-100.php?key=ajg-audit-2026) before shipping. Never skip sitemap regeneration on FTA additions.
v207.1 cross-Crucible synthesis · FTAs
FTAs aren't just tariff schedules — they're cross-Crucible decisions. A Free Trade Agreement between two jurisdictions ripples through visa categories (investor pathways, intra-company transfers, professional-services mobility), incorporation strategy (where to base for FTA-network access), landed cost (preferential tariff savings stack with Rules of Origin compliance costs), and macro-economic positioning (member states gain GDP-growth correlations, currency-stability spillovers, FDI-attraction tailwinds). The 273 active FTAs as tracked at v206.6 are the framework's most under-leveraged cross-cutting variable: most cross-border decision-makers consider visa OR business OR cost in isolation when the FTA layer compounds all three.
Sources: WTO Regional Trade Agreements Database (273 RTAs in force as of Q1 2026) · World Bank International Comparison Program PPP 2024 · OECD Trade Statistics + Trade Facilitation Indicators 2025 · IMF Direction of Trade Statistics (DOTS) · UNCTAD Handbook of Statistics 2025 · ASEAN Secretariat 2025 · EU Commission DG Trade · MFAT/CPTPP Secretariat 2025 · India Ministry of Commerce CEPA portal · AfCFTA Secretariat
Explore
Every page in the AJG platform cross-links to these primary entities. Click any pill to explore that branch of the knowledge graph.