thanks, Eric what about style tags, and polymer elements has style tags inside with js script tags and content goes inside templates tags, will search engine won't be effected of any , <style> and <script> and will read the content inside? and in the google best practice for SEO inline style is not one of it , also it increases the page size ?
On Thursday, October 13, 2016 at 8:06:27 PM UTC+4, Eric Bidelman wrote: > > Check out the resources on > https://twitter.com/ebidel/status/781197133072347136. There are some good > explanations there. > > Basics: > - Use the standard best practices and you're all set...<title>, anchors > instead of JS, metadata, json-ld, appropriate hierarchies etc. > - Search engines that can crawl and execute JS (Google) have no problem > with Shadow/Shady DOM. They see the final composed DOM tree. > - If you use a single tag like <my-app> , search engines that don't > execute JS may have issues surfacing your content. Try to use light dom as > much as possible for important content (titles, main text content). Shadow > DOM should be used for implementation details of your components. > > On Thu, Oct 13, 2016 at 8:40 AM nawras albaghdadi <[email protected]> > wrote: > >> I'm new to the polymer . trying to start my new project using it , but >> when I tried it and used the custom elements I notice that in the HTML when >> you inspect the page elements you see it has a lot of style tags and >> scripts tags >> >> also , when viewing the page source the page looks empty , so >> 1 ) how the search engine will work with this ? >> 2) and the shadow dom won't affect the SEO ? >> 3) and what about all the style and scripts tags inside the body of the >> page , won't affect the search engine? >> >> thanks >> >> On Wednesday, February 12, 2014 at 11:28:26 PM UTC+4, Alex Komoroske >> wrote: >> >>> [bcc polymer-announce] >>> >>> To date the best way to get questions answered by Polymer experts was to >>> send an e-mail to polymer-dev, our general purpose mailing list. That >>> works, but the questions and answers get mixed in with lots of other >>> e-mails on the list, making them hard to find later--especially for new >>> members of the community. >>> >>> That's why we now *recommend that you ask general questions on >>> stackoverflow.com <http://stackoverflow.com>, tagged with "polymer"* >>> (or, if your question is not specific to Polymer, "web components"). The >>> Polymer team will keep an eye out for new questions there and make sure you >>> get an answer. >>> >>> If you want to follow along, you can subscribe to e-mail notifications >>> for the polymer tag on stackoverflow.com (visit >>> http://stackoverflow.com/tags/polymer/info, hover over the 'polymer' >>> tag, and hit 'subscribe'). >>> >>> Of course, polymer-dev is still a great place to talk about all things >>> Polymer. >>> >>> --Alex >>> >> Follow Polymer on Google+: plus.google.com/107187849809354688692 >> --- >> You received this message because you are subscribed to the Google Groups >> "Polymer" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/polymer-dev/c3ad9022-1718-407a-9156-2d86cbd4c055%40googlegroups.com >> >> <https://groups.google.com/d/msgid/polymer-dev/c3ad9022-1718-407a-9156-2d86cbd4c055%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/37b9352b-6560-4b19-843c-8c412462c5fc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
