-
Notifications
You must be signed in to change notification settings - Fork 157
ng add @angular/seo #729
Comments
Why not make this as part of the
That implies a router, no? We don't have a router by default (maybe we should). |
There are classes of applications that do not need/want to worry about SEO: internal applications, applications exclusively behind a login, etc. For those cases the files and logic could manually be removed, I suppose. However, some of those items (e.g., conditional polyfills) are things that could be elevated beyond SEO though. |
I think we need to experiment with this stuff more before we roll it out to
everyone. This would be a safe way to iterate and find a the right solution
for most apps without breaking things.
…On Wed, Apr 18, 2018, 10:47 AM clydin ***@***.***> wrote:
There are classes of applications that do not need/want to worry about
SEO: internal applications, applications exclusively behind a login, etc.
For those cases the files and logic could manually be removed, I suppose.
However, some of those items (e.g., conditional polyfills) are things that
could be elevated beyond SEO though.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#729 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AANM6IGYVfpeP7yBHWm1MYviQ0wdnBHVks5tp24SgaJpZM4TZyPX>
.
|
If it's only a set of relatively static files that can be generated initially, it wouldn't matter to much whether its part of |
Another aspect is that part of the generated files might need to be extended by users based on dynamic data, which are not known in the app. This is a separate flow and we should be careful do allow for such manual additions.
Developers can create other manual sub sitemap files and include them into the main sitemap (which should not be generated again). |
Great Idea, as i built my site, it would had helped me, if at least, I would have known the which basics I have to take care.
Probably the trade off effort/results is to go for the number 2. |
I think this is a really cool idea and didn't know about any of this so adding this with one command potentially with some granularity/options would be awesome! |
It seems to me that in the general case, for a dynamic application, sitemap.xml would be generated by server-side code that accesses the same data as the Angular application. Therefore - perhaps the sitemap idea fits in well with Universal, but not with client-only Angular? Universal is becoming more popular; perhaps angular/seo ought depend on /universal. |
@kylecordes agreed that this would make a lot of sense in universal, but as @IgorMinar pointed out at ngconf, he's in favor to see a solution in non-universal driven websites. Ideally we try to achieve the same for both in a generic way. |
I believe SEO is the most important think. More than speed, comfort, simple code, etc....
|
About the price he said. I think IgorMinar is right. More money, more SEO... It is a truth and it is acceptable. Assume that your website is dynamic content (just like news, or blog or something with auto generated content).
|
A great idea.... and maybe some kind of support for JSON lD (https://json-ld.org/) |
@IgorMinar diving into the angular.io index.html to see which best practies are you using. |
This issue was moved to angular/angular-cli#12120 |
Bug Report or Feature Request (mark with an
x
)Area
Versions
v6
Desired functionality
I'd like to be able to invoke
ng add @angular/seo
and have the CLI make my application search engine friendly. Initially I'd like to see the following feature provided by the schematics:noindex
metadata to emulate the HTTP 404 and 500 status codesMention any other details that might be useful
The text was updated successfully, but these errors were encountered: