Project Overview
Abdul Majid 25 Urban Residence is a boarding house (kosan) property in Indonesia offering 23 rooms. The property owner originally built his own website using Durable.com, a drag-and-drop page builder, which took approximately three hours to complete. The result was a functional but poorly optimized site with no SEO strategy, no heading structure, and no visibility on Google.
When the owner brought in new business development support, the website was immediately flagged as a critical issue. Dwi Yanti was asked to rebuild it entirely. My role covered everything: design, copywriting, content structure, SEO architecture, technical implementation, and ongoing optimization. The project began on Blogspot with a custom domain and later migrated to self-hosted WordPress — a decision driven entirely by technical SEO requirements.
This case study documents both phases of the project: the initial Blogspot build and the subsequent WordPress migration, including the technical problem that made the migration necessary.
SEO Problem Identified
After the initial Blogspot build, the site performed well — ranking on page 1 of Google within hours of launch, eventually reaching positions 2 and 3 for target keywords. However, following a series of Google algorithm updates, an unexpected redirect issue emerged.
Blogspot's domain handling was producing redirect chains between the custom domain and the underlying blogspot.com address. These redirect chains are a known negative signal for Google — they slow crawling, dilute link equity, and create ambiguity about the canonical URL. Despite still holding a page 1 position, the ranking stability was compromised and the redirect behavior was outside my control as long as the site remained on Blogspot infrastructure.
Dwi Yanti attempted multiple fixes within the Blogspot environment — adjusting domain settings, reviewing DNS configuration, and testing redirect behavior across different tools including redirect checker and Google's URL Inspection tool in Search Console. The root cause was architectural: Blogspot's platform introduces redirect layers that cannot be fully eliminated by the site owner.
Staying on Blogspot meant accepting a permanent technical SEO ceiling. That was not acceptable for a client whose occupancy directly depends on search visibility.
Technical SEO Analysis
Before deciding on a migration path, Dwi Yanti conducted a full technical audit of the existing Blogspot site using the following tools and methods:
-
1
Redirect Chain Analysis Mapped the full redirect path from the custom domain through to the final URL using a redirect checker. Confirmed multi-hop redirect chain originating from Blogspot's internal domain routing.
-
2
Google Search Console — URL Inspection Checked how Google was crawling and indexing the site. Confirmed that Googlebot was following the redirect chain and indexing the correct URL, but flagged crawl efficiency as a concern.
-
3
Schema Markup Audit Validated existing Schema with Google's Rich Results Test. Blogspot's template system limited what Schema types could be implemented — structured data was minimal and not fully controlled.
-
4
Page Structure Review Reviewed heading hierarchy (H1–H3), meta title, meta description, and canonical tag behavior. Blogspot's template overrides made it difficult to maintain clean canonical output across all pages.
-
5
Competitor & Keyword Gap Analysis Reviewed competing boarding house websites using Ahrefs and Semrush to identify gaps in content coverage and Schema types that could strengthen topical authority post-migration.
The platform itself was the bottleneck. No amount of on-page optimization could eliminate a redirect chain that Blogspot's infrastructure introduced at the DNS level. The only correct solution was a full migration to a platform where every layer of the technical stack — from server response to canonical output — is under direct control.
SEO Strategy Implemented
The migration strategy was built around a single principle: rebuild everything from code, not from templates. This is the approach Dwi Yanti apply consistently across all projects as part of my technical SEO specialist work — because templates introduce unknown variables into your SEO architecture.
Platform Decision
Self-hosted WordPress on Business hosting was selected for three reasons: full PHP access for custom theme development, complete database control for the room availability system, and no restrictions on plugin or code customization.
Domain Strategy
I recommended the client purchase urbanresidence.id — a clean, brandable domain with the .id country code TLD. This immediately signals geographic relevance to Google for Indonesia-based searches and eliminates any association with the previous Blogspot URL structure.
Custom Theme Architecture
Rather than installing an existing WordPress theme and modifying it, Dwi Yanti built the theme entirely from scratch using HTML, CSS, and PHP. This decision was not about aesthetic preference — it was a technical SEO decision. Every line of code in the theme exists for a reason. There is no unused CSS bloating render time, no theme-generated markup competing with SEO output, and no plugin dependency for functionality that can be written directly.
SEO meta tags, Open Graph tags, Schema JSON-LD (LocalBusiness, BreadcrumbList, WebPage),
canonical URL logic, and heading structure were all written directly into the theme's
header.php, functions.php, and individual page templates.
No SEO plugin was used or needed.
Content Strategy
All page copy, headlines, and article content were written by me with SEO intent from the first draft. Room descriptions, location content, and service pages were structured around target keywords while maintaining natural, readable language. This included writing content designed to answer questions that prospective tenants ask — directly targeting featured snippet and AI-generated answer opportunities.
Implementation Process
The full implementation — from domain purchase to live indexed site — was completed within three days. Below is the documented process in sequence.
-
1
Domain & Hosting Setup Purchased urbanresidence.id, configured DNS, and set up Business hosting with WordPress installed. Configured server-side redirects to enforce HTTPS and www/non-www preference.
-
2
Custom Theme Development Built complete WordPress theme:
style.css,functions.php,header.php,footer.php,index.php, page templates, and single post template. All coded from scratch in approximately three days. -
3
SEO Architecture Implementation Wrote all meta tag output, canonical logic, Schema markup (JSON-LD), and breadcrumb functions directly in
functions.phpandheader.php. Tested with Google Rich Results Test and W3C validator. -
4
Content Migration & Optimization Migrated all content from Blogspot with revised copy optimized for the new domain and target keyword set. Rewrote headings, meta descriptions, and body copy throughout.
-
5
Room Availability CMS Integration Built a custom PHP admin dashboard with its own database configuration, then created a config-bridge to surface room availability data inside WordPress page templates — without causing conflicts with WordPress's own database connection.
-
6
Google Search Console Setup & Indexing Submitted XML sitemap, requested indexing via URL Inspection tool, and monitored crawl coverage and index status. Verified Schema via Rich Results Test before submission.
WordPress uses a single
wp-config.php to manage its database connection. Calling a
second database config directly inside a WordPress page template causes connection conflicts.
The solution was to build the dashboard as a standalone PHP application in a subdirectory,
then expose only the necessary read functions through an isolated include file that WordPress
templates could safely call without touching or overriding $wpdb.
Results and Improvements
The results following the WordPress migration exceeded the performance of the original Blogspot build — which had itself already achieved strong rankings. The new architecture delivered faster indexation, stronger ranking stability, and measurable real-world business impact.
The site was indexed within 6 hours of launch and entered the SERP at page 1, positions 4–6. Over subsequent weeks it climbed to position 3, then 2, then settled at Rank #1. Google Analytics 4 confirmed international traffic from Japan, South Korea, France, and Singapore — directly correlated with new international tenants checking in at the property. The boarding house, which previously operated below full capacity, now regularly reaches full occupancy of all 23 rooms.
The redirect chain problem that triggered the migration was completely eliminated. No redirect hops exist between the domain and the served URL. Schema validation passes with zero errors. Bing Copilot now surfaces the property in AI-generated answers for relevant accommodation queries — a direct result of the structured data implementation.
SEO Insights from This Case Study
Platform choice is a technical SEO decision
Free platforms like Blogspot introduce infrastructure constraints that no amount of on-page optimization can overcome. When your hosting platform controls how redirects are handled, you do not have full SEO control — regardless of how well your content is optimized.
Building from code outperforms building from templates
A custom-coded WordPress theme with hand-written SEO architecture consistently outperforms template-based builds for one simple reason: there is no code in the output that wasn't intentionally placed there. Template bloat, plugin output conflicts, and unexpected markup are eliminated entirely.
Schema markup without plugins is achievable and more precise
Free SEO plugins generate Schema markup based on their own logic, which may not match your
actual page structure. Writing Schema JSON-LD directly into functions.php allows
you to output exactly the structured data that accurately describes each page — no more, no less.
This precision is what Schema validators and rich result eligibility checks reward.
SEO results translate to real business outcomes
Rank #1 on Google is not the end goal — it is the mechanism. The actual outcome of this project was a boarding house that went from partial occupancy to consistent full occupancy, with tenants arriving from five countries. That is what SEO specialist work looks like when it is executed correctly.
The most important decision in this project was not a keyword or a meta tag — it was recognizing that the platform itself was the problem, and making the architectural call to migrate before rankings deteriorated further. Technical SEO requires diagnosing problems at the infrastructure level, not just the content level.
This methodology — build from code, control every output, validate everything — is the same approach applied across all projects in my technical SEO and SEO strategy work.