At the start of the week I had a nagging SEO problem with the Civo Cloud Manager marketing site. Two pages were fighting over the same search query, both targeting Object Storage, both thin enough that neither was winning. By the end of the week the fix was in, six new guide pages were live in all 16 locales, and the code tokens buried in the guide prose were finally marked up correctly. Not a dramatic week. Six commits total. But the work was real and the decisions behind it are worth writing down.
Content architecture on civo-cloud-manager.app
The biggest thing I shipped was six new guide pages, each published across all 16 language routes the site already supports. The guides live inside a topic cluster that now links properly back to the main feature pages, and vice versa. That internal linking was missing before. The pages existed in isolation. Google had no signal about how they related to each other or to the app itself. Wiring the cluster together is one of those changes that feels invisible on the day you push it and then quietly pays off over the following months.
The keyword cannibalism fix took less time but mattered more immediately. I had two Object Storage pages (one for the S3 browser feature, one for a broader guide), and they were competing for the same query. Neither was ranking. The fix was straightforward once I saw it clearly: differentiate the intent. The feature page targets someone who wants to know what the app does. The guide page targets someone who wants to learn how to do something. Different queries, different content shapes, different internal link targets. A few hours of editing and the overlap was gone.
I also marked up the code tokens in the guide prose properly, wrapping inline commands, file paths, and API names in <code> tags instead of leaving them as plain text. This is the kind of thing that should have been done from the start. It was not. Prose that mixes natural language and technical strings without semantic markup is harder to read and gives search engines less signal about what the page is actually about. Not a big fix, but it was overdue.
What I dropped this week: the llms.txt link that had been sitting in the footer. I had added it a few weeks ago as an experiment: a machine-readable hint for AI crawlers about what content is available. In practice it added footer noise and I am not convinced it does anything measurable yet. Out it goes. I can always add it back.
The Civo Cloud Manager marketing site is the public face of a native macOS app I am building for developers who run workloads on Civo Cloud: Kubernetes live dashboard, S3 file browser, menu-bar firewall, Touch-ID-protected credentials. If you are thinking about having a custom app built and wondering what the ongoing maintenance and content work actually looks like alongside the development, this is it: small, consistent, unglamorous. It adds up.
You can find it on the Civo Cloud Manager app page.