After scouring the internet for a few days and reading all the bugs, I'm at a loss, so I'm going to ask the community.
I'm trying to just get a canonical link on my user login and register pages. Meta tags does a wonderful job of placing that canonical link on every other page on my entire web site, but not mysite.com/user/login or mysite.com/user/register. Unfortunately, with login redirect tokens in the URL when a user wants to comment on a blog post, I'm getting a TON of duplicate page content errors that are negatively affecting my SEO efforts.
Any suggestions?
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | metatag-n1933678-10.patch | 3.89 KB | damienmckenna |
Comments
Comment #1
damienmckennaHave you tried using the Metatag Context submodule to assign the values by path?
Comment #2
justinthughes commentedYeah, I tried that. I added it to the 'by path' tab in the Meta tag config page, and I've verified that it then appeared in the 'structure' section under contexts.
I'm using the paths:
user/login
user/register
Any mistakes there?
Comment #3
damienmckennaComment #4
justinthughes commentedOK, so this is now back on the top of my list. Any help would be appreciated.
On every piece of content, on the front page, everywhere, my meta tags show up... just not on the login or register pages.
Comment #5
damienmckennaDid you try with the latest beta7?
Comment #6
damienmckennaI've tested this locally and can confirm that the meta tags do not show on the user login pages.
Comment #7
damienmckennaOk, no, I was loading the wrong page.
I cannot reproduce this.
You should check that the path is set correctly - remember that the login form is available at /user/login and /user. What you might want to do is use the Context UI module to customize the context definition, add the user role "anonymous" as a condition and then add both the "user" and "user/login" paths.
Comment #8
damienmckennaMaybe it would help if Metatag included some contexts out of the box to handle scenarios like this?
Comment #9
damienmckennaThis should be easy to do, so lets include it with the main release.
Comment #10
damienmckennaThis adds default Context definitions for both the user login and registration pages. The configurations are default by default but may be enabled via the Context UI admin page and then customized as needed; the metatag_context's README.txt has been updated to note the changes.
Comment #11
damienmckennaCommitted.