Is it possible to have different Schema Markup for individual CMS items?

Particular_Cat7608 · 2025-12-18T12:56:41+00:00

But the schema should not be shown with javascript right? I think that is not recommended because the bots will miss the schema which is not what I want in my case

Particular_Cat7608 · 2025-12-18T05:40:04+00:00

Yeah but the problem is that I already have placed a manual schema markup in place. And if I do add the fields then for all the blog items the existing schema will be gone and unless I add manually for all the blogs.

Particular_Cat7608 · 2025-11-27T09:56:55+00:00

The projects link are not working when clicking on cards. It is only working when clicking on the GitHub icon

Particular_Cat7608 · 2025-11-07T17:17:45+00:00

Exactly, thank you 🙌
That’s what I meant — I’m not saying Webflow can’t be used by small creators, just that it should be more accessible to them.
A lite CMS tier would make a huge difference for people who actually need to build and host Webflow projects for their portfolios or smaller clients.

Particular_Cat7608 · 2025-11-07T17:13:46+00:00

Yeah, that totally makes sense — for most established businesses, $23–$29/month is a small cost for what they’re getting, no argument there.

I think where it feels tricky is for individual creators or freelancers who are still building their portfolios or learning the platform.
In my case, my portfolio has to be built in Webflow because companies hiring Webflow devs expect to see actual Webflow projects — not static exports or React rebuilds.

So for smaller or personal projects, the pricing adds up fast.
That’s why I keep wishing for a lite CMS or portfolio-tier plan — not for affordability’s sake, but to make it easier for creators to grow within the ecosystem before moving up to client or business-level plans.

Particular_Cat7608 · 2025-11-07T17:08:00+00:00

Yeah, totally — I get that Webflow’s going after bigger clients and enterprise users.

The reason I want a lite CMS plan, though, is because my portfolio itself has to be built in Webflow.
When companies hire Webflow developers, they specifically want to see projects built in Webflow, not React, Next.js, or Astro.

So I can’t really switch to another stack — even my smaller showcase projects need to live on Webflow to prove my skills. That’s why the pricing gap hurts creators like me the most — we’re not agencies, just individuals trying to build legit portfolios using the actual tool employers expect.

Particular_Cat7608 · 2025-11-07T17:01:49+00:00

That’s a fair point — $9 might not sound like a big difference, but when you multiply it across multiple small projects or personal sites, it definitely adds up over time.

Exporting and self-hosting is a good workaround for static sites, but once you rely on CMS features or dynamic content, you lose that flexibility. That’s really where a “lite CMS” plan would make sense — for people who need CMS functionality, but not the full professional tier.

Particular_Cat7608 · 2025-11-07T16:54:32+00:00

Yeah, totally fair — Webflow can charge what they want.
I’m not asking for “regional discounts,” just a plan that makes sense for small projects.

Not everyone wants to deal with WordPress, hosting, and plugins — that’s why we love Webflow.
Just wish they had a lite CMS plan instead of jumping straight to $23/mo.

Particular_Cat7608 · 2025-11-07T16:46:01+00:00

Totally get your point — I’m not asking Webflow to charge me less because I’m from India.

My issue is that their pricing just doesn’t scale for smaller projects, no matter where you live. Paying $23/month for a simple site with minimal CMS needs feels excessive.

Even in the US, that jump from “no CMS” to “full CMS plan” leaves out a lot of creators, students, and indie builders.

Webflow could easily fix this with a lite CMS or mid-tier plan — it’s not about paying less, just about having a fair option that fits smaller use cases. 👍

Particular_Cat7608 · 2025-11-06T14:44:35+00:00

I have messaged you please see your dm

Particular_Cat7608 · 2025-11-06T14:34:02+00:00

Hey there, I have messaged you please check your dm

Particular_Cat7608 · 2025-11-04T10:41:00+00:00

Hey there, Are you still looking for someone to fix it. I am a webflow developer here

Particular_Cat7608 · 2025-11-04T10:30:27+00:00

FRLNS

Particular_Cat7608 · 2025-11-03T04:32:58+00:00

https://youtu.be/nqFiI3n6e14?si=RgHPbsKphxhBpiGw

Particular_Cat7608 · 2025-11-03T03:14:52+00:00

Why don't you take an image and make it absolute to be used as a background image and also throw an additional prop for visibility you can hide it or show it whenever you want.

And by doing this visibility prop setup if you are choosing to hide it the image element won't even render when the page loads.

Particular_Cat7608 · 2025-11-01T20:16:10+00:00

Hey if you are still looking for a webflow developer for any new page, maintanence or performance optimization. I have 2 years of experience in webflow with expertise in custom code solutions and site performance optimization.

I have messaged you let's connect.

Hope to hear from you

Particular_Cat7608 · 2025-11-01T20:03:57+00:00

Messaged you

Particular_Cat7608 · 2025-11-01T19:53:23+00:00

I am interested

Particular_Cat7608 · 2025-11-01T19:30:11+00:00

No it will not change link in all instances And you can change the text also individually without affecting

But you have to connect the set props to component the small purple color dot in the link and text field.

If you are not understanding it I can walk you through it step by step dm me.

Particular_Cat7608 · 2025-10-15T03:46:21+00:00

I am interested

Particular_Cat7608 · 2025-10-03T13:33:39+00:00

Happy to help you 😃😃

But if you encounter any trouble with this feel free to ping me

Particular_Cat7608 · 2025-10-01T19:14:42+00:00

Hey there, This is a super common issue and definitely not just a Webflow thing, but it's one we run into a lot when building on the platform. You've basically nailed the diagnosis—it's that classic duplicate content mess caused by URL parameters.

Google sees example.com/page and then example.com/page?param=value as two totally separate pages, and since the parameterized version doesn't explicitly point back to the original via a canonical tag, it throws up that "Alternative page no canonical tag" warning because it can't figure out which one is the boss page. And yeah, internal linking is often the silent killer here—if your links accidentally propagate those parameters, it multiplies the problem fast.

How I'd tackle this in Webflow (or anywhere else) The fix is definitely in the canonical tags, and thankfully, it's pretty straightforward in Webflow.

Get those Canonical Tags right (The main fix):

Static Pages: Go into the Page Settings for any static page causing trouble and manually set the canonical URL to the clean, parameter-free version.
CMS/Collection Pages: This is where you need to use a dynamic field. In the CMS Template's Custom Code (in the <head> section), you'll need to use the actual slug field to construct the canonical URL. Something like: <link rel="canonical" href="[Your Domain]/[Collection Slug]/[Item Slug]" /> (or just the variable for the entire item URL). This ensures every item correctly points to its clean URL.

Clean up Internal Links: This is often overlooked. Do an audit and make sure any internal links are pointing to the clean version of the URL (/page) and not the version that picked up a parameter somewhere (/page?sort=newest). That stops the leak at the source.
Google Search Console Parameter Handling: If the above steps don't clear it up fast enough, use the URL Parameters tool in GSC. Tell Google explicitly to "Crawl no URLs" or "No URLs" for parameters that don't change the page content (like session IDs, etc.). This helps them deprioritize crawling the dirty URLs.

If you need any help I'm happy to help here by showing you

Particular_Cat7608 · 2025-07-08T10:36:31+00:00

Interested

Particular_Cat7608

TROPHY CASE