Forums / Setup & design / Search Engine Optimisation - more efficient use of the title tag

Search Engine Optimisation - more efficient use of the title tag

« 
Previous topic
|
Setup & design
|
Next topic
 »
Author Message

steve walker

Wednesday 09 June 2004 8:24:05 am

Hi there,

This is more a discussion request than a support one.

Good Search Engine Optimisation is heavily influenced by good marrying of the <title> keywords with the keywords in the body. Its always recommended you change the title tage dependent on the page it referes to. So, for instance, when a user goes to your product page selling 'icecream', 'icecream' is referred to in the title tag, and greatly improves the chances of that product page doing well in Search Engines for users searching on this term.

I'm not trying to teach anyone to suck eggs here - but an extension or module that allows the title tag to be specified when necessary on a per class basis is required.

Would it not be easy to have two components that make up the page title, the existing one, and a second more specific one? So that the overall title is 'my webshop etc' which comes from the global configuration, and then a second more specific '- tastey icecreams' - with this being lifted from the product class...

So the header info in the page has to take information that is derived from the main content of the page.

Is this possible, and has anyone else been wondering about this?

Regards, Steve.

http://www.oneworldmarket.co.uk

Ekkehard Dörre

Wednesday 09 June 2004 11:55:32 am

http://www.coolscreen.de - Over 40 years of certified eZ Publish know-how: http://www.cjw-network.com
CJW Newsletter: http://projects.ez.no/cjw_newsletter - http://cjw-network.com/en/ez-publ...w-newsletter-multi-channel-marketing

steve walker

Thursday 10 June 2004 12:04:34 am

Ekke,

Many thanks for the code.

Kind regards, Steve.

http://www.oneworldmarket.co.uk

Paul Forsyth

Thursday 10 June 2004 12:52:04 am

I have a few problems maintaining a good title. Most of it stems from the fact that a node is not always available and getting a title is difficult.

I filed this bug a while back describing the problem:

http://ez.no/community/bug_reports/always_have_a_valid_node_object_available

I have to perform some checks and put in code accordingly, eg:

{let my_node=0}

{section show=is_set($DesignKeys:used.node)}
  {set my_node=fetch(content, node, hash(node_id, $DesignKeys:used.node))}
{/section}

<title>VisionWT
{switch match=$module_result.uri}
  {case match='/user/register'}
- Register new user
  {/case}
  {case match='/user/login'}
- Login user
  {/case}
  {case match='/user/forgotpassword'}
- Forgot Password
  {/case}
  {case match='/shop/confirmorder'}
- Confirm Order
  {/case}
  {case}
    {section show=is_set($search_text)}
- Search Results
    {section-else}
      {section show=ne($my_node, 0)}
- {$my_node.name}
      {/section}

    {/section}
  {/case}
{/switch}
</title>
{/let}

It isn't ideal because you have to add more cases to cover every bit of ez publish that doesnt have a node. Though, in my haste i may have overlooked something. Are there better alternatives?

paul

--
http://www.visionwt.com

Ekkehard Dörre

Wednesday 23 June 2004 2:58:48 pm

... for Meta Description tag look at:
http://ez.no/community/forum/developer/meta_description_tag

Greetings, ekke

http://www.coolscreen.de - Over 40 years of certified eZ Publish know-how: http://www.cjw-network.com
CJW Newsletter: http://projects.ez.no/cjw_newsletter - http://cjw-network.com/en/ez-publ...w-newsletter-multi-channel-marketing

eZ debug

Timing: Jan 19 2025 20:11:30
Script start
Timing: Jan 19 2025 20:11:30
Module start 'content'
Timing: Jan 19 2025 20:11:30
Module end 'content'
Timing: Jan 19 2025 20:11:30
Script end

Main resources:

Total runtime0.1817 sec
Peak memory usage2,048.0000 KB
Database Queries141

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0066 589.2266180.7969
Module start 'content' 0.00660.0047 770.023498.1016
Module end 'content' 0.01130.1703 868.1250527.2031
Script end 0.1816  1,395.3281 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00351.9397200.0002
Check MTime0.00130.7121200.0001
Mysql Total
Database connection0.00090.499810.0009
Mysqli_queries0.131872.57161410.0009
Looping result0.00140.76391390.0000
Template Total0.169993.510.1699
Template load0.00100.529610.0010
Template processing0.168992.976410.1689
Override
Cache load0.00070.365510.0007
Sytem overhead
Fetch class attribute can translate value0.00090.475110.0009
XML
Image XML parsing0.00030.164610.0003
General
dbfile0.00703.8739200.0004
String conversion0.00000.002930.0000
Note: percentages do not add up to 100% because some accumulators overlap

CSS/JS files loaded with "ezjscPacker" during request:

CacheTypePacklevelSourceFiles
CSS0extension/community/design/community/stylesheets/ext/jquery.autocomplete.css
extension/community_design/design/suncana/stylesheets/scrollbars.css
extension/community_design/design/suncana/stylesheets/tabs.css
extension/community_design/design/suncana/stylesheets/roadmap.css
extension/community_design/design/suncana/stylesheets/content.css
extension/community_design/design/suncana/stylesheets/star-rating.css
extension/community_design/design/suncana/stylesheets/syntax_and_custom_tags.css
extension/community_design/design/suncana/stylesheets/buttons.css
extension/community_design/design/suncana/stylesheets/tweetbox.css
extension/community_design/design/suncana/stylesheets/jquery.fancybox-1.3.4.css
extension/bcsmoothgallery/design/standard/stylesheets/magnific-popup.css
extension/sevenx/design/simple/stylesheets/star_rating.css
extension/sevenx/design/simple/stylesheets/libs/fontawesome/css/all.min.css
extension/sevenx/design/simple/stylesheets/main.v02.css
extension/sevenx/design/simple/stylesheets/main.v02.res.css
JS0extension/ezjscore/design/standard/lib/yui/3.17.2/build/yui/yui-min.js
extension/ezjscore/design/standard/javascript/jquery-3.7.0.min.js
extension/community_design/design/suncana/javascript/jquery.ui.core.min.js
extension/community_design/design/suncana/javascript/jquery.ui.widget.min.js
extension/community_design/design/suncana/javascript/jquery.easing.1.3.js
extension/community_design/design/suncana/javascript/jquery.ui.tabs.js
extension/community_design/design/suncana/javascript/jquery.hoverIntent.min.js
extension/community_design/design/suncana/javascript/jquery.popmenu.js
extension/community_design/design/suncana/javascript/jScrollPane.js
extension/community_design/design/suncana/javascript/jquery.mousewheel.js
extension/community_design/design/suncana/javascript/jquery.cycle.all.js
extension/sevenx/design/simple/javascript/jquery.scrollTo.js
extension/community_design/design/suncana/javascript/jquery.cookie.js
extension/community_design/design/suncana/javascript/ezstarrating_jquery.js
extension/community_design/design/suncana/javascript/jquery.initboxes.js
extension/community_design/design/suncana/javascript/app.js
extension/community_design/design/suncana/javascript/twitterwidget.js
extension/community_design/design/suncana/javascript/community.js
extension/community_design/design/suncana/javascript/roadmap.js
extension/community_design/design/suncana/javascript/ez.js
extension/community_design/design/suncana/javascript/ezshareevents.js
extension/sevenx/design/simple/javascript/main.js

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1pagelayout.tpl<No override>extension/sevenx/design/simple/templates/pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs