Informational article
Custodial vs. non-custodial wallets — where does liability sit?
In preparation
Link Building for Crypto
We combine 46 financial and 62 technology portals only after establishing whether we are communicating an authorised CASP service, a crypto asset, or blockchain infrastructure. Each type receives separate sources and dedicated landing pages.
108
financial and tech portals
2
communication paths
12 mo.
indexation monitoring
Finance & Technology
Technology portal
MiCAService scopeEU
Publication topic
How to verify a crypto-asset service provider in the ESMA register
Reference articlecrypto-brand.eu/status
Portal database
Financial portals for services, technology portals for infrastructure
We use 46 financial portals for client-facing processes, fees, custody, and risk. 62 technology portals cover protocol, integration, API, and code. We do not publish identical content across both categories.
46
finance & insurance sites
62
IT & technology sites
2
communication paths
12 mo.
indexation monitoring
Portal selection criteria
- 01
Entity role
We establish whether the client is a CASP, an issuer, a technology provider, a protocol developer, or another participant. Content does not conflate these roles.
- 02
Current regulatory source
For EU-facing services, we verify the ESMA register entry provided by the client and the scope of services it covers.
- 03
Financial or technical audience
We select portals based on the dominant question. Developer documentation does not belong in content framed as an investment guide.
- 04
Evidence with a defined scope
We describe white papers, audits, and authorisations in line with their actual scope, version, author, and associated responsibilities.
- 05
Publisher policy and domain profile
We confirm crypto publication eligibility before outreach. Only then do we assess traffic, link profile, and pricing.
We never select portals based on a single metric alone.
Collaboration paths
Are you building visibility for crypto service users verifying a provider, or for developers evaluating blockchain infrastructure?
A service provider and an infrastructure builder may operate within the same ecosystem, but they should not share the same messaging. We separate entity status from code properties and from the underlying asset.
Path 01
Crypto-asset service
- Who it's for
- A client who wants to verify the provider, the scope of services, the custody model, fees, risks, and how to get support.
- What you gain
- Does the entity hold a valid MiCA authorisation, which services does the register entry cover, who holds the assets and keys, where are the fees listed, and how does a complaint or transfer work.
- Link destination
- A specific service page linked to the entity's details, authorisation information, fees, risk disclosures, terms of service, and contact.
- Materials
- Legal name, LEI or other identifiers, ESMA register entry, scope of authorised services, markets served, fees, custody model, terms and conditions, risk disclosures, and compliance onboarding process.
- Editorial boundary
- Content does not present an authorisation as a guarantee of asset value or investment safety, and does not extend the authorisation's scope to services not covered by the register entry.
Sample topics
- How to verify a crypto-asset service provider in the ESMA register
- Where to find service scope and fee schedules for a crypto platform
- Who holds the keys in a custodial crypto service?
Path 02
Blockchain technology and infrastructure
- Who it's for
- A developer, product manager, or business partner evaluating a protocol, wallet, smart contract, API, or integration tool.
- What you gain
- What problem does the technology solve, which components does the documentation cover, who controls the keys and updates, what does the audit scope include, and how does integration work.
- Link destination
- Technical documentation, repository, architecture overview, security centre, audit report, or a B2B integration page.
- Materials
- Architecture, documentation, governance model, dependencies, audit scope, code versions, repositories, known limitations, update process, and the client's legal classification of their activity.
- Editorial boundary
- The article does not describe a project as secure solely because an audit covered a selected portion of the code, and does not present a white paper as regulatory approval of the technology or the asset.
Sample topics
- What a smart contract audit covers — and what it does not confirm
- How to describe a key custody model in a wallet product
- What information is needed before integrating a blockchain API?
Packages
How many links do you need?
We define scope after auditing your services, audiences, source documents, and landing pages. A higher publication count makes sense only when the project has more than one genuine information problem to solve.
Single service or technology
10publications
A first campaign for a specific CASP service or a single technology product with complete source documentation.
- Entity brief and evidence register
- One consistent target audience
- Report and 12 months of monitoring
Lower unit cost
Pricing after portal selection
Service and infrastructure
20publications
Two separate paths — one for service users and one for a technology audience.
- Financial and technology portals with distinct topic clusters
- Links to both the product and the documentation
- Staged compliance approval
Lower unit cost
Pricing after portal selection
Product ecosystem
30publications
A plan covering multiple services, components, audiences, or markets — without extending a single authorisation across the entire project.
- Entity, service, and document matrix
- Separation of financial and technology content
- Publication order aligned with source readiness
Lower unit cost
Pricing after portal selection
How it works
How we work together
- 1
Send your brief
Tell us about the site, niche, target market and campaign goal. We'll use that to scope the work.
- 2
Site selection & pricing
We match sites to your topic, audience and budget, then send a proposal for your approval.
- 3
Content & approval
You can supply a ready article or ask us to write one — either way you sign it off before we publish.
- 4
Publication & monitoring
Once approved, we publish and start monitoring indexation.
What's included
What you receive after each publication
Before publication we create an entity, source, and claims brief. After delivery we hand over the published URLs and begin indexation monitoring.
Entity, service, and market brief
We record the client's role, markets, service scope, register entry, and authorisation scope — or the technology project's classification. The client confirms both the data and the legal assessment.Source and limitations register
Every claim about a service, asset, code, or security is assigned a source, version, and scope. A claim without supporting evidence is removed.Question and landing page map
We separate service users from technology audiences. Every question leads to a current product page, register entry, documentation, or report.Content, approval, and indexation monitoring
The client reviews the proposed topic and portal before production begins. The finished article goes through compliance and editorial review. After publication we deliver the URL and monitor indexation for 12 months.
See if we're the right fit
Send a brief for one client — we'll come back with a portal proposal, role breakdown, and a rough timeline.
Important for this industry
What we do not link without a confirmed MiCA authorisation, a defined entity role, and a source for every claim
- We do not link crypto services to EU clients without a confirmed MiCA authorisation and the corresponding service scope in the ESMA register.
- We do not treat a legacy national VASP register entry as a current CASP authorisation.
- We do not extend a code audit or a single entity's authorisation to an entire asset, protocol, or network of partners.
- We do not publish price forecasts, trading signals, promises of guaranteed returns, or claims of absolute security.
Jak pracujemy
Financial portals and technology portals are not interchangeable — the entity's role determines the link-building path
CASP entities and technology projects go to different portals — the entity's role determines the portal group
An authorised crypto-asset service provider builds visibility through financial portals, where users go to verify a provider. Infrastructure projects and developers belong on technology portals. These two groups do not overlap — we do not select portals without first establishing the client's role.
A MiCA licence is the entry requirement for a service campaign — not one document among many
An article about a CASP service on a financial portal links to a landing page that must confirm a valid authorisation. Before selecting a portal, we verify the client's ESMA register entry and the scope of services it covers. A legacy VASP registration does not substitute for MiCA authorisation.
46 financial portals and 62 technology portals: content determines which set applies
Financial portals work for services, fees, asset custody, and client risk. Technology portals fit protocols, APIs, smart contracts, and documentation. We do not publish identical material across both categories — the audience and the underlying question determine the correct portal set.
A white paper and a code audit are evidence with a defined scope — the portal repeats only what we state
A financial or technology portal republishes the claims made in the article. An article can only describe what the documents actually confirm — a white paper is not a regulatory approval, and an audit does not cover the entire project. We verify the scope of every piece of evidence before selecting a portal.
Authorised CASPsWalletsBlockchain protocolsWeb3 infrastructure
FAQ
Frequently Asked Questions
Answers covering MiCA authorisation, the ESMA register, white papers, code audits, technology content, and campaigns for crypto-asset services.
We can work with authorised crypto-asset service providers, issuers, and technology projects once we have established their precise role, market, and scope of activity. A general description of "blockchain project" is not sufficient for qualification.
No. Following the end of the MiCA transitional period, a historical entry in a national Virtual Currency Business Register does not authorise the provision of CASP services. Clients serving EU users need a valid MiCA authorisation.
The client provides the entity's details and their current ESMA register entry. We cross-reference the legal name, identifiers, country, and service scope against the planned article's claims. The client confirms the legal accuracy and currency of the information.
No. ESMA states explicitly that white papers appearing in the register have not been reviewed or approved by any competent authority. Responsibility for their content rests with the named offeror or issuer.
Yes, provided we receive the audit report, the version of the code reviewed, the scope of the engagement, the date, and its stated limitations. The article explains what the audit covered — it does not convert the report into a security guarantee for the entire project.
Financial portals suit services, fees, custody, transfers, and client risk. Technology portals are the right choice for architecture, protocols, APIs, integrations, and code audits. When a topic straddles both, the dominant audience determines the placement.
No. We do not produce forecasts, trading signals, return promises, or rankings designed to drive asset purchases. Our content covers verifiable service features and technology characteristics.
Depending on the path: ESMA register entry, service scope, terms and conditions, fee schedules, custody model, and risk disclosures — or technical documentation, repositories, architecture overview, audit reports, and the update process. Every piece of material must have an owner and a version.
We monitor each publication for 12 months. If it does not index within 60 days, or drops from the index during that period, we source a comparable portal at no additional cost — the replacement site also goes through our qualification process.
No. They can build a verifiable information footprint for your entity, services, and technology — but they do not guarantee Google rankings, citations by AI systems, client acquisition, or asset value.
Last updated: July 2026
Next step
Do you have a crypto service or technology project with complete source documentation?
Send us your entity role, target market, service scope, register entry, documentation, and landing pages. Once qualified, we will prepare a portal map and topic matrix.
108financial and tech portals
2communication paths
12 mo.indexation monitoring
See also