Top 7 SEO mistakes found in Drupal sites
https://www.zyxware.com/sites/default/files/styles/user_image/public/pictures/Z_ribbon.png?itok=va3zzVQA
BY webmaster
6 years ago
Drupal
2
comments comment

SEO is the bread and butter of any website and Drupal is no exception. The rules of SEO are pretty much the same in a Drupal as on any other CMS or plain HTML website but there are some SEO mistakes that are unique to Drupal like the ones found in our list of the Top 6 SEO mistakes found in Drupal sites. Also checkout the Top 6 SEO modules for Drupal to achieve even better Search Engine rankings. If you would like to ensure that all SEO aspects are taken care of in your Drupal site do get in touch with us

Clean URLs not enabled or not configured correctly

Clean URLs are URLs which do not contain any query strings and contain only the path to the resource. Clean URLs are better from an SEO perspective than ‘Unclean’ URLs as they tend to provide better readability and indicates better content structuring. Clean URLs also tend to allow webmasters to make the URL permanent as it does not expose the underlying implementation details. So ensuring Clean URLs is a good practice both from an SEO perspective, a semantic perspective and to a certain extent a security perspective.

Hardcoded links to non-aliased URLs

Drupal uses “nodes” to refer to content i.e http://www.example.com/node/183. This is not an issue for browsers and servers as it is for users as it is totally illegible to them to what the page is standing for. Using Hardcoded links (links in the node/nid format) instead of an aliased URL like site.com/history-of-drupal in templates and custom modules is not very good SEO. Drupal has a feature called URL aliasing that provides meaningful names to these standard URLs. This would allow for better ranking on these keywords for the pages.

Clean URLs enabled without Global Redirect.

It is a fact that Search Engines do not like duplicate content. If you have enabled Clean URL's on your Drupal website then nodes will be available both from their node/nid path as well as the aliased path leading to the same content becoming available from two different URLs. This can be fixed by installing the Global redirect module which when configured correctly can redirect unaliased paths to the corresponding aliased paths.

Note: You might like to checkout our list of Top 10 Performance mistakes in Drupal

Changing node path without creating a redirect

If you have changed the url of a node in your Drupal site which has incoming links it will affect your search engine rankings negatively as it is bad SEO to have broken links. This can be solved by installing and setting up the Path Redirect Module which helps you redirect from an old url on your Drupal site to the new path. You can also decide to set the URL for the new node as the same as the old node using url alias.

Having a really slow Drupal site

If your Drupal site is slow - takes more than 2 seconds to load, its not only bad for SEO but your visitors will also be put off by it. Drupal has a variety of caching systems to help speed up your website. Boost is one such Drupal caching system that is pretty effective in improving site performance.

Robots.txt file

There is a serious SEO flaw in the standard robots.txt file of Drupal. It is set to exclude the /sites/ folder from being crawled by Search Engines. This is the folder where Drupal stores a sites images. Images with the correct alt attribute can boost your Search Engine rankings. So if your robots.txt file is not corrected you are missing out on a valuable area in SEO. Drupal has corrected this file from versions 6.20 onwards, but if you are running an older version you should correct this file or alternatively update your drupal installation.

Ignoring good analytics software.

Even if you get the basics of SEO right by using the right search terms and keywords and having quality content on your site, you need to get real time data of how your site performs to make minute adjustments. A good Analytics package like Google Analytics can gives you a good idea of how SE Optimized your website by giving you reports of traffic to your website, average page load times, the demographics of your users, average page bounce rates, the number of unique and recurring visits to your sites and a whole lot more which can alert you to potential areas of improvement.


RELATED ARTICLE

close

on 01st January 2008 / by webmaster
We have added a few new modules to our site recently. Two of these are the StumbleThis module and the DiggThis module. Drupal already had a DiggThis module available for download but there was no StumbleThis module. StumbleUpon has been a popular source of traffic for zyxware.com and we wanted users to have an option to add any of our pages to their StumbleUpon favorites. So we created our own StumbleUpon module. Normally people use stumbleupon toolbar to stumble websites. However when the toolbar is not enabled this provides an easy way to add the URL to the stumbleupon favorites. The StumbleThis button will be shown on the left of the content inline. Positioning of the StumbleThis button can be controlled by the weight option in the admin menu. By setting a negative value you can have the button displayed on top of the post while a positive value will take it to the bottom of the post.Click here to download the StumbleThis module for Drupal. The module has been tested with Drupal 5.1. Please use the comments form below if you have any questions or suggestions. Open Source Web Development Drupal Blogging Free Software Drupalgive Leave a reply Your email address will not be published. Required fields are marker * Sean (not verified) access_time 20 Jun 2019 - 17:07 Hi there, I uploaded the files, enabled the modules to use SU, and now I see the link, but there is no icon... How can I fix this? Thanks, Sean webmaster access_time 20 Jun 2019 - 17:07 In reply to Icon doesn't show by Sean (not verified) What do you see when you view the source? Search for stumblethis_button and you should be able to see the code for the image and the URL. Then you should be able to troubleshoot from there. Juicy Couture Addict (not verified) access_time 20 Jun 2019 - 17:07 thanks for the post. would love to hear more of you. by the way, drupal's really popular nowadays as it has easy and fast features. you agree with me? thanks. Add new comment
more_horiz
close

on 16th January 2008 / by webmaster
Most webmasters do not realize this, but a lot of the content on lot of websites can be accessed from multiple URLs. A simple example would be where www.example.com and example.com leads to the same page. This is a fatal mistake in Search Engine Optimization and search engines penalize you for duplicate content. The correct configuration would be where the above two urls will lead you to the same page but example.com will redirect you to www.example.com with a 301 (Moved permanently) status which will not result in search engines penalizing the page. It is very easy to configure 301 redirects using Apache .htaccess file and the process is the same for a Drupal installation also. The article is relevant only to those webservers running Apache. There are two ways in which you can issue a 301 redirect using .htaccess on an Apache Webserver. One is using a mod_alias Redirect statement and the other is using the mod_rewrite Rewrite statements. Redirect statements take paths and assign corresponding paths to be redirected to while rewrite statements take regular expression patterns and associate paths where matched urls have to be redirected to. When you install Drupal, it will automatically insert statements in the .htaccess file that will allow you to redirect www.example.com to example.com or vice versa. The only thing you have to do normally would be to uncomment the statements corresponding to your preference of accessing your domain ie with or without the www part. # If you want the site to be accessed WITH the www. only, adapt and # uncomment the following: # RewriteCond %{HTTP_HOST} ^example\.com$ [NC] # RewriteRule .* http://www.example.com/ [L,R=301] # # If you want the site to be accessed only WITHOUT the www. prefix, adapt # and uncomment the following: # RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC] # RewriteRule .* http://example.com/ [L,R=301] There is however a problem with the above redirections in that they lose the rest of the URL. Say for example if you try to access example.com/somepath and your configuration is to use the www prefix the user will be redirected to www.example.com but the somepath part will be lost. This can easily be rectified by the following small change in the Rewrite Rule # For the first option you can use the following rewrite rule # RewriteRule (.+) http://www.example.com/$1 [L,R=301] # # whereas for the second you can use the following rewrite rule # RewriteRule (.+) http://example.com/$1 [L,R=301] These modifications will ensure that the user will be redirected to the correct page with or without the www prefix and without losing on your page ranks. So make the necessary modifications and make sure that you can access the pages to your site using only one version of the URL. The above configuration of .htaccess should be used not just for Drupal websites but for all websites. If however your problem is the reverse, ie you don't have pages corresponding to the URLs that the user typed, ie if you are getting lot of 404 errors (page not found errors) and users are thrown to the default Page not found page, you can try installing the Drupal Search404 Module to search for the keywords in the URL and show relevant results to the user. You can read more about apache mod_alias and apache mod_rewrite at the apache official documentation Apache mod_rewrite and Apache mod_alias Web Development Drupal SEO Drupal Planet Leave a reply Your email address will not be published. Required fields are marker * Anonymous (not verified) access_time 20 Jun 2019 - 17:07 Hello. I'm trying to make example.com show as www.example.com, and I'm running into difficulties. I'm on Apache 2.0 and using the following lines in my httpd.conf file: RewriteEngine on RewriteCond %{HTTP_HOST} ^xxxxxxxxxx\.com$ [NC] RewriteRule ^(.*)$ http://www.xxxxxxxxxx.com/$1 [L,R=301] When I go to http://xxxxxxxxxx.com, I get http://www.xxxxxxxxxx.com (as expected). However, when I go to http://xxxxxxxxxx.com/node/1 (it's a Drupal site), I get a 404 thrown and the URL changes to xxxxxxxxxx.com/var/www/drupal/node/1. Same thing with www.xxxxxxxxxx.com/node/1. Any suggestions? I want to run without Drupal's .htaccess file (instead incorporating these calls into my httpd.conf file). webmaster access_time 20 Jun 2019 - 17:07 In reply to Rewrite including filesystem path by Anonymous (not verified) I think the problem is with the base path which results in the redirection to /var/www/ part. The best approach I would think is to start with drupal htaccess and then strip out parts and move to httpd SNVC (not verified) access_time 20 Jun 2019 - 17:07 This is definitely a good guide. Thanks for this. wellyson access_time 20 Jun 2019 - 17:07 This is really nice and helpful. Add new comment
close

on 07th January 2008 / by webmaster
We have volunteered to take up the maintenance of a very useful Drupal module - Search404. As of today we are the official maintainers of this very useful Drupal module. We know that this is going to be a challenge for us, being a young company and with a young team. But we do feel that it is our responsibility to give back to the Drupal community at least some part of what it has given us. About Search404 Module Normally when a user types in an incorrect URL in a site the web server will issue a 404 error (page not found error) and correspondingly redirect you to a 404 error page. If there is no custom 404 page on the server the browser will show the 404 page not found error to the user. This could happen when either the user types in the URL himself or he clicks on a URL incorrectly typed in another page. Another case when such errors happen is when content is deleted or moved in a site and the search engine indices have not been updated to reflect the removal or change. The web crawlers of search engines on getting a 404 error will take out the URL from their indices. The normal web user will however be totally lost when he sees the 404 error page. This is especially true if the user came from a search result page and has no idea about the navigational structure of the site or the content organization of the site. Drupal however shows its own 404 error page and avoids showing the grotesque, default 404 page that would otherwise be shown by the browser to the end user. Even this 404 error page is only a bare page with just the information that the page cannot be found. The Search404 module intelligently does a search for the terms in the URL while still issuing a 404 error. This will ensure that the URL gets taken out from the search engine index at the same time making sure that the user is given some options in terms of navigating in the site. You can check out how this works by clicking on the following non-existant URL Drupal Modules from Zyxware. Even though the page does not exist you get what you wanted to get to. If you have any questions, issues or suggestions regarding this module you can either post them as comments to this page or post your issues at the Search404 Module at Drupal.org. Open Source Web Development Drupal Leave a reply Your email address will not be published. Required fields are marker * ian douglas (not verified) access_time 20 Jun 2019 - 17:07 I notice your updates on the Drupal modules page has some patch files, but they are patches for an older version of the 5.x branch of search404. Do you have any expectation on when a version for Drupal 6 will be ready? webmaster access_time 20 Jun 2019 - 17:07 In reply to when will search404 for drupal 6 be ready? by ian douglas (not verified) Hi Ian, We are currently working on moving Search404 to Drupal 6. The port has already been done and we should have a release up on drupal.org by tomorrow or worst case by monday. Cheers Anoop John Team Zyxware Dejan (not verified) access_time 20 Jun 2019 - 17:07 In reply to when will search404 for drupal 6 be ready? by ian douglas (not verified) I think that's been up for a while... did you check the download page? Add new comment
Leave a reply
Your email address will not be published. Required fields are marker *

Filtered HTML

  • Web page addresses and email addresses turn into links automatically.
  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type='1 A I'> <li> <dl> <dt> <dd> <h2 id='jump-*'> <h3 id> <h4 id> <h5 id> <h6 id>
  • Lines and paragraphs break automatically.
The content of this field is kept private and will not be shown publicly.
CAPTCHA This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.


author-image
Alexsmith (not verified)
access_time 20 Jun 2019 - 18:29

unique meta tags also one the factor for SEO. Having unique meta title and description for every page is also one the great factor in the SEO.