Hotclutch

Sorry, i think you misunderstand. The default theme consists of a template set right ? I am referring to the number of templates in the template set.

Is there a header and a footer template ? Or can the header and footer of each page be customised in their respective templates ? Can php conditions be used in templates ?

how many templates does the default theme have ?

I should add the first thing of interest to me in the new version will be URLs and their structure. I think any shopowner with a SEO position to protect would be.

Can the team page be updated to clarify people's roles now under new management ? Some of those people have not logged into the forum for years now. Who are the moderators and who are part of the developing team ? It would be nice if an announcement could be made wrt the support of the official osCommerce versions that are still available and being used, at least until the new release is made available. Even after the new release it would be a while before any shop owner could migrate to the new release, depending on whether the release will be one that is production ready or would still require sorting out of teething problems. In the past people who posted for support were treated with disrespect and referred to a closed club for support. In any event good luck with the new vision for osCommerce and the anticipated new release.

Add-On or Plug-In. There are other free and opensource projects that use these names for extensions so i would call them that. Also "contribution" would be a fine description for the free extensions like in the past.

Product pages are missing the breadcrumb trail, those are useful to both customers and search engines for SEO.

Looks nice, nothing stands out as being wrong.

Why assume a problem with your site when most economies have changed due to Covid ? What's the demand for the products you sell now in Covid conditions ? Anyway, I don't see any major issues with the site. If it was driving traffic before it should still do so now, nothing significant has changed recently in the online world. 1) You could assign better more descriptive titles to your pages. 2) Your use of the rel="canonical" meta tag is wrong. Probably Google is saving you from yourself and ignoring it. 3) You have blank meta description tags on a lot of pages.

The warnings are related to the use of structured data which is hard coded into the product_listing.php module file.

That's invalid syntax. You cannot redirect query strings like that in htaccess. You can do more harm than good when experimenting with htaccess like this, my suggestion is not to make entries in htaccess until the code you put is fully tested by someone who knows htaccess rules (which are complex). Just do this for now.

$optional_rel_prods_content .= ' <div class="card" itemprop="isRelatedTo" itemscope itemtype="http://schema.org/Product">'; $optional_rel_prods_content .= ' <meta itemprop="url" content="' . tep_href_link('product_info.php', 'products_id=' . $optional_rel_prods_values['pop_products_id_slave']) . '" />'; switch (MODULE_CONTENT_PRODUCT_INFO_RELATED_PRODUCTS_HEIGHT_MODE) { case 'Equal Height': $optional_rel_prods_content .= ' <div class="card-body text-center">'; break; case 'Fixed Height': $optional_rel_prods_content .= ' <div class="card" style = "height:' . MODULE_CONTENT_PRODUCT_INFO_RELATED_PRODUCTS_HEIGHT_VALUE . 'em;">'; break; case 'None': $optional_rel_prods_content .= ' <div class="card">'; break; } Can't be right. You already have: $optional_rel_prods_content .= ' <div class="card" itemprop="isRelatedTo" itemscope itemtype="http://schema.org/Product">'; then you have a case where; case 'None': $optional_rel_prods_content .= ' <div class="card">'; break; which means somewhere in your output you could end up with <div class="card" itemprop="isRelatedTo" itemscope itemtype="http://schema.org/Product"><div class="card">

Someone posted a similar type problem just a few posts back from yours. You need to find where in your script it is generating these parameters and then fix it, by adding code possibly. Even if the problem is already fixed / removed, google will continue to crawl the URLs indefinitely, until you put a 301 redirect on URLs of that type. A quick fix for Google would be to ignore those parameters in webmaster tools, MSN also has an ignore parameter tool.

If you are redirecting index,php to the root, then you don't want to be submitting that URL in a sitemap. You should be submitting the root URL. If it's not easily possible with code, then hopefully it will be possible just to remove that entry form the sitemap, Google will still index the root URL. Also webmaster tools will alert with an error if you do have index.php in a sitemap, whilst there is a 301 redirect on it. Any links in your script should be changed over to the root domain URL, otherwise you're linking to a perpetual redirect.

does not make sense. Once you delete the product, there's nothing in the code that would cause that. Unless you have something else going on.