How We Manage Multilingual Content Across Markets in DMARCeye Using HubSpot Content Hub
What is DMARCeye?
DMARCeye is a SaaS platform focused on email security — specifically on monitoring and evaluating DMARC reports and records. It has technically existed for more than a year, but until recently it was primarily an internal project created as a response to the DMARC requirements introduced by Google and Yahoo in early 2024.
DMARCeye was still waiting for its first paying customers, had no proper website, and therefore no meaningful position in search.
The Core Challenge
How do you start marketing a product that is technically complex, has a very low unit price (you pay just a few dollars per domain per month), and operates in a highly competitive segment?
Why PPC Was Not an Option
In this field, keywords are extremely expensive (USD 10–25 per click), search demand is very seasonal — spiking after major phishing waves or changes in email authentication standards — and with a low-margin product, PPC simply doesn't pay off.
This made the decision clear: instead of short-term performance campaigns, we needed to invest into content that brings long-term value.
Why We Chose HubSpot
In DMARCeye, we ended up moving to HubSpot Customer Platform — Professional, meaning the full suite:
- Marketing Hub for marketing
- Content Hub for website and content creation
- Sales Hub for sales
- Service Hub for customer support
- Data Hub for the data model
- Commerce Hub (which we have but don't use yet)
Buying the entire suite is a better investment than paying for each Hub separately. And moving additional services into HubSpot wasn't a problem for us. (We won't discuss the level of vendor lock-in here — that's for another time.)
We also connected the entire ecosystem to our product — all user activity inside the SaaS syncs directly into HubSpot. We wanted content to be part of the same environment, not a separate CMS living next to our CRM.
Originally, we saw HubSpot CMS purely as a temporary, emergency solution. We didn't want to block developer capacity with a project that belongs entirely to marketing.
But it turned out that HubSpot Content Hub can handle far more than we expected.
What Our Setup Looks Like
We currently have the website in 5 languages (EN / CZ / PL / JP / KR).
Additional versions — PT, ES and DE — are prepared, but no longer a priority because the initial goal (a fast launch and a stable content base) has already been achieved.
The entire content ecosystem is managed by one person, who doesn't even do this full-time. Besides DMARCeye, this person manages content for other projects as well — all entirely within HubSpot. That means: no Notion, no Trello, no spreadsheets.
What Tasks Do We Manage Inside HubSpot?
1. Writing articles for the website and the blog
New articles are created directly in HubSpot — including editing, formatting, and scheduling. All language versions are connected under a unified structure.
2. Complete website & blog management
From landing pages to articles — everything lives inside one system, which makes revisions, tagging and organising content by topic or language extremely fast.
3. Maintaining SEO topics and content clusters
HubSpot tracks the performance of pages, topics and keywords. AI suggests which articles should be updated, improved or linked internally to strengthen the visibility of the entire site.
4. Evaluating traffic and acquisition sources
We can see where visitors come from, how they behave, and which pages convert the best.
5. New article ideas via the "Blog Research Agent"
This AI agent automatically monitors keywords, search positions and the performance of existing content. Based on that, it generates new article suggestions every day. For now, we still manually review and approve them.
6. Translations and localisation
We write content primarily in one language (usually English). AI prepares it for translation, and then we convert it into additional language versions using DeepL. Each language version is further optimised for local SEO.
7. Content repurposing
From a single article, we generate social posts, newsletters or supporting emails — all again inside HubSpot without switching tools.
Goal: Content Optimised Not Only for Google, But Also for Language Models
Alongside classic SEO, we now focus on LLM optimisation — ensuring our articles and pages are readable and understandable for AI assistants and retrieval-based chatbots.
We believe this is where B2B content is heading in the coming years. HubSpot offers a real advantage here — it allows us to manage, evaluate and iterate content in real time, from a single place.
Early Results
We're still at the beginning — proper evaluation will come in a few months once we see the impact on organic traffic and engagement. I'll be happy to share those numbers later.
But already we know that:
- HubSpot Content Hub handles multilingual content better than we expected,
- AI content assistants save time instead of adding more work,
- A unified environment for marketing, sales and support is a massive operational advantage.
A Few Numbers
- 📊 0 developers / 0 designers
- 🕛 1 month
- ✍️ 1 part-time copywriter
- 🌍 1 website → 5 language versions
- 📄 384 published pages
Conclusion
HubSpot Content Hub is not a perfect CMS and has its limitations — but I don't think its purpose is to compete with standalone CMS platforms. Maybe we should have spent more time in the early stages planning the structure or choosing a better template. But that wasn't the point of this exercise.
The real value is in the Combo: Content Hub + Marketing Hub + AI.
Together they form a strong backbone for modern content management. And above all, they allow small teams to achieve results that used to be slow, painful and resource-heavy. For us at DMARCeye, it started as a necessity. Now, it's a deliberate strategy.
Originally published on Medium.