Crypto Accountants: running four connected web properties and their technical SEO as one engineer

How I run the Crypto Accountants web platform as one engineer: site, forum, academy and AI assistant, with a daily technical SEO routine for the UK.

Client
Crypto Accountants, UK
Role
IT Operations, Web and Digital Marketing Manager
When
Jul 2025 to now
Stack
WordPress, PHP, Technical SEO, Schema markup, Google Search Console, Hosting and security, LLM APIs

Visit the live site

Crypto Accountants web platform, screenshot
4connected web properties
In short

The Crypto Accountants web platform is four connected properties, a WordPress site, a forum, an academy and the ALI AI assistant, that I run as the single engineer for a UK firm. I handle hosting, security and uptime, plus a technical SEO routine: audit, improve one page at a time against search intent, outreach and measurement.

The Crypto Accountants web platform is four connected properties, a WordPress site, a forum, an academy and the ALI AI assistant, that I run as the only engineer. Since July 2025 I have handled hosting, security, uptime and a daily technical SEO routine aimed at ranking for "crypto accountant" in the UK.

The problem

Crypto Accountants is a UK firm. Its web presence is not one site but four: the main WordPress site, a community forum, a learning academy and an AI assistant. Each has its own software, its own updates and its own failure modes, and all of them reflect on the firm.

On top of keeping everything up and secure, the firm wants to be found by people searching for a crypto accountant in the UK. That is a competitive term, and SEO done in bursts tends to produce noise rather than progress.

Constraints

  • One engineer for everything. Operations, security, development and SEO all sit with me.
  • Four separate properties. Updates, backups and monitoring have to cover each one.
  • A regulated, trust-sensitive field. Content has to be accurate, and the site has to look and behave like a professional firm.
  • Measurable SEO. Effort has to show up in rankings and Search Console data, or it is not worth repeating.

What I built

Operations across four properties

I run hosting, security and uptime for cryptoaccountants.live, forum.cryptoaccountants.live, academy.cryptoaccountants.live and cryptoaccountants.ai. Treating them as one platform means one routine for updates, checks and fixes instead of four ad hoc ones.

A technical SEO routine for the main site

The main site follows a fixed loop: audit, pick one page, improve it against what searchers actually want, and measure. Technical work covers the usual foundations, such as Core Web Vitals, schema markup, crawlability and Search Console health. Alongside that, I run weekly link outreach.

The AI assistant

ALI is the fourth property and the most technical. It answers UK crypto tax questions from HMRC guidance with quotes and exact links. It has its own write-up in the ALI case study.

How it works

  1. Run an audit to find technical issues and pages that underperform for their search intent.
  2. Choose one page and define the intent it should satisfy.
  3. Improve the page: content, headings, internal links, schema and speed where needed.
  4. Run weekly link outreach to earn references to the site.
  5. Measure rankings and Search Console data, then decide the next page.
  6. Keep hosting, security and uptime checks running across all four properties in the background.

Decisions and trade-offs

One page at a time versus a site-wide rewrite. A big rewrite feels productive but makes results unreadable: if rankings move, you cannot say why. Improving one page at a time against search intent is slower to start, but every change is something I can measure and either keep or undo. My WordPress technical SEO checklist covers the audit side of this.

Search intent before keywords. Matching a page to what someone is trying to do matters more than repeating a phrase. For a firm like this, a searcher usually wants to know whether the firm can help with their situation, so pages are written to answer that directly.

A platform view of operations. Running four properties as one system costs some upfront effort in setting up shared routines, but it is the only way one person keeps four sites patched, backed up and monitored without things slipping.

Answer-first content. Pages lead with a direct answer, which serves both readers and AI search tools that quote sources. I wrote about that approach in how to get cited by ChatGPT and AI Overviews.

Outcome

All four properties, the site, forum, academy and ALI, are live and run by one engineer, with hosting, security and uptime handled as a standing routine. The main site follows a repeatable SEO loop of audit, page-by-page improvement, weekly outreach and measurement in Search Console. I do not quote ranking or traffic figures here because I only publish numbers I can verify.

What I would do next

  • Tighten internal linking between the four properties so authority and readers flow between them.
  • Build more of the routine into automated checks, so regressions are flagged before they reach Search Console.
  • Keep extending structured data where it accurately describes the firm's services.

If you want the same approach on your site, see my technical SEO service or get in touch.

Questions people ask

What does the Crypto Accountants web platform include?

Four connected properties: the main WordPress site at cryptoaccountants.live, a forum at forum.cryptoaccountants.live, an academy at academy.cryptoaccountants.live, and the ALI AI assistant at cryptoaccountants.ai. I run all four as one engineer, covering hosting, security, uptime and SEO.

What is your technical SEO routine?

Audit first, then improve one page at a time against search intent, run weekly link outreach, and measure rankings and Search Console data to see what changed. The aim is the search term "crypto accountant" in the UK. Working one page at a time makes it possible to tell which change made the difference.

Why improve one page at a time instead of changing the whole site?

If you change fifty pages in a week and rankings move, you cannot tell which change helped or hurt. Working page by page against a clear search intent keeps each change measurable in Search Console. It is slower to start but gives you evidence instead of guesses.

Can one engineer really run four properties?

Yes, if the work is routine and the stack is kept simple. Hosting, security and uptime are handled as a standing process, and SEO follows a fixed weekly rhythm. The trade-off is that large new features wait their turn, so priorities have to be clear.

Need something like this?

Want results like these?

Tell me what you are building. I reply within one working day.

Start a project