Was not sure whether to post this under future enhancements or bug reports.

The unload event is problematic for most browsers because it messes up the bfcache. Google is starting to bark more and more when this event is used. Obviously, they recommend the pagehide event instead.

I am curious if this is something that's going to be addressed since it involves going into some AbleCommerce functionality. They are also becoming very strict on how the beforeunload event is also used.

Everything today from a Google perspective is about speed from a mobile device, using outdated events just messes up any type of optimization.

If you require additional information, please let me know, but Google has a tremendous amount regarding this. Hopefully, maybe in a next release this can be addressed and start moving some of these functions into the newer technology that is being used today and recommended by Google.

Please reach out to me if you require any additional info.

Like always, many thanks,
-Ray

I think it might be a good idea to try to use the pagehide event instead to try to meet this requirement. Since you can do better testing on your end on how this might affect other factors, I decided not to make the change myself.

It might be a good idea to attempt to test this for a future version. Google is becoming very specific in what they're looking for and this will impact ranking.

On another note, I need to address the Canonical URL issue again. I don't think you guys understand how serious this is. And anyone who uses AbleCommerce is penalized because the homepage creates an entirely different page called default.

Now that we're undergoing even further SEO optimization, we have run various SEO tools against other AbleCommerce websites, and all these tools agree that this is not correct. You can run these tools yourself and come to the same conclusion. No one using your software benefits from this.

All the tools have the same warning "The specified canonical link points to a different page.", and because this is happening on the main index page, AbleCommerce users are going to suffer.

On my post dated 29 days ago, your recommendation was "objectURL should not be equal to "default" = (!objectUrl.Equals("Default")"

Why doesn't this work?

I'm still using " (!objectUrl.Contains("Default")))", which works perfectly as long as default is not included in any other url.

Await your feedback—thanks

---

Just in case you need to see the full contents of the meta-tag file. Yes I know I'm hard coding the webURL, this is intentional.

@{
string description = ViewBag.MetaDescription ?? string.Empty;
string keywords = ViewBag.MetaKeywords ?? string.Empty;
string objectUrl = ViewBag.ObjectUrl ?? string.Empty;
string webUrl = "https://www.myradiomall.com";
}

<meta http-equiv = "content-language" content = "en">

@if (!string.IsNullOrEmpty(description)) {
<meta name="description" content="@description">
}
@if (!string.IsNullOrEmpty(keywords)) {
<meta name="keywords" content="@keywords">
}
@if (!string.IsNullOrEmpty(objectUrl) && (!objectUrl.Contains("Default"))) {
<link rel="canonical" href="@objectUrl" />
}
@if (objectUrl.Contains("Default")) {
<link rel="canonical" href="@webUrl" />
}

Edited by user Friday, July 8, 2022 8:18:43 AM(UTC)  | Reason: Not specified

Thank you for your explanation, it makes sense and I should've figured it out on my own.

Going back to the original concern with the unload event. In your opinion, do you think changing any appearance of the "UNLOAD" event to "PAGEHIDE" would have any destructive effects with normal functions?

-Ray

Edited by user Saturday, July 9, 2022 9:18:51 AM(UTC)  | Reason: Not specified

Thank you so much for your feedback.

We are doing a structural review for better SEO purposes. We should get to this point sometime late next month. I will do my tests, then report back.

But since this is an outdated technique, and not recommended in today's times, in might be beneficial to look for a better way to do this in a future upgrade.

Many thanks,
-Ray

Edited by user Wednesday, July 13, 2022 1:30:43 PM(UTC)  | Reason: Not specified