Final Boss of Heading in CMS, please Help - first part of the problem so everybody can understand what I am talking about - a visualization of the question below. Start from 2:46 if you acknowledged the first part; everything before is just a rewind

Hey guys, in this video, I want to address a major problem I’m facing with the headings on my website’s CMS collection pages. Currently, all the headings are managed through the CMS, which is causing some serious SEO issues. The website’s SEO checker shows that we have an excessive number of H1, H2, and H3 headings due to the way they are implemented. I’ve tried various solutions, but it seems that the only viable option is to add custom fields for each heading on each country’s page. However, the problem is that the business plan only allows for 60 custom fields in the CMS, and I would need at least 250 for all the pages and countries. I’m wondering if anyone has encountered a similar problem and if there’s a way to increase the limit of fields or find an alternative solution. Your input would be greatly appreciated! :pray:

I am 100% serious that this issue can kill my business if I need to re-do every page manually, because I don’t see an option of just easily dublicating each page and providing changes separately, so I’m really asking for some help or advice on how I can fix this Headings problem without re-creating each page from scratch :pray::pray::pray::pray:

P.S. I attach the answer from support, but this guys are not responding with correct information from what i see (correct me if I am wrong)

Here is my public share link: Webflow - Golden Harbors

You have an odd structure for all of this. It’s non-standard as far as I can tell.

The common approach is to have a CMS Collection with many items in it. Each item would be your main topic, like a country (as one example).

So Cambodia, Egypt, France, etc… and each of those items has everything it needs to add dynamic content to your CMS Collection Page.

It can contain a few page titles, images, content, etc… you can do a lot with 60 fields.

This would be information about the services you provide for each of those countries. Then, when any one area within this topic has more details, you can click into another page (much like a how a blog is setup) to get more details.

If you need more custom control per collection page, that’s when you start using Rich Text Fields.

It’s 1 field and gives you a lot more control. Take a look at the Webflow blog as an example. They maybe use 15 CMS fields. It’s mainly a Rich Text Field.

They have some small structural changes between them, but much like Webflow support suggested to you, you use conditional visibility for that. It provides a way to make that one CMS Collection Page look a bit more unique.

My only real advise would be for you to take a step back, go through some of the tutorials and try to understand how the CMS should be structured in Webflow.

Then look at the Webflow blog and see if you can understand how they structured it.

Once you start understanding some of the basics that it looks like you may be missing, then go read how to do more advanced stuff.

Here’s a good resource to get you started:

What they do is fairly complex, and they only use 35 fields, and I think this would be going beyond what you would need (if I’m understanding your needs).

Sorry I don’t have a better, more direct “solution” for you. But I think you’re going in the wrong direction and if you don’t course correct, you’ll just continue being frustrated.

Good luck!

1 Like

Hey again GH,

A few things specific to your current questions-

Webflow uses blue to indicate elements that are static ( not CMS bound ), like this-


Purple indicates elements that are dynamic ( CMS bound ) -


You need to choose which parts of your page content are static, and which are dynamic, depending on your design goal.

As for the SEO issue, if you want to, you can use an HTML embed instead to mix static and dynamic content into a single H2 element.

e.g. HTML - <h2>{{ Country Name }} Citizenship</h2>

Where {{ Country Name }} is the correct embedded field you want ( click + Add Field, top right of the code embed editor window ).

I’ve said this already in my previous reply, but your site design approach in how you’re using collections is very difficult to manage and will cause you a ton a frustration.

You really need to redesign your CMS use and collection pages.

Rather than trying to store ever since piece of dynamic information in a field, make much better use of Rich Text elements. You can do a ton with them and get much more advanced layouts when you combine them with Finsweet’s Powerful Rich Text extension.

1 Like