SEO BrainFree · Built in Bahrain
Book a DemoLet’s Connect

Verified case study · faimglobal.com · 25 Oct 2026

What the audit found on our own website

This is FAIM's site, audited with the method on this hub. The numbers are dated tool observations, not current figures. We show them because we would rather show our own weak points than invent someone else's success.

9 min readAll levels80 XP quest
A crowd gathered at night in front of large illuminated screens
Photo: Freepik via Magnific (licensed stock)
168
sitemap URLs, all returning 200 [T]
0
test searches where FAIM appeared, from a US location [T]
3 / 0
form clicks vs stored submissions, 23 Oct [T]
19/47
posts under 650 stored words [T]

Lighthouse, mobile, best of two runs

Runs on the same page varied by up to 18 points. Real-user data needs Search Console. [T] 25 Oct 2026

What we did next

ChangeStatus
Commercial registration and VAT numbers added to the contact page and Organization schemaReported done, verify live
"Built with" links from nine case studies to their solution pagesReported done, verify live
Titles and descriptions retargeted; duplicate "event technology solutions" targeting reducedReported done, verify live
Search Console and Bing Webmaster Tools verificationOpen, needs DNS access
Arabic section (/ar/)Open, management decision

The lesson

We also found a mistake of our own: case studies looked thin because their text lives in a theme field, not the main content field. Counting rendered words, not stored words, fixed the reading. The skill now says so, which is the point of keeping a dated audit separate from stable rules.

No client results are claimed on this hub. Client projects are named on faimglobal.com only where FAIM shows them, and names in this skill are flagged as needing written permission.

BreakdownStep by step

  1. Where we started

    On 25 Oct 2026 faimglobal.com passed most technical checks but did not appear in any test search we ran, and the enquiry form was not reliable.

  2. What we fixed first

    Measurement, the form, one public name, schema identifiers and titles. Not new content.

  3. What we built next

    Solution pages with proof, case studies with real venues, a blog that links to the service each post supports.

  4. How we keep it honest

    A health check every four days with the same report layout, and a rule that every number carries its source.

Worked example

A dated before and after

Before: forms leaked and Search Console was not connected. After: every enquiry is stored and emailed at once, Search Console and Bing are connected, and a four-day check reports scores, leads and AI referrals. Ranking results are reported only when Search Console shows them.

TipsWhat works in practice

Write your own case study the same way: dated, sourced, including what did not work.
Keep before screenshots. You will want them.
Report the boring fixes; they usually mattered most.
Update the case study as numbers arrive instead of rewriting history.

AvoidCommon mistakes

  • Claiming results before the data exists.
  • Leaving out the mistakes.
  • Showing one good screenshot without the date or context.

Quest · Historian badge

Tell the true story

3 tasks + 1 question · 80 XP

What did FAIM fix before writing new content?

Why: Without measurement and a working form, new content could not be judged and would lose the enquiries it earned.

Historian badge unlockedChapter complete. Your progress is saved in this browser.