We've released SC/A 2025.1.30, which, notably, inc...
# suitecommerces
Steve Goldberg
07/22/2025, 1:09 PMWe've released SC/A 2025.1.30, which, notably, includes a bug fix for the SEO canonical URL having incorrect URL parameters on search and category list pages. It now uses a setting in the configuration record under Shopping Catalog > Facets SEO > Options, where you can choose which parameters you do want to include; unsetting all of them prevents them all from being included, which is probably what you want by default.
✅ 1
💜 1
👀 1
m
Martin
07/22/2025, 1:59 PMSCA 2025.1 is released?
s
Steve Goldberg
07/22/2025, 2:00 PMYes
m
Martin
07/22/2025, 2:00 PMDo you have the bundle ID? I was not able to find it using the search, thanks!
s
Steve Goldberg
07/22/2025, 2:01 PM562977
m
Martin
07/22/2025, 2:01 PMThanks Steve!
s
Steve Goldberg
07/22/2025, 2:01 PMIt may not have been shared to your account
m
Martin
07/22/2025, 2:02 PMI found it with that ID, thanks!
d
Diego Gallo
07/22/2025, 6:24 PMHi @Steve Goldberg,
I guess that SEO Page Generator had modifications to have the capability to work with these new features right? At platform level I mean.
We are in current discussions with Support about various issues with no logical explanation (unless the behavior of the SEO page generator changed) we are facing with some customers.
I guess you wouldn't have released changes to the seo page generator without a PFCN right? But in case that happened, can you please let me know which exact behaviors changed? That'd make our lives easier to give feedback back your way and continue to improve the product all together
s
Steve Goldberg
07/23/2025, 10:35 AMI'm not aware of any specific changes that were made to the SEO page generator recently. If you could be more specific about the changes you think have been made, I could try to corroborate them
d
Diego Gallo
07/24/2025, 12:45 AMWorking on defect 834367, I was told there were changes to the behavior of the SEO Page Generator and the support/product teams are waiting on my feedback on the behaviors and dates I am seeing. I am also not aware of the changes, but they mentioned there were actual changes - and by looking at the debugger wording (now it says "prerender v1" which wasn't the wording a month or so ago) it is clear that it is being modified somehow.
@Steve Goldberg
I'll keep ya posted on whatever that comes up on that defect, but if you keep an eye on it you should be able to dig more internally 🙂
Thanks for all the help, Steve, appreciate it
Diego Gallo
07/24/2025, 1:06 AMoh BTW there is another thing that's been happening and I suspect it might be related with the behavioral changes: some bot traffic is now being reported in GA4 and that wasn't the case.
The reason I suspect this might be related is because GTM (where ga4 runs) is by design excluded from the seo page generator or at least it was when I was leading that project.
The fact that we are seeing bot traffic in GA4 means we are serving a JS version of the site to more bots, or that we are rendering JS on the SEO page generator that used to be excluded.
OR it could be something else for sure! That's why I'm presenting this as an hypothesis, not a fact.
s
Steve Goldberg
07/24/2025, 10:36 AMnow it says "prerender v1" which wasn't the wording a month or so agoYah, we're working on a v2, and we wanted an easy way to mark which version produced which content
Steve Goldberg
07/24/2025, 10:36 AMI'm not aware of any material changes to v1 that would mess with rendering
2 Views