Capeweddings.co.za SEO report

1. Unexpected tags.

There are unexpected tags in body of portlets and addcontentpage objects. Usually, the structure of the HTML document contains some mandatory tags that are inserted in a defined order. Unexpected tags broke html structure of documents in this case.

<title>Untitled Document</title>

<meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1">

http://www.capeweddings.co.za/portlet.2006-04-13.5045397382/base_edit
http://www.capeweddings.co.za/customers/vrede_lust/addcontentpage.2006-05-16.1291430317/base_edit
This could be because of content manager mistake (wrong copy/paste from Macromedia Dreamweaver).

2. Duplicated content

about us | to advertise | contact us | disclaimer
links are relative instead of absolute. This lead to duplicated content issue. It is very bad for Google.
to advertise Link must go to http://www.capeweddings.co.za/to-advertise at every page.
Currently, if you are located on any deep level of your site .e.g.
http://www.capeweddings.co.za/customers/vrede_lust/addcontentpage.2006-05-16.1291430317/
then to advertise link is
http://www.capeweddings.co.za/customers/vrede_lust/addcontentpage.2006-05-16.1291430317/to-advertise
Plone preview correct page because of Zope acquisition feature, but it is bad for search engines.
Thats why Google index many pages withe same content.

3. Display View

Site structure is broken. The url http://www.capeweddings.co.za/customers is available for Google .
Links at http://www.capeweddings.co.za/customers lead to empty pages like http://www.capeweddings.co.za/customers/vrede_lust/.

Suppose your are located here here http://www.capeweddings.co.za/customers/vrede_lust/addcontentpage.2006-05-16.1291430317/folder_contents
Using such ID like addcontentpage.2006-07-18.1117819954 in URL is not good for search engines.
In case of capeweddings.co.za it must be mustn't be used. Site structure is not polished because
http://www.capeweddings.co.za/customers/vrede_lust/ includes empty page, thus one of the levels is empty. It would be much better if
http://www.capeweddings.co.za/customers/vrede_lust/ preview content of
http://www.capeweddings.co.za/customers/vrede_lust/addcontentpage.2006-05-16.1291430317

Currently addcontentpage.2006-05-16.1291430317 object is created by custom AddContentPage content type.
Currently this object can't be set as default page for http://www.capeweddings.co.za/customers/vrede_lust/ folder.
Look at our tutorial about Display View Feature.
Developers should fix it. So the page http://www.capeweddings.co.za/customers/vrede_lust/addcontentpage.2006-05-16.1291430317
should be available under the http://www.capeweddings.co.za/customers/vrede_lust/url. All links should lead to http://www.capeweddings.co.za/customers/vrede_lust/ instead of http://www.capeweddings.co.za/customers/vrede_lust/addcontentpage.2006-05-16.1291430317

The same is with all other objects created with AddContentPage content type:
Suppose you are located here http://www.capeweddings.co.za/customers/remould/folder_contents then
Studio One object (addcontentpage.2006-07-18.1117819954 id) should be able to set as default Display View item.
So the page http://www.capeweddings.co.za/customers/remould/addcontentpage.2006-07-18.1117819954
should be available under the http://www.capeweddings.co.za/customers/remould/ url. Links should go to http://www.capeweddings.co.za/customers/remould/ instead of http://www.capeweddings.co.za/customers/remould/addcontentpage.2006-07-18.1117819954

4. unexpected tags in portlets

Portlets with unexpected tags. If you insert portlet e.g. sponsored links then unexpected tags are available in HTML

DOCTYPE

html

head

title

body

These tags broke normal structure of html documents. Search engine robots can't index pages correctly.

5. not closed tags.

Html code is not clean. There are mistakes with not closed tags.

6. Div tags in wrong places

DIV tags are used too much in wrong places (e.g. <tr> tag inside <div> tag)

7. Empty Div tags

there are a lot of empty DIV tags in HTML like <div></div>

8. AddContentPageReference content type

Suppose we are in Accessories section created with AddContentPage content type.
http://www.capeweddings.co.za/for-the-bride/accessories/
AddContentPageReference content type is used here to create links (references) to customers pages.
http://www.capeweddings.co.za/for-the-bride/accessories/addcontentpagereference.2006-06-13.8996535153/base_edit
Links must go to
http://www.capeweddings.co.za/customers/hdp_creating/
instead of
http://www.capeweddings.co.za/customers/hdp_creating/addcontentpage.2006-05-22.7665872578
Plone developer should fix AddContentPageReference content type.
According to above 3. Display View item addcontentpage.2006-05-22.7665872578 should be set as default DisplayView for hdp_creating object.

9. ALT properties

The following img tag <img src="capeweddings/search_here" width="131" height="27"> should have Alt property.
Many pages doesn't have ALT property in IMG tag.
http://www.capeweddings.co.za/customers/vrede_lust/addcontentpage.2006-05-16.1291430317

10. H1 tags

addcontentpage content type has Title field, but it doesn't preview it on pages with H1 tag. I don't see it in page html source. H1 tag with text related to page content is very important.
Usually it is visible at Header of articles in Page, Folder content types. Designer should decide where to preview Title field with H1 tag. It can be small, but it must be available.

11. Titles

Titles of every page are not optimized for Search engines (screenshot 1, screenshot2). It can be done with qSEOptimizer Plone product. Titles should include 5-10 words with keyword phrases important for your site.

12. Bride pages

Links like http://www.capeweddings.co.za/bride-of-the-year/january/addbridepage.2006-06-09.5448976112 should be changed to links like http://www.capeweddings.co.za/bride-of-the-year/january/alisonochse or http://www.capeweddings.co.za/bride-of-the-year/january/alison-ochse

13. honeymoons

Currently folder
http://www.capeweddings.co.za/honeymoons has broken structure links like

http://www.capeweddings.co.za/honeymoons/Shamwari%20Game%20Reserve/addcontentpage.2006-07-03.5453162896 should be changed to
http://www.capeweddings.co.za/honeymoons/Shamwari%20Game%20Reserve/
or even to
http://www.capeweddings.co.za/honeymoons/shamwari-game-reserve/

14. bridal alerts IDs

http://www.capeweddings.co.za/bridal-alerts/addcontentpage.2006-09-18.3496902700
should be changed to smth
http://www.capeweddings.co.za/bridal-alerts/july-2006

Usability of content manager workflow

Strange workflow

Strange situation is with
http://www.capeweddings.co.za/bridal-alerts
http://www.capeweddings.co.za/bridal-tools/
you have there AddContentPageReference with links to AddContentPage located inside bridal-alerts. You have 3 AddContentPages and 3 AddContentPageReference for every AddContentPages. I don't know Why you need here AddContentPageReference object, workflow is mixed up and it is not easy to manage it. You should simply list AddContentPage objects without AddContentPageReference.

Workflow

You should have straight vision (workflow) how you add pages. In one place you add
http://www.capeweddings.co.za ->AddCategory -> AddCategory -> AddContentPage
http://www.capeweddings.co.za/honeymoons/Blue%20Bay%20Beach%20Resort
in other place you add
http://www.capeweddings.co.za/customers/body_beautiful
http://www.capeweddings.co.za/ -> Folder ->Â Folder -> AddContentPage

Site structure

You should describe why the site structure is so strange Links here
http://www.capeweddings.co.za/special-features/
goes to customers subfolder special_features
like
http://www.capeweddings.co.za/customers/special_features/valentine-jan06
and pages
http://www.capeweddings.co.za/special-features/ring/addcontentpage.2006-06-30.8731188086
They all should go to pages like
http://www.capeweddings.co.za/special-features/ring/
http://www.capeweddings.co.za/special-features/valentine-jan06