Serve HubSpot as a Subdirectory
Don't throttle your HubSpot blog by putting it on a subdomain. Slashblog lets you run two platforms from one domain so you get the best SEO! 🚀
HubSpot Subdomain vs Subdirectory
Subdomain
- Throttles traffic to your blog as your subdirectory doesn't fully benefit from your root domain
- Poor UX from two websites because your visitors have to switch between domains
- Increased security risk because it's easy to detect you're using HubSpot
- Increased bot traffic which may increase server costs
Subdirectory
- Consolidate your backlinks and let your blog benefit from your root domain’s authority
- Better UX and engagement because users stay on one domain
- Get the best of both worlds – your blogging platform and your marketing platform
- Reduce security risks as it's harder to detect you're using HubSpot
- Reduce bot traffic which can lower your server costs and free up resources for real people
Slashblog is The Best Solution to Serve HubSpot as a Subdirectory
If you searched for "serve HubSpot as a subdirectory", you'll like have found no solutions.
Many people in the HubSpot Community have asked this question, but the answers are a resounding, "no, can't be done".
Yes, you can serve your HubSpot site as a subdirectory of another site.
Slashblog lets you serve your HubSpot site as a subdirectory!
I set out to create a simple solution. One that is done for you so you don't have to spend time on this. And one that doesn't risk messing up your website.
Here's how it works:
- Let's say your root domain is WordPress (it can be anything as long as you meet the requirements)
- When a visitor goes to example.com/blog, we'll instruct Cloudflare to intercept the request, and in fact request blog.example.com/blog, but serve it from the first URL!
- Users and Google navigate your subdirectory (which is HubSpot)
This effectively lets you use two (or more) platforms and serve them from the same domain!
Features
/make-it-indistinguishably-a-subdirectory
Serve your subdomain as a subdirectory
Magically make your subdomain serve from your subdirectory.
Works with any path
Your blog can be at "/blog" or any other desired subdirectory.
Auto updates references to the subdomain in the HTML
Links, canonical tags, and many more elements will show your subdirectory so Google and visitors will truly be browsing a subdirectory.
No SEO issues
From updating internal links to structured data/schema, the API takes care of SEO.
Auto updates links in sitemap
Your sitemap links will automatically point to your subdirectory meaning Google will get 200 (instead of 301) HTTP codes when crawling.
Auto redirects subdomain to subdirectory
This prevents two versions of your website being available (no good for SEO or usability).
Continue using backend of subdomain
Even though the subdomain redirects to the subdirectory, there is special logic in place to allow admin traffic through. This allows content editors/admins to continue working as normal.
Works with any platform on your root domain
As long as your traffic is proxied through Cloudflare (orange clouds).
Lightning fast (literally)
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.
Supporting HubSpot and SEO
Form Submissions
Some solutions stop forms from working! Not Slashblog.
Slashblog works with:
If you don't see your form solution, contact us and we'll test it. It most likely will work.
SEO
Plugins will continue outputting references to your subdomain. But Slashblog intelligently updates HTML to reference your subdirectory.
- Links
- Schema
- Canonical
- Sitemaps
- Redirections
- Next
- Open Graph
- Icons
- Stylesheets
- Scripts
- Meta Content
If you are curious about a certain feature or SEO impact, contact us.
/requirements
Use Cloudflare with proxy on (orange clouds) for both the subdomain and root domain.
Add me to your Cloudflare with just two permissions (Workers and Firewall).
If you're not already using Cloudflare to manage your DNS, you 100% should. It's free and provides improved performance and security.