Description
Upbinger Blog lets you seamlessly embed your blog content — published through Upbinger — into your WordPress site at /blog. Posts are rendered on the server so search engines see the full article, and the blog’s styles are scoped so they never clash with your theme.
Key Features
- Server-side rendering for SEO — Full post content,
<title>, meta description, canonical link, Open Graph/Twitter tags and JSON-LD are in the first HTTP response, and unknown posts return a real 404. - Posts listed in your sitemap — Every published post is added to WordPress’s sitemap (
wp-sitemap.xml), to Yoast SEO and Rank Math sitemaps, and served at/blog/sitemap.xml, so search engines can find all of them. - Automatic fallback — If your host cannot reach the Upbinger CDN from the server, the blog renders in the browser instead, so it always displays.
- Theme-safe CSS — The blog stylesheet is scoped to the blog container, so it cannot affect your theme.
- rem → em Conversion — CSS
remunits are converted toemso blog typography renders correctly regardless of your theme’s root font-size. - Customizable Styles — Configure grid title, colors, fonts, spacing, and more from the Upbinger dashboard.
- Clean URLs — Posts live at
/blog/your-post-slug/, listing pages at/blog/page-2/. Old.htmladdresses redirect permanently to the clean ones. - Anonymous Analytics — Visit counts are sent via
sendBeaconwith session deduplication. No cookies, no PII.
How It Works
- Your blog HTML is published to the Upbinger CDN.
- When a visitor or search engine loads a blog address, the plugin fetches that page from the CDN (cached for a few minutes).
- The content, SEO tags and scoped styles are placed into your theme’s page template.
- The post list is added to your sitemap so search engines discover every post.
Requirements
- An active Upbinger account with a published blog.
- WordPress 5.6 or higher, with any permalink setting other than “Plain”.
- PHP 7.4 or higher.
External services
This plugin relies on two third-party services provided by Upbinger.
Upbinger CDN (cdn.upbinger.com)
Blog HTML, CSS, images, and font references are fetched from the Upbinger content-delivery network.
- What is sent: an HTTPS GET request containing only the URL path of the file being loaded (e.g.
/blogs/example.com/index.htmlor/blogs/example.com/sitemap.xml). No cookies or personal data are transmitted. - When: when a blog page is loaded on your site; when a search engine or the settings page requests the post list for the sitemap (the list is cached for 30 minutes).
- Service provider: Upbinger — Terms of Service | Privacy Policy
Upbinger Analytics API
Anonymous page-view events are sent so site owners can see which posts are popular. No cookies are set and no personally-identifiable information is collected.
- What is sent: the page path, a session-scoped deduplication flag (stored in
sessionStorage), and the site domain. The request is made vianavigator.sendBeacon. - When: once per unique page view per browser session (deduplicated). Can be disabled entirely from Settings → Upbinger Blog → Disable Analytics.
- Endpoint:
https://m745tnh6jg.execute-api.us-east-1.amazonaws.com/api/trackVisit - Service provider: Upbinger — Terms of Service | Privacy Policy
Installation
- Install the plugin from Plugins → Add New, or upload the
upbinger-blogfolder to/wp-content/plugins/. - Activate the plugin through the Plugins menu in WordPress. A
/blogpage is created automatically. - Make sure Settings → Permalinks is set to anything other than “Plain”.
- Visit
/blogon your site to check that your posts appear. - Optional: open Settings → Upbinger Blog to see the status, turn analytics or the sitemap listing off, or enable debug logging.
- Submit your sitemap (
/wp-sitemap.xml, or your SEO plugin’s sitemap) in Google Search Console.
FAQ
Do I need an Upbinger account?
Yes. The plugin loads blog content from Upbinger’s CDN, so you need a published blog on the platform.
Will this break my theme’s styles?
No. The blog’s stylesheet is scoped to the blog container, so it cannot leak into the rest of your site.
Why are font sizes different on my site?
Some themes set html { font-size: 62.5%; } which changes the meaning of CSS rem units. This plugin automatically converts rem to em and sets a 16px base so blog text renders at the intended size.
Does this affect my SEO?
Positively. Posts are rendered on the server with their title, description, canonical link, Open Graph/Twitter tags and JSON-LD structured data, and every post is listed in your sitemap.
My posts are not showing up in Google. What should I check?
- Update to version 2.3.0 or later, which lists your posts in the sitemap.
- In Google Search Console, submit
https://your-site/wp-sitemap.xml(or your SEO plugin’s sitemap index). - Use URL Inspection → Test live URL on one post. If it reports “Blocked” or a 403 error, your host’s firewall or bot protection is blocking Googlebot; allow it in your hosting control panel.
- Settings → Upbinger Blog shows how many posts are listed in the sitemap.
Which SEO plugins are supported?
WordPress’s built-in sitemap, Yoast SEO and Rank Math list the posts automatically. With any other SEO plugin, the blog sitemap is added to your robots.txt as /blog/sitemap.xml, which search engines read.
Are analytics GDPR compliant?
Yes. The plugin sends anonymous page-view events only (no cookies, no personal data). You can also disable analytics entirely from the settings page.
Changelog
2.3.0
- Posts are now listed in your sitemap. Upbinger posts are not stored in the WordPress database, so no sitemap listed them and search engines had to find each post by following links. Every published post is now added to WordPress’s sitemap (
wp-sitemap.xml), to Yoast SEO and Rank Math, and served at/blog/sitemap.xml(also added torobots.txtwhen another SEO plugin replaces the WordPress sitemap). Can be turned off in Settings → Upbinger Blog. - Old
.htmladdresses redirect. Links to/blog/your-post.htmlnow redirect permanently to/blog/your-post/instead of showing “not found”. - Consistent structured data. Post URLs inside JSON-LD now match the canonical address.
- Status at a glance. The settings page shows how many posts are in the sitemap.
- Rewrite rules repair themselves after an update that adds a new route, without visiting Settings → Permalinks.
2.2.0
- Server-side rendering for SEO, with automatic fallback. When your WordPress host can reach the Upbinger CDN, the blog is now rendered on the server: full post content,
<title>, meta description, canonical, Open Graph/Twitter tags and JSON-LD are in the first HTTP response, and unknown posts return a real 404 — so search engines index your posts without running JavaScript. - Never worse than before. If the host cannot reach the CDN from the server, the plugin automatically falls back to the previous client-side rendering, so the blog always displays.
- Theme-safe CSS. When rendering server-side, the blog stylesheet is scoped to the blog container so it cannot leak into your theme.
2.1.2
- Reverts to the stable client-side rendering of 2.0.2. The server-side rendering introduced in 2.1.0/2.1.1 could leave the blog area blank in some environments; it is being reworked and re-tested before re-release. Your blog displays normally again on this version.
2.0.2
- Fix: Remove ALL duplicate canonical tags (not just first one) to prevent SEO conflicts.
- Fix: Strip .html suffix from canonical and og:url for clean public-facing URLs.
- Fix: Deduplicate meta tags by property/name before injecting.
- Add: Light DOM H1 tag for SEO crawlers that cannot read Shadow DOM content.
2.0.1
- Fix duplicate JSON-LD structured data (BlogPosting + FAQPage) appearing in both document head and Shadow DOM.
2.0.0
- Complete rewrite for WordPress.org coding standards.
- Shadow DOM isolation for CSS conflict prevention.
- rem → em conversion for theme compatibility.
- SEO meta injection (OG, Twitter, canonical, JSON-LD).
- SPA-style internal navigation.
- Anonymous analytics with session deduplication.
- Debug logging gated behind an admin setting.
- Proper escaping, sanitization, and i18n throughout.
1.0.0
- Initial release.