Case Study: How InLinks & Waikay Drove a 650% Increase in AI Visibility | Waikay®
Case Study: How InLinks & Waikay Drove a 650% Increase in AI Visibility
4 December, 2025
Background: A hole found in AI understanding
At the beginning of the year, I spoke with an InLinks client about their long‑term goals. As a major online accounting software provider, they had already established dominance across several niches. One area they identified as a priority, however, was building greater visibility and authority-sites/ authority around the entity of “E‑invoicing.”
[...] (continues with the main content)
The Results: How Entity Frequency Skyrocketed
Entity frequency of each brand over the past 30 days
The story this tells is fantastic, and a huge learning point for SEOs. Ultimately, Brand A (first row) have dramatically improved an LLMs understanding of E-invoicing. They lead this entity, with 42 mentions of it in the past 30 days, over double their next closest competitor.
Let's take a look at this increase over the last few months:
Frequency of 'E-invoicing' entity mentions for Brand A found in response to prompt 'Best E-invoicing Software'
The number of times the entity “e‑invoicing” appeared in relation to the brand rose from 2 mentions at baseline to 15 at peak — a 650% increase.
Important: What increased was not (necessarily) how often the brand was named, but how often the entity ‘e‑invoicing’ was explicitly tied to the brand in LLM responses.
Brand A also improved in other entities as well, including Accounting and Automation “Automation”
Frequency of 'Accounting' entity mentions for Brand A found in response to prompt 'Best E-invoicing Software'
Frequency of 'Automation' Entity for Brand A found in response to prompt 'Best E-invoicing Software'
The heatmap and accompanying graphs illustrate a clear win for Brand A, which dominates in mentions tied directly to the entity of e‑invoicing. However, the picture is more nuanced when looking across competitors. Brand B and Brand C stand out in other areas — particularly around customizability and features — where they consistently outperform Brand A.
This breakdown begins to reveal how LLMs interpret and prioritize associations over time.
What This Means For AI Visibility Strategy
AI visibility is ultimately about positioning your brand closer to the right entities so it surfaces in more queries. You don’t need to track hundreds of prompts — a single, well‑chosen prompt can reveal enough direction to guide strategy for months.
What should Brand A do now?
Now that the gaps around e‑invoicing are clear, Waikay can step in to shape the next stage. The data highlights where expansion is needed, and from this we can build an actionable topic report. For Brand A, the recommendations are organized into three areas: new content that should be added, enhancements to existing material, and broader structural improvements informed by the insights we’ve collected.
Brand A Topic Report for E-invoicing
Content additions
High priority
Content Type: Pillar page plus interlinked regional guides (blog/guide format, not duplicating existing regional product pages)
Create a central, SEO‑optimized pillar page (e.g., /global/e-invoicing or /e-invoicing/guide) that:
- Explains what e‑invoicing is
- Compares it to traditional invoicing
- Outlines benefits (automation, faster payment, fewer errors)
- Explains PEPPOL/InvoiceNow and cross‑border networks
- Links out to existing regional e‑invoicing product pages (/au/e-invoicing, /nz/e-invoicing, /sg/e-invoicing, /my/accounting-software/e-invoicing, etc.)
- Summarizes mandatory e‑invoicing timelines by country with links into more detailed local guides or campaigns
- Surfaces existing media releases and blog posts as a ‘latest updates’ module
Developer ‑Facing e ‑Invoicing API and Integration Overview
High Priority
Content Type: Developer documentation overview page + supporting technical article series
Produce a public, indexable developer overview (on the developer portal, but SEO‑discoverable from the main site) titled along the lines of “Integrate e‑Invoicing with APIs.” It should:
- Explain supported e‑invoicing flows (send, receive, status updates)
- Outline how the platform works with PEPPOL/InvoiceNow and other networks at the API level
- Describe integration patterns with ERP or procurement systems
- Include code examples or diagrams
Follow up with 1–2 technical blog/guide articles per key use case (e.g., integrating e‑invoicing into an ERP, automating AP with e‑invoices).
Content Enhancement
High Priority
Existing Content: regional e‑invoicing product pages (AU, NZ, SG, MY, UK, US, etc.) and campaign pages
On each e‑invoicing product/initiative page, add sections that:
- Explicitly connect e‑invoicing to automated reminders, scheduled/recurring invoices, and invoice tracking (reusing language and features from existing invoicing pages)
- Highlight integration with online payments (e.g., Stripe) and how e‑invoicing accelerates cash collection and improves cash‑flow visibility
- Include concrete, quantified benefit statements where possible (e.g., reduced days to payment) and link to cash‑flow guides and calculators
- Briefly mention personalization/branding options available for e‑invoices and link to free invoice template resources where appropriate
Advisor and Industry ‑Specific e ‑Invoicing Positioning
Medium Priority
Existing Content: advisor portals, industry pages (construction, self‑employed, etc.), and accountant/bookkeeper guides
Add advisor‑ and industry‑specific e‑invoicing sections or sidebars that:
- Explain how accountants and bookkeepers can use e‑invoicing to streamline AR/AP for clients, improve accuracy, and prepare for mandatory regimes
- Position e‑invoicing as an advisory opportunity, with links back to the global e‑invoicing hub and “what is e‑invoicing” guide
Structural Improvements
High Priority
Create a clearly linked e‑invoicing topic cluster and navigation entry
- From main invoicing pages (e.g., //accounting-software/send-invoices/ and ‘explore invoicing software’ pages) and from payments/Stripe pricing pages, add consistent navigation and in‑content links to the e‑invoicing hub and regional e‑invoicing pages
- Implement a small e‑invoicing ‘module’ or banner within invoicing pages that explains in one sentence what e‑invoicing is and routes users to the hub
- This will consolidate topical authority and improve discovery
Medium Priority
Standardize regional e‑invoicing page structures and schema
- Align page structure across AU, NZ, SG, MY, US, and UK e‑invoicing pages: consistent H1/H2 patterns (What is e‑invoicing, How it works in [region], Benefits, Compliance, How to get started)
- Add FAQ sections addressing mandatory rules, PEPPOL/InvoiceNow, registration steps, and integration with existing invoicing features
- Implement appropriate FAQ schema to capture more SERP real estate
- Ensure each regional page links back to the global hub and relevant support/learning resources (e.g., ‘Register to receive e‑invoices’, ‘send and receive PEPPOL e‑invoices’, learning course for Malaysia)