ASP.NET - SEO-friendly? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, o开发者_如何学Gor expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 10 years ago.

I would like to ask you guys about your opinion on SEO for services written in ASP.NET. I met an SEO specialist who says that it is almost impossible to make SEO for services/portals written in ASP.NET because Google robots don't like the pages it generates. Can you confirm or deny this theory?

---

If the portal relies heavily on query strings or improperly loaded AJAX pages, then it would be nearly impossible. But if it has friendly names, it wouldn't be too hard.

Any platform can do horribly for SEO and any platform can do miracles for SEO. It all depends on how well the application is written.

---

I confirm this theory. But this being said there have been some very nice additions like the routing engine allowing you to have SEO friendly URLS and the full control over the generated ids (in ASP.NET 4.0).

---

The problem's not in the platform itself but rather how you use it. One major SEO rule is to have machine readable HTML code to make a semantic page and standard XHTML.

ASP.net's problem lies on the built-in components that are used in a page. When the components are rendered to HTML they generate non-standard HTML code.

The trick is to generate the data on a page using standard HTML tags and than use CSS and JavaScript to style it i.e. The data can be saved in a RecordSet instead of a DataGrid and looped over to create an HTML table.

.Net has made great improvments to the auto generated code since MVC 1.0 which creates standard XHTML.