Blogpost SEO gives the same data on different posts

Helpdesk Collections
1

Hello Community,

I’m at a loss, and unfortunately, Sitejet support hasn’t been making any real progress for several weeks. They say they’re working on it. I’m just puzzled that my blog’s SEO isn’t working, while it works fine with Websitebutler.

My problem:

When I run SEO simulations for my individual blog posts, I always get the same SEO results for each of the three posts, even though I’m using a different post URL.

The posts in question are listed here:

I’m testing with https://totheweb.com/learning_center/tools-search-engine-simulator/

No matter which of the three post URLs I test, I always get the results for this post: Wirksamen Meetingstruktur – Frischer Wind in Meetings

This includes the same keywords and the same H1, H2, and H3 headings.

However, when I test this with the blog articles from Websitebutler here: Websitebutler Ratgeber | Alles über Websites und Unternehmenserfolg then the tool displays the correct values ​​for each page, as expected.

Has anyone else encountered this problem and perhaps found a solution or workaround?

Just to know: I’ve integrated the regular blog collection, only slightly tweaking the design and renaming it. I haven’t changed anything else technically.

2

From your page source, this doesn’t look like a normal fully rendered HTML page. It looks more like a partial template with injected scripts, and I don’t see key SEO elements like a proper meta description or canonical tag.

That would explain why every URL returns the same SEO result — the tool is likely seeing the same base HTML for each post.

Here are the most important things I’d check:

  1. View the raw page source (not inspector) for multiple blog posts and compare:
  • <title>
  • <meta description>
  • <h1>
    If these are identical, your template isn’t outputting dynamic data per post.
  1. Look for a canonical tag:
<link rel="canonical" href="...">

If it’s missing or the same across posts, search engines will treat them as one page.

  1. Check if your blog content is actually present in the HTML source.
    If it’s loaded via JavaScript, SEO tools (and sometimes Google) may only see the base template.

  2. In Sitejet, make sure you’re not using custom HTML blocks in the blog template, as that can break rendering.

3

Hello @Kalisperakichris

Your analysis confirms what I’ve already discovered.

Since I built everything using only Sitejet’s built-in features, without any custom HTML, I assumed it would work.

So why isn’t a normal HTML structure being generated here? Why does it work with Websitebutler’s blog pages, though?

I’ve created another test blog, completely without a header or footer, to rule out any potential influences that aren’t part of the collection: https://www.bewusstes-unternehmen.com/blogtest-eintrag

The collection and the collection entry on the individual page are both directly on the page, without any nesting. It’s the collection and the individual page layout that Sitejet generates without any changes on my part.

Of course, there are containers linked to CMS elements, but these are also built-in Sitejet features, and I wouldn’t consider them custom HTML. I’ve also tested it without them and still get the error.

After searching extensively here, I found a blog that also has this problem (https://www.ltwebdesigns.com/ → under News). So it’s not just me.

Therefore, I would assume it’s not my fault, but of course, I’m not ruling it out and am more than open to constructive tips.

Perhaps there are certain settings that need to be changed somewhere, or perhaps shouldn’t be changed at all. I have no idea, so if anyone has any experience or ideas, I’d appreciate it.

4

Hi Dirk,

Thanks for sharing all the details — that’s really helpful.

From what you described (and especially since you’re seeing identical results across different post URLs), it does seem like the tool is picking up a shared base template rather than fully rendered, per-post HTML.

In Sitejet collections, a lot of content is injected dynamically, so some SEO tools may not properly interpret the final rendered output — especially if they rely on initial HTML instead of fully executed JavaScript.

Since you’ve already confirmed this happens even without custom elements, it could indeed be a limitation (or bug) in how Sitejet outputs collection pages, or how the testing tool processes them.

At this point, it might be worth:

  • Testing with Google’s URL Inspection or Rich Results Test (to see how Google actually renders the page)
  • Reaching out to Sitejet support to confirm how collection pages are rendered for SEO

Curious to hear if others have seen similar behavior :+1: