interac.ca — AI Site Grade

Analysis

Interac.ca — AI-Visibility Audit

The site's most consequential gap is not technical blockage but a cold-knowledge mismatch: the LLM prior describes Interac as a "debit and e-transfer network" with no awareness of its expanding identity-verification business, yet the site positions verification as a co-equal pillar alongside payments, with 568 million verification transactions in 2024.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, Applebot-Extended, anthropic-ai — receive a full 200 response with identical byte-size content (357 KB) as a browser. No UA-based blocking, no JS shell, no Cloudflare challenge. The sole exception is Bytespider, which gets a 502 Bad Gateway from nginx — a backend routing failure, not a deliberate block. The robots.txt uses a single User-agent: * rule disallowing only /wp-admin/, search-query URLs, and /wp-content/plugins/. No AI-bot-specific directives exist. The llms.txt is present (generated by Yoast SEO v27.5) and lists ~80 URLs across pages, payments, verification, company, resources, and content sections — a strong signal for LLM consumption.

Cold-Knowledge Gap

Asked cold, the LLM describes Interac as a "Canadian financial services network" focused on Interac Debit, Interac e-Transfer, and Interac Flash (contactless). It mentions "over 1 billion transfers annually" and flags "e-Transfer phishing scams" as a reputational concern. The site itself tells a materially different story: Interac Verified (identity verification) is given equal billing in the primary navigation, with 568 million verification transactions in 2024 — a figure the LLM does not know. The site also promotes Interac Direct (card-free online payments via Konek), Interac e-Transfer Cards (digital greeting cards with money), and transit payments (TTC, BC Transit). None of these newer products appear in the cold knowledge. The LLM's prior is frozen at roughly 2022-era product awareness.

Schema Posture

Every page uses JSON-LD via Yoast with WebPage, BreadcrumbList, WebSite, and Organization types. The Organization schema includes sameAs links to Facebook, X, Instagram, LinkedIn, and YouTube. However, no product or service schema (Product, Service, FAQPage) is used anywhere — even on pages with extensive FAQ sections (the Interac Debit page has 8 FAQ items rendered as plain H3s). The WebSite schema includes SearchAction but no potentialAction for chatbot or voice-assistant interactions. The dateModified values are current (2026 dates), indicating active content maintenance.

External Signals

The site is hosted on WP Engine (nginx + WP Engine headers) with AWS DNS. DNS TXT records reveal integrations with Salesforce, Qualtrics, Atlassian, DocuSign, Dynatrace, Twilio, and Pardot — a sophisticated MarTech stack that suggests the brand invests heavily in customer experience but has not extended that investment to AI-crawl optimization. The innovation subdomain (innovation.interac.ca) hosts developer-facing API documentation for verification solutions, Business Request Money, and Interac Direct — content that would be highly valuable for LLM training but is siloed on a separate subdomain with its own schema and navigation.

Findings

1. LLM cold knowledge omits Interac's identity-verification business High

   The LLM prior describes Interac only as a debit and e-transfer network, missing its co-equal identity-verification pillar (568M transactions in 2024) and newer products like Interac Direct and e-Transfer Cards.

   What to change: Publish an llms.txt or llms-full.txt that explicitly lists all product pillars (payments, verification, transit) with descriptions and key statistics to seed LLM knowledge.

2. No product or FAQ schema on key pages Medium

   Despite extensive FAQ content on pages like Interac Debit and e-Transfer, no FAQPage or Product schema is used. This limits structured extraction by AI crawlers.

   What to change: Add FAQPage schema to pages with FAQ sections and Product or Service schema to product pages (e.g., Interac e-Transfer, Interac Debit).

3. Bytespider receives 502 Bad Gateway Medium

   The ByteDance crawler (Bytespider) gets a 502 error from nginx, likely a backend routing issue, preventing content indexing by that bot.

   What to change: Investigate and fix the nginx backend routing for Bytespider requests to return a 200 response.

4. Innovation subdomain siloes developer content Medium

   Developer-facing API documentation for verification and Interac Direct lives on innovation.interac.ca with separate schema and navigation, reducing its discoverability for AI crawlers.

   What to change: Consolidate key developer content under the main domain or add cross-links and sitemap entries to ensure AI crawlers discover innovation.interac.ca.

5. No AI-bot-specific robots.txt rules Low

   The robots.txt uses a single wildcard rule and does not explicitly allow or disallow AI crawlers, leaving them to default access but missing an opportunity to signal crawl priority.

   What to change: Add explicit allow rules for key AI crawlers (GPTBot, ClaudeBot, etc.) to signal crawl priority and prevent accidental blocking.

6. WebSite schema lacks chatbot potentialAction Low

   The WebSite schema includes SearchAction but no potentialAction for chatbot or voice-assistant interactions, missing an opportunity to guide AI agents.

   What to change: Add a potentialAction property for chatbot interactions (e.g., 'Ask about Interac products') to the WebSite schema.

What's working

• llms.txt file present with 80+ URLs — An llms.txt generated by Yoast SEO lists ~80 URLs across all site sections, providing a strong signal for LLM consumption.
• Major AI crawlers receive full 200 responses — GPTBot, ClaudeBot, PerplexityBot, and others get identical content as browsers, with no UA-based blocking or JS shells.
• JSON-LD schema present on all pages — Every page includes WebPage, BreadcrumbList, WebSite, and Organization schema via Yoast, with current dateModified values.
• Organization schema includes social sameAs links — The Organization schema lists Facebook, X, Instagram, LinkedIn, and YouTube profiles, aiding entity disambiguation.
• Content is actively maintained with 2026 dates — dateModified values are current (2026), indicating regular updates and fresh content for crawlers.
• robots.txt allows most content — Only /wp-admin/, search URLs, and /wp-content/plugins/ are disallowed; all product and content pages are crawlable.