Step 03 of 05 — Build
A governance position documented. Infrastructure that makes you identifiable, not just accessible. Monetisation rails that are already live. Three layers. In this order.
GOVERNANCE
You have made a decision. Now it needs to exist somewhere other than a meeting. Governance is the work of turning a position into a documented, enforceable, technically implemented stance — one that holds when the CTO changes, the CMS is upgraded, or the EU AI Act auditor arrives.
Where do you stand on AI governance? We score your domain against the same framework that produced the global average of 4.4 out of 100 — and show you exactly what moves the number.
Three files. Each one says something different to AI systems. We audit your current configuration, draft the declaration that matches your decided position, and implement it. Most publishers have a policy they didn't choose — we replace it with one they did.
Which AI platforms are crawling you now? What are they finding? What are they saying about you when someone asks? We map your current AI visibility and flag the gaps between what you intend and what is happening.
A blocking policy in robots.txt is a technical instruction. A compliance record is an institutional decision. We produce the documentation that makes your AI governance position auditable, defensible, and communicable at board level.
INFRASTRUCTURE
An AI system that can reach your content still needs to understand it. Infrastructure is the work of making your site readable not just to humans but to the AI systems that are now a primary audience. Without it, you can be open and still be invisible.
Organisation, author, article, editorial policy — the JSON-LD that tells AI systems who you are and what your content covers. We implement the schema, test it against the signals that matter to AI citation, and make your site identifiable rather than just accessible.
Most CMSs were configured before AI was a consideration. We audit your current setup, identify the settings that are quietly blocking the wrong things or exposing the wrong things, and adjust the configuration to match your position.
AI traffic does not look like display traffic. We review how your current adtech stack responds to AI crawler visits and identify where the infrastructure is working against your monetisation position.
A structured review of every technical signal that affects your AI visibility: crawlability, structured data coverage, authorship signals, editorial policy pages, load performance for bots. You get a scored report — not a list of issues, but a prioritised build order.
MONETIZATION
Under 5% of publishers are currently positioned to earn from AI traffic. The first generation of licensing infrastructure is live — Tollbit, Cloudflare Pay Per Crawl, the Perplexity Publisher Program. Qualification requires the governance and infrastructure work from the two pillars above. Monetization is what happens when all three are in place.
We assess your qualification for the three live AI monetisation platforms, identify what is missing from your current setup, and build the path to eligibility. For publishers already eligible, we handle the onboarding.
If your business runs on display advertising, AI traffic changes the equation. We review how your current model responds to a shift in the traffic mix — and identify where there is exposure and where there is opportunity.
AI systems send different audiences than search does. We work with you to understand the change in your traffic profile and assess whether your current subscription and membership model is positioned for it.
A prioritised plan for building revenue streams that are less dependent on the traffic models that AI is disrupting. Not theory — a sequenced set of moves, with the infrastructure dependencies mapped out.
Where does your domain stand today?
We start with a scan of your domain — the same framework that produced every number in our global research. You get a scored picture of where you stand and a prioritised build order for what to do next.