Hi DA team. Great work on this module! I've been playing around with attempting to get SEO working with this module. The issue that I am running into is that I'd rather not hardcode meta data into templates. True, it works for now, but might I recommend a different approach?

FIrst, I am not a developer... so I am adding this as a feature request. This is also meant to hopefully assist the dev team here in finding a good solution to tackle this.

Rather than the popular nodewords module, I've grown fond of the int_meta module. Its give you many more way to manage and add meta data to sites you develop (hat off the those guys). It also allows the addition of token into metatags.

I'd suggest adding a description and maybe even default keyword fields to the domain settings screen in DA. If we could then pass these fields to tokens... a project patch I've seen in the DA quere, these tokens could be passed into meta tags by int. This would allow for dynamic management to meta data for all your domains by reusing code.

Adding a new sub module that depends on int_meta and tokens should do the trick and expand the possibilities for this already great module.

Any thoughts?

CommentFileSizeAuthor
#12 domain_meta.zip3.02 KBnonsie

Comments

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

Should not be terribly difficult. Perhaps someone will take it on. Since this is not a core feature, it is unlikely that I will.

The token patch is already in HEAD.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Title: SEO and Domain Access » int_meta settings for Domain Access
keesee’s picture

keesee commented

Ken,

Thank you for the quick replies, as always. might I inquire as to how you are handling this issue on your installations of DA? theme?
I also don't think "int_meta settings" is a good name for this post... the int_meta module is just an example application possible if we were to start collecting description and keyword data for a domain. I just posed that as an example of what would be possible. I see this step focusing on making that data available rather than limiting it to a specific module. It could be used in any tokenized module, passed to the theme layer, or used by other modules.

here are my thoughts on how this should look...
-Addition of text area "Site Description" to the domain settings pages
-Addition of text area "Keywords" to the domain settings pages
-Token support for both that can be leveraged in int_meta and other tokn supported modules. (token support should in practice support all setting fields where it makes sense to do so) happening here.... http://drupal.org/node/361018
--- tokens to pass
a.) description for the current domain
b.) keywords for the current domain
- this would be implemented as a new module "DA_meta"

I am wiling to partially fund this development... fully if it is reasonable.

Although this is now another module, I think that addition of basic domain information in the DA module core is needed (description at minimum). I am not quite sure why Drupal as a whole hasn't adopted this on their site settings page. Never got why there is mission field, but not a description field. Just my take.
--
J.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Title: int_meta settings for Domain Access » Meta tag settings for Domain Access

Title change.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Active » Postponed
tassoman’s picture

tassoman commented

I think it's a crucial feature. Anyone building complex web applications need this. The best bet would be having it implemented only at level of global keywords and meta description.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

Then build it. I am already maintaining too much code, and we are trying to get a stable release out.

Hence "postponed" status.

sittard’s picture

sittard commented

If you are using a different theme per domain then an alternative suggestions might be to use the theme-settings and create a form using the form API. This could be used to gather meta tag information on a per theme basis.

nonsie’s picture

nonsie
she/her
Primary language Estonian
commented

Just a FYI - I'll be needing it for a site due to be launched in late July so I'll most likely end up writing some of it if not all. If you are willing to help, drop me a line.
It will not be part of Domain Access (released as a separate module).

chipway’s picture

chipway commented

Interested to setup DA personnalized meta tags, so subscribe.

nonsie’s picture

nonsie
she/her
Primary language Estonian
commented
Project: Domain » Domain Meta Tags
Version: 6.x-2.0-rc6 »
Component: User interface » Code
Status: Postponed » Needs work

Moving to the correct project.

nonsie’s picture

nonsie
she/her
Primary language Estonian
commented
StatusFileSize
new domain_meta.zip3.02 KB

Here's something to test while I get this project set up correctly.

keesee’s picture

keesee commented

Great! I look froward to testing it over the weekend!

nonsie’s picture

nonsie
she/her
Primary language Estonian
commented
Version: » 6.x-1.x-dev
Status: Needs work » Needs review

There's now DRUPAL-6--1 branch all future patches should go against.

keesee’s picture

keesee commented

Perfect. thx. looks like I won't get to it until tuesday or so, but look forward to giving it a go.

regards,
J.

nonsie’s picture

nonsie
she/her
Primary language Estonian
commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.