How World Mobile Token Rebuilt Schema and Authority to Survive a Google Update
Telecom blockchain project with 80+ anonymous blog posts, no source citations and Organization schema where Service should have been. The work paid off when March 2024's update hit competitors hard.
Client context
World Mobile Token is a telecommunications blockchain project building decentralized network infrastructure across underserved regions. The token (WMT) powers network operations, node staking and ecosystem participation. The team had real infrastructure on the ground, real partnerships in target regions and a real working product. What they had less of was online discoverability for the queries that mattered.
The site was a content-heavy WordPress installation with about 200 indexable pages: project overview, technology explainers, ecosystem partner listings, token information and a blog with about 80 posts published over two years. Page volume was solid. Page quality was uneven.
The token information page (the page covering tokenomics, supply, distribution and utility) was emitting generic Article schema. The chain overview page (covering the protocol architecture and node operator economics) was emitting Organization schema. Neither schema type matched the content well. The token page should have been Cryptocurrency. The chain page should have been Service with serviceType set appropriately.
The blog had a different problem. Every post attributed to either "World Mobile Team" or "WMT Editorial". No bylines, no bio pages, no credentials. Some posts cited external sources (academic papers on telecom infrastructure, World Bank reports on connectivity gaps, peer-reviewed papers on rural network economics). Most didn't. For a YMYL site (any token-adjacent project is YMYL), this combination of anonymous authors and uncited claims was a slow-burning trust signal problem.
The problem
Three issues, well-aligned with what we'd seen at Eidoo but with different specific manifestations.
The schema mismatch was the first problem. The chain page describing protocol architecture was running bare Organization schema, which was correct for the company entity but wrong for the page-level content. The page wasn't about the company; it was about the chain's service offering. Service schema with serviceType set to "Telecommunications Blockchain" would have been correct.
The token page was running Article schema. Article is for blog posts. The token page was a permanent reference page covering tokenomics, distribution and utility. Cryptocurrency schema with explicit currencyCode (WMT) plus FinancialProduct stacked alongside would have enabled rich result eligibility on token-specific queries.
The blog authorship situation was the second problem and the bigger long-term threat. About 80 posts attributed to anonymous "Editorial Team" bylines. The posts varied widely in quality. Some genuinely original analysis, some repackaged news. None of it was identifiable to a specific human with credentials. For YMYL content this is a major demote signal.
The lack of source citations was the third problem. Posts making claims about telecom infrastructure economics, regulatory environments and network deployment costs would assert numbers without linking to any source. Some claims were straight from World Bank or ITU data. Some were from internal modelling. Some were unclear in origin. Without inline citations, readers (and Google's helpful content systems) had no way to assess credibility.
The combination created a YMYL trust score that was much lower than the actual quality of the underlying work justified.
The audit
Audit ran two weeks. The output was a 32-item issue list with the schema work and the authorship rebuild as the two largest projects.
We mapped the schema fixes per template. The chain page got Service schema with serviceType, areaServed listing the regions of operation, provider pointing to the company entity; offers describe the node operator economics. The token page got Cryptocurrency schema with currencyCode, currentExchangeRate (pulled from an oracle and refreshed via ISR), totalSupply and circulatingSupply. We stacked FinancialProduct on the token page for queries seeking the financial-product framing. BreadcrumbList went on every page.
The authorship rebuild was the more time-consuming work stream. We worked with World Mobile's team to identify actual writers for each post. About 60 of 80 posts had identifiable authors still at the company or willing to be associated retroactively. The remaining 20 we either consolidated under a named editorial lead with appropriate caveat or, in a few cases, retired entirely because the content was outdated.
The citation work ran in parallel. We went through every post making factual claims about telecom infrastructure, network economics and regulatory frameworks. Claims got matched to original sources where possible (World Bank, ITU, Hermès reports). Claims that couldn't be sourced were either reframed as analysis (with the framing made explicit) or removed.
FREE WEB3 AUDIT
Get the same audit type for your site.
Run the same Crawlux audit on your crypto domain. Free first audit, full PDF report.
Free first audit · No signup · 60 seconds · Full PDF report
The work
Schema migration: chain page and token page
The chain page got Service schema. serviceType: "Telecommunications Blockchain". provider: the World Mobile Group entity. areaServed: countries where node infrastructure operates. offers: high-level summary of node operator economics. We stacked Organization schema for the company entity in the same @graph using @id references to keep things clean.
The token page got Cryptocurrency schema as the primary type. currencyCode: WMT. currentExchangeRate updated hourly via ISR pulled from CoinGecko. totalSupply and circulatingSupply pulled from on-chain. We added FinancialProduct as a secondary type to capture the broader financial framing for queries seeking that perspective.
Both pages got BreadcrumbList. The token page got FAQPage with Speakable for the tokenomics questions. Validation across Schema.org Validator, Google Rich Results Test and Bing Markup Validator passed clean within the second iteration.
Author attribution across 80+ blog posts
Worked through the back catalogue post-by-post. For each, identified the actual author through interviews with current and former staff, internal documentation review and content style analysis. About 60 posts got attributed to specific named individuals. The remaining 20 either got attributed to a named editorial lead with appropriate context or got retired.
Built bio pages for the eight most-frequent authors. Each bio page emits Person schema with credentials, sameAs links to LinkedIn and Twitter, jobTitle, worksFor. Bio pages went live in /authors/{slug}/ structure with linked posts.
Updated each post's byline and Article schema author field to the named person. Where posts had multiple contributors, used the contributor field for additional attribution alongside the primary author.
Inline citation work
Reviewed every post making factual claims about telecom infrastructure, network economics and regulatory frameworks. Built a citation library covering: World Bank Digital Economy reports, ITU Connectivity Targets, GSMA Mobile Economy reports, peer-reviewed academic papers on rural network economics, regulatory filings in target jurisdictions.
For each factual claim, matched to a source citation if possible. Added inline links to the source. Where multiple sources supported a claim, linked to the most authoritative.
Claims that couldn't be matched to a source got either reframed (e.g., "our internal modelling suggests" instead of stating as fact) or removed entirely. About 40 posts received some level of citation work; about 15 had substantial revisions.
Updated post Article schema with citation property pointing to authoritative sources where applicable. This signals to AI engines that the post is sourced and verifiable.
Token page hub strategy
Built /token/ as a dedicated hub covering tokenomics, distribution, utility, staking and node operations. Sub-pages for each: /token/tokenomics/, /token/staking/, /token/node-economics/. Each sub-page emits the appropriate schema (Cryptocurrency, FinancialProduct, FAQPage with Speakable).
The hub strategy gave AI engines a clear destination for token-specific queries. "WMT staking returns", "WMT node operator economics", "World Mobile Token utility" all started landing on the right sub-pages with the right schema rather than getting funneled through the homepage.
Internal linking from blog posts to relevant /token/ sub-pages strengthened the architecture. Posts about network deployment cite the node economics page; posts about regional rollouts cite the relevant token utility pages.
Results
The token-specific query work showed up first. "WMT chain" queries moved from page 4 to page 1 within 8 weeks. Token-related queries ("World Mobile Token utility", "WMT staking", "WMT tokenomics") all started ranking on page 1 within a similar window.
The YMYL trust score work paid off most clearly during March 2024's spam and helpful content update. Multiple competitor sites with similar profiles (anonymous bylines, uncited claims, weak schema) saw substantial traffic drops in the weeks following the update. World Mobile Token's organic traffic was stable through the update with modest gains continuing.
This was the most defensive of the four engagements. The schema work added rankings. The authorship work and citation work largely added insulation against algorithm volatility. We measured the improvement differently because the comparison wasn't before-vs-after on the same site; it was World Mobile Token vs other crypto projects of similar profile that did not invest in YMYL signal building.
AEO citation rate improved substantially over 90 days. ChatGPT and Perplexity both started citing the project for telecom blockchain queries where they had previously cited generic crypto coverage instead of the project itself.
5 tactical lessons you can apply
Service schema with serviceType beats Organization on protocol pages
Organization is correct for the company entity but wrong for the page-level content describing what the protocol does. Service with serviceType set to a specific descriptor ("Telecommunications Blockchain" in this case) is the right type for protocol-architecture pages. The distinction matters for AI engine retrieval.
Cryptocurrency schema needs FinancialProduct stacked alongside
Cryptocurrency schema captures the token-as-asset framing. FinancialProduct captures the broader financial-product framing. Different queries seek different framings. Stacking both via @graph captures both query intents from a single page.
Citation work is non-negotiable for YMYL crypto content
Anonymous bylines plus uncited claims is a slow-burning trust collapse. Algorithm updates increasingly target this combination. Build the citation library proactively. Match every factual claim to a source. Reframe or remove claims that can't be sourced. The cost is editorial bandwidth; the benefit is algorithm insulation.
Pilot citation work on 10 posts before scaling to 80
We did the full catalogue at once and consumed substantial editorial bandwidth. A 10-post pilot would have refined the citation library and the editorial process before scaling. For large content rewrites, always pilot before scaling. The pilot cost is small; the process improvements compound.
Defensive SEO work is hard to attribute but real
The work we did at WMT didn't produce a headline traffic chart. What it produced was stability through an algorithm update that hit competitors hard. You can't cleanly attribute defensive lifts the way you can attribute offensive ones. But the next competitor hit by the next update is the proof.
AB's takeaway
The World Mobile Token engagement was the most YMYL-focused of the four. OVR was about rendering and schema. Eidoo was about schema and authority. Magic Square was about CWV and schema. World Mobile Token was about authority and citations on a YMYL site exposed to algorithm risk.
Defensive SEO work doesn't produce headline numbers easily. You can't cleanly say "the citation work caused this lift" the way you can with a CWV fix. What you can say is that competitor sites which didn't do this work got hit by the spring 2024 updates while clients who did weren't.
For projects in the long-tail of crypto (smaller market cap, less brand recognition, more dependence on organic discovery), the YMYL signal investment is non-negotiable. Algorithms keep getting harsher on uncited claims and anonymous YMYL content. Build the authority graph or accept that you're structurally exposed to the next update.
What we'd do differently
Two things.
First, we'd have started the citation work on a smaller pilot of 10 posts before scaling to all 80. Doing it across the full catalogue at once consumed substantial editorial bandwidth. A pilot would have let us refine the citation library and the editorial process before scaling, probably saving 20-30% of the total time investment.
Second, we'd have built the /authors/ hub structure earlier. We launched it after most of the post-level attribution had been completed, which meant some early-attribution posts shipped before the linked author bios existed. A reader clicking the byline in the first batch of updated posts would have hit a 404 for a few days. Sequencing the hub first would have prevented this minor but avoidable issue.
We weren't expecting much during the spring algorithm update because we'd watched competitors get crushed. The schema and authorship work TG3 had completed kept us stable while others lost half their traffic. That insulation alone justified the engagement.
Run a free Crawlux audit on your site
The audit identifies which schema, technical and AEO issues are blocking your rankings. Same diagnostic framework we used at World Mobile Token.
Run free audit →Related playbooks
Pillar guides
RUN YOUR OWN AUDIT
See what Crawlux finds on your site.
These results came from the same audit you can run for free on your own domain. 60-second turnaround.
Free first audit · No signup · 60 seconds · Full PDF report