Something has been bugging me lately, so I figured I would think it through here in writing.
I run a small site under my humfurie.org domain that covers Cordova, Cebu. It is not affiliated with any government office or tourism board. It is just something I put together on my own time: blog posts about local spots, a page or two on hotels, and a handful of business listings for the town. Nothing groundbreaking. It is not the kind of project that is going to win any awards or attract a flood of visitors overnight. But it is useful, it is real, and people from Cordova (or people planning a trip here) occasionally find it helpful.
Here is the conflict. Right now this Cordova content lives as part of humfurie.org, and humfurie.org is supposed to be my portfolio site. It is where potential employers or clients look when they want to see my work as a software engineer: my projects, my writing about Laravel and NestJS, the things I actually build for a living. It is my professional front door.
The Cordova tourism and business content is a completely different animal. It is not about software engineering at all. It is local, service-oriented, and aimed at a completely different audience (tourists, small business owners, people searching "hotels in Cordova Cebu" rather than recruiters searching for a backend developer). Mixing the two under one domain means Google Search Console sees one property with wildly mismatched topics. I checked, and it is exactly as I suspected. Search Console merges everything under humfurie.org, subdomains included, into a single property. My impressions and clicks for "Laravel developer Philippines" style queries sit right next to impressions and clicks for "Cordova Cebu hotels." That is not a clean signal.
The numbers make this more concrete than I expected. Over the last 28 days, the Cordova subdomain pulled in 1.54k impressions on its own. That is not nothing for a town this size, but it is also lower than I would like, and I suspect part of that ceiling is simply because it lives as a subdomain rather than a standalone, fully indexed domain in its own right. What stands out more is where my traffic actually goes. Consistently, it is the Cordova content pulling people in, not the portfolio pages. So the site that is supposed to be my professional front door is, in terms of raw traffic, being outpaced by a side project about hotels and businesses in a small coastal town.
And yet, none of that traffic has turned into anything. No business owner has reached out. No tourist has messaged me. As far as I can tell, there just is not much active interest in Cordova as a destination at the moment, at least not the kind that converts into outreach. The impressions are there. The engagement is not. That is an odd position to be in: real, measurable progress on paper, and basically zero real-world response to show for it.
So why keep going back and forth on this instead of just deciding? If I am honest, the biggest problem is not the domain question at all. It is that no one manages this project except me, and I am not consistent about it. My portfolio and my other sites get regular attention. Cordova gets attention in bursts, whenever I remember it exists or feel like writing something. It has generated its own traffic despite that inconsistency, which honestly says more about the potential than the current execution.
That is probably the real answer buried in all of this. If I gave the Cordova site its own domain, I would want it to grow into something bigger: more listings, more consistent posting, maybe eventually monetized through affiliate hotel bookings or paid business placements. But a new domain will not fix an attention problem. It will just give an attention problem its own postal address. Before I spend money separating it from humfurie.org, the more honest question is whether I am ready to actually show up for it consistently. If the answer is yes, the domain is a small cost. If the answer is still no, splitting it off just moves the neglect somewhere else and stops it from at least contributing traffic to a domain I do maintain regularly.
For now, I think the plan is to keep testing my own consistency on the Cordova content before I commit to a separate domain. If I can prove to myself that I will actually show up for it week after week, the case for splitting it off becomes obvious. If I cannot, no domain is going to solve that.