Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I'm not sure how much sense this would make if we provide integration with Views and Panels, since that's most of the use-cases that people wanted for the nodewords custom pages sub-module in Drupal 6. Leaving this as postponed for now.
Comments
Comment #1
Jamie Holly CreditAttribution: Jamie Holly commentedI could actually see this being useful, as there are sites out there that have custom pages that aren't views or panels pages (ie: custom module pages). Of course another alternative (or perhaps one that should also be included) is an API to allow these modules to add their own metatags.
Comment #2
Dave ReidI'm still not sold on this, since the 80% of users would be fine as long as entities, views, and panels all have meta tag support. There would be an API, but this would be much lower priority than the Views and Panel integration. Once we have the full base API ready, anyone can post a temporary stand-alone solution here though.
Comment #3
john.oltman CreditAttribution: john.oltman commentedSubscribe
Related post:
http://drupal.org/node/1146018#comment-4446604
Comment #4
Dave ReidMarked #1151926: Allow meta tags to be assigned to custom paths as a duplicate of this issue.
Comment #5
ar-jan CreditAttribution: ar-jan commentedWait, this issue is a duplicate of itself... That's so meta! ;)
But, I just wanted to add another use case: assigning a noindex tag to
comment
,comment/reply
paths (example). The problem that emerged in that thread is that the comments permalinks internally carry a node/% path, which also makes an ad hoc solution hard.Comment #6
KoCo CreditAttribution: KoCo commentedAnd for generic Drupal pages, 'login page' or 'contact form' for example.
You have the general, but one would rather choose not to index login and alter description for certain contact pages.
(following)
Comment #7
ejwettstein CreditAttribution: ejwettstein commentedI have to agree with KoCo. I want to get my login and password recovery page out of Google. It's ugly to have them there. I'm not quite willing to change my global settings to no-index and make sure everything else is in.
Comment #8
ar-jan CreditAttribution: ar-jan commentedIf you need a temporary fix for some paths, you can use something like this:
Comment #9
dynamicdan CreditAttribution: dynamicdan commentedSeems like a good tmp fix but this module could also implement that logic easily right?
showing /user in a google index is a (medium) security risk in my opinion.
I see 2 needs:
1) can be resolved either with URL matching or perhaps module URL matching?
2) would work similar to 1?
Tip: re-use the interface that pathauto does. Display a list of custom URLs and their meta assigned.
Updating to 'major' due to security risk (and that everyone in drupal world would use this feature!!).
Comment #10
chrisroditis CreditAttribution: chrisroditis commentedIs there currently an api that allows us to achieve this, or any plans to implement this functionality into the module?
Comment #11
Pablo Romero CreditAttribution: Pablo Romero commentedI agree with KoCo. I've also been trying to customize metatags for contact and login pages.
Subscribing
Comment #12
Summit CreditAttribution: Summit commentedHi, I know a different solution what works on custom paths. It is not metatag but a specific module.
It is called Beanstag: http://drupal.org/sandbox/beansboxchrispang/1189124
It is working great for custom pages!
Would love to see it integrated in metatag!
Greetings, Martijn
Comment #13
DamienMcKennaClosed #1431794: Any way to restrict metatags by path or block? as a duplicate of this.
Comment #14
DamienMcKennaWould you be willing to use Context to assign the meta tags per path? There's already a context_metadata module which I'm intending to help with to rewrite to use the Metatag module's configuration rather than its own, I think it'd be a huge time savings if we go this route rather than building our own system.
Am tagging this as a release blocker as we need either a) working code, or b) a decision to use context_metadata.
Comment #15
Summit CreditAttribution: Summit commentedHi, I went allready that route, not yet completely there with tokens, but see: http://drupal.org/node/1765796#comment-6435626
greetings, Martijn
Comment #16
couturier CreditAttribution: couturier commentedThis could really be on to something, using Context to assign meta tags per path. I know that EclipseGc is working to incorporate Panels features into Drupal 8 core, and Panels works together with Context for URL creation, so this way of working is going to be getting more popular going forward.
The Views maintainers don't want to spend the time to support unique page titles for their paginated views that are creating SEO errors with Google and Bing (reference this issue). And, with page title support now also added to the Metatag module, maybe we could achieve not only metatag support but also page title support specific to URL through Context. If this is possible, it would save time and maybe also achieve this Metatag module request: Using Views with [current-page:page-number] to avoid duplicate page titles (comment #5 above also applies to this as a variation).
Comment #17
DamienMcKennaI'm personally pushing to focus on Context integration as the initial solution for per-path functionality: #1187710: Integrate with Context
Comment #18
DamienMcKennaThanks to amazing work by Marcin Pajdzik, we will be handling the by-path functionality via #1187710: Integrate with Context.
Comment #19
DamienMcKennaDuplicate issues don't get tags.