-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
google indexing does not index my description and title #33
Comments
Me too! I'm with the same issue |
please tell me if you have already solved the problem. may i know the url
of your website ?
…On Wed, Mar 15, 2017 at 7:16 AM, Leonardo Couy ***@***.***> wrote:
Me too! I'm with the same issue
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATV9N3wq3KrPHkXWPLt4_VsOy7zVE8Afks5rlx_YgaJpZM4Mc__s>
.
|
Having the same problem. |
hoping the author of ngMeta will help us :D
…On Thu, Mar 16, 2017 at 1:03 AM, Benjamin Schuch ***@***.***> wrote:
Having the same problem
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#33 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATV9N7kD3CZwF9fRfNzQ7a0MiCBOXCErks5rmBncgaJpZM4Mc__s>
.
|
did someone already fix this ?
On Thu, Mar 16, 2017 at 2:10 AM, Kim Sean <[email protected]>
wrote:
… hoping the author of ngMeta will help us :D
On Thu, Mar 16, 2017 at 1:03 AM, Benjamin Schuch ***@***.***
> wrote:
> Having the same problem
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#33 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ATV9N7kD3CZwF9fRfNzQ7a0MiCBOXCErks5rmBncgaJpZM4Mc__s>
> .
>
|
Bump! I have this issue as well, on https://www.e7solutions.com. I do wonder if it's Google's issue, since their crawlers should be properly interpreting AngularJS now. |
i have exactly the same issue. It shows {ngMeta.description}} |
bump! |
Since google announced that they won't "support" crawling complex SPA's in favour of progressive enhacement in the future, you have to think about a way to render static html anyway. |
me too have the same problem ! |
@foxegypt : By using https://prerender.io, it resolved my problem. |
same issue |
Is there any solution to resolve this problem? |
@nomankt https://support.google.com/webmasters/answer/81766?hl=en is the only real solution or server side rendering (static html pages). |
So, we used this other module for more than a year and google crawled the metadata correctly. Now we changed to ngMeta and we are facing the same problems described in this issue, comparing the two source codes of the modules, it seems that angular-update-meta modifies the DOM directly to update the metadata, unlike ngMeta which uses angular scopes (just took a quick look, I could be wrong). So to fix the issue it seems that ngMeta needs to be modified to change the DOM directly so the google bot works well with it @vinaygopinath |
Thanks for the tip @Eduardo-Julio. The other module fixes SEO issues, which was why I was planning to use ngMeta in the first place. |
Hi, same issue here! @KingKarrow and @foxegypt, I google search your website and the google search results look ok. Can you share how did you solve the problem? Thanks |
try it https://prerender.io |
i've added my site in fetch as google. when i search it, google does not index my title and my description
it shows only
{ngMeta.description}}
The text was updated successfully, but these errors were encountered: