This module currently implements three rules and I don't have very much knowledge about SEO. I therefore want to use this issue to gather ideas for further rules. I obviously can't promise that I will add or implement every idea but if you provide good ideas and ideally also good patches, that would be great.

Comments

miruoss’s picture

Version: 6.x-1.x-dev » 6.x-2.x-dev
IreneKraus’s picture

We've just tried activating this on our community site, and are running into an issue with the rule that links must include the Title attribute. While I realize this may be an important SEO Factor, the editor I currently have installed on the site (CKEditor) does not make any provision for adding this attribute:
http://docs.cksource.com/CKEditor_3.x/Users_Guide/Rich_Text/Links

The only way to add this attribute is to manually edit the link tag, which goes beyond what most of the users on my site wish to do. I've got things set to allow Admins to over-ride this rule so content can still get published, but it is an annoyance. What I'd like to see is a way to enable or disable those rules in the settings so I can tailor those to the users of a site.

miruoss’s picture

Hi Irene

First of all I suggest you fill the title tag. It is in the advanced tab of your links widget (http://docs.cksource.com/CKEditor_3.x/Users_Guide/Rich_Text/Links#Advanced):

Advisory Title – the text of the tooltip that is shown when the mouse cursor hovers over the link (title attribute).

However, you can also do one of the following things (assuming you're using Drupal 7):

  • Disable a rule by setting its threshold to 0% on the seo checker module configuration page.
  • Give your editors permission to save a node even if it doesn't pass all the tests (permissions).
spidersilk’s picture

Another change that would be useful is allowing the image alt checker to check image fields, not just inline images in the body field.

spidersilk’s picture

On that last request I post (checking image fields) - I'm actually working on that now, since I have a client who wants it. Will contribute my code if I can get it to work.

Just noticed, though, that the version listed for this issue is the D6 version, and I'm working on it for D7. Is this thread supposed to be for feature requests for both versions, or just the D6 version?

miruoss’s picture

Version: 6.x-2.x-dev » 7.x-1.x-dev
Issue summary: View changes

That would be great of course! And no, actually we should focus on D7. But when the ticket was created, there was no D7 version.

spidersilk’s picture