While Keeping Both Platforms Separate and Functioning Smoothly
Love your blogging platform and marketing platform?
With /Blog you don’t need to compromise – you can have the best of both worlds.
You can use two different platforms, but serve them both from the same URL.
Consolidate your backlinks and let your blog benefit from your root domain’s authority.
Get the best of both worlds – your blogging platform and your marketing platform.
Eliminating domain switching keeps visitors longer and boosts engagement.
Magically make your subdomain serve from your subdirectory.
Your blog can be at "/blog" or any other desired subdirectory.
Links, canonical tags, and many more elements will show your subdirectory so Google and visitors will truly be browsing a subdirectory.
From updating internal links to structured data/schema, the API takes cares of SEO.
Your sitemap links will automatically point to your subdirectory meaning Google will get 200 (instead of 301) HTTP codes when crawling.
This prevents two versions of your website being available (no good for SEO or usability).
Even though the subdomain redirects to the subdirectory, there is special logic in place to allow admin traffic through allowing content editors/admins to continue working as normal.
As long as your traffic is proxied through Cloudflare (orange clouds).
On average, lightning travels at a speed of 1 foot per nanosecond through air. Assuming the distance between the cloud and the ground is about 1 mile, it would take approximately 5.3 ms for the lightning to travel from the cloud to the ground.
/Blog API takes around 5ms from start to finish, aka lightning fast.
No, your website managers (such as content people and marketers) continue working how they always have – logging into the same place, working on the same URLs, etc.
No, this is not against any Google guideline, nor will it ever be. That’s because it’s not manipulative.
No, minimal input is required from you. If you decide to self-install the Worker then it will require a bit more work.
No, it can be undone rather easily, but that’s not advisable.
Kind of, but anything that Google says has to be analyzed. Here it goes… When considering a brand new domain, creating a subdomain will be given the same fair shot at achieving rankings as the root domain. So it is true that subdomains and root domains have equal treatment. But here's where this unravels. If we are considering creating a brand new subdomain on a domain that has built up credibility and traffic over time, they will not be treated equally. The root domain has established its dominance, but the subdomain has not.
When a visitor goes to the desired subdirectory, Cloudflare will intercept the request and call our lightning fast API that is on the Cloudflare edge. Our API will retrieve your subdomain, make any necessary changes (like swapping out HTML references to the subdomain) and return the page. The visitor is then delivered the subdomain page disguised as the subdirectory. This all happens in around 5 ms.
Probably, but nothing is guaranteed. Here are 14 case studies of people achieving massive success when moving their blog to their root domain.
There is a one-time installation fee + a monthly subscription to the API.
There will be virtually no difference. There is approximately 5 ms added to each request.
Contact me with whatever you might be wondering!Email /Blog