This article uses a Magento product page as an example to try and make the perfect product page but a lot of the information can be translated to a product page of any e-commerce platform.
When writing a product page
When writing a product page we have to consider the product. Keywords help/show google what the page is about and whether it is a real page and not spam content created by a computer, Google can now tell. Most dodgy techniques no longer work.
We have to write article naturally but there are still methods we can consider when writing content that help SEO. There is no harm in helping google to see your product though and through the correct placement of keywords we can do that
The following should be used at minimum for its keywords
SEOmoz identified the following keyword factors as having most influence on Google's ranking algorithm (the method by which the search engine orders results), for example:Keyword Use in title tag
I will now go over the different sections of the magento product page. I will try to explain what the different bits are and then at the end of each section I will just bullet point what the aims for that section should be. There are some rules that might not be able to be implemented so do not worry if you cannot do everything.
To get an idea of what you should be doing, watch this video:
On Page Optimisation with Magento 1.4 - YouTube
It uses a Firefox plugin called SearchStatus
This will be the products name and by proxy the main keyword for the page. This is slightly different to a normal page where this can be put in artificially. Because you are using this on an ecommerce site the products name is usually enough
The descriptions should be written to be easily read by humans and if they are google will like them. But there are a few things we can do to help google rankings
Short Product Description
Short description is specific to this design package. This description will display at the top of the product page, and in category listings in List view. Magento User Guide, this is used in the local site search and sometimes can be picked up by google (probably if the meta description is not filled in)
Long Product Description
The product‘s description. It will display in the main section of the product page. This section is where you would put in a full description of the product in detail. Magento User Guide
This is the last part of the URL
the first one is using the sku code for the title, this needs to be the actual name of the product so google know what the page is about.
So delete the SKU code out of the URL key and paste the items title in. Magento should then create a correct ‘URL Key’ upon saving.
Meta Description
Meta description is most likely to be used by google for its snippets in the search results. You can have a max of 255 characters including spaces but SEO recommends 140 – 160 so the results look nice on a google search result.
Meta Keywords
Although keywords are not used for search results by the search engines they can be used heavily for search results from the sites own search and sometimes for categorising and filtering products. Normally you would not use these as they would give your competition your keyword research however in the context of ecommerce and the extra functionality you should use them
Meta keywords is a list of keywords for this page or product:
The images have labels that google reads. Images cannot be read by google so we need to add simple labels
Examples are when you have more than one colour of a product; put the colour at the end
These are bad examples
Aspects of a product that need checking
General Tab
Meta Information Tab
Images Tab
The reason for this is that WYSIWYG editors on Joomla by default look for template.css and some will only look for this. When editors can use this file they can apply the default template styling into the WYSIWYG editor window making things look the same as they will display for the end user.
Currently Gantry does not have a template.css and as such WYSIWYG editors have no styling.
Not all WYSIWYG editors have an option to use custom CSS files and indeed other extensions (which I cant think of at the minute) could have the same issue.
For completeness I will outline both ways I can get JCE editor to have the gantry styling in the editor itself just in-case someone mentions that you can use custom CSS files as this feature request is for more than JCE editor.
This is the template.css emulation method I would like to see.
create the file /g5_helium/css/template.css and add the following into it:
@import "../custom/css-compiled/helium_13.css"; @import "../../../media/gantry5/engines/nucleus/css-compiled/joomla.css"; @import "../custom/css-compiled/helium-joomla_13.css"; @import "../custom/css-compiled/custom_13.css";
This effectively loads the gantry styling into the template.css which the WYSIWYG editor can use without affecting any gantry code
In the JCE editor component you can specify the custom css files with the following lines. This method might be a little bit quicker than using the template.css method.
templates/$template/custom/css-compiled/helium_13.css, ../../../media/gantry5/engines/nucleus/css-compiled/joomla.css; templates/$template/custom/css-compiled/helium-joomla_13.css, templates/$template/custom/css-compiled/custom_13.css
This also works, $template is changed for the active template name
templates/g5_helium/custom/css-compiled/helium_13.css, ../../../media/gantry5/engines/nucleus/css-compiled/joomla.css; templates/g5_helium/custom/css-compiled/helium-joomla_13.css, templates/g5_helium/custom/css-compiled/custom_13.css
This is a full collection of the Gantry Template files loaded in the frontend of Joomla.
@import "../../../media/gantry5/engines/nucleus/css-compiled/nucleus.css"; @import "../custom/css-compiled/helium_13.css"; @import "../../../media/gantry5/assets/css/bootstrap-gantry.css"; @import "../../../media/gantry5/engines/nucleus/css-compiled/joomla.css"; @import "../custom/css-compiled/helium-joomla_13.css"; @import "../custom/css-compiled/custom_13.css";
these are not needed for the WYSIWYG
This is one of the last areas wehere wordprss is beating Joomla, but not for long. Page Builders allow a novice to build pages how they wnat them to look without needing to know complex HTML.
Page builders concentrate on building content where as most new template frameworks concentrate on layout such as modules positions. There is some overlap between these two areas. Somethings can be done both in your template framework or within a page builder.
I have gone through all of the Page Builders so I could find to see what they were like and which one I wanted to use. During my research I found there was quite a range of quality and methods for page builders.
These are my assessments of the page builders adn are in order of preference.
Cannot recommend or give an opinion.
These are my more indepth notes i made while assign the various page builders.
These are my notes on DKIM (Domain Keys) and SPF DNS records. These help prevent sending of spam from your server and allows the remote end to verify that the email you sent is from you. There is also DMARC to help prevent spam.
v=spf1 +a +mx +ip4:185.38.45.194 +include:spf.mfilter.dimenoc.com -all
This laptop was an old Dell but had 64-bit processor and 4gb RAM so i upgraded it to windows 10. If you send it to sleep and then wake it up, the screen appears. This is obvously a driver issue.
These are my notes on what I tried using the offcial driver:
Solution
This do not give you all the acceleration of the graphics card but it does not suffer from the blacked out screen issue.
The following error usually occurs sometimes when you move your website with kunena or you change templates.
0 load error: failed to find /home/xxxxxx/public_html/components/com_kunena/template/crypsis/assets/less/crypsis.less

Solutions
This show you the default layout for the gantry Helium Theme (Base Outline) and the section names.

These are the steps I took to create my first template with the layout and module positions I want. Based on the Gantry5 Helium Theme. These are not instructions but someone might find it useful if you are going through the same thought process.
Step 1
Step 2
Step 3
Step 4
Step 5
Outlines are equivalent to Joomla templates and are installed in Joomla as templates. Outlines all inherit from a ‘Base Oultine’ which is not visible in Joomla as a template. This inheritance can be turned off.
It is recommend to alter the ‘Base Outline’ for global changes and if you are only going to have one arrangement then you only ever need to adjust this template. The outline ‘Helium – Default’ is configured to inherit all of the ‘Base – outline’ so it would be this that you use as you joomla template. The ‘Helium – Home – Particles’ is just a demo showing particles (which only exist in Gantry) functioning on a Gantry template/outline.
Once you have loaded the layout in outlines the edits to the file /custom/layouts/example1.yaml will not work as this is only a preset file and not the actual the layout/template file.
When you add a layout from a preset what happens is:
You can edit these files and you layout will change.
These are styles that are accessible via the dropdown menus in gantry admin should as module styling.