Geek Answers Handbook

Benefits of SEO.html v / s jsp / php / etc?

This may seem like a silly question, perhaps it is. But I'm only trying to make sure that hidden information is not hidden from me.

Well, therefore, if I have the opportunity to make additional efforts for development in simple html and connect my back-end via ajax, am I following it?

Meaning, I could use PHP / JSP to include files such as headers, footers, and navigation. This processing is performed at the user's request for the file.

But as an alternative, I can use ant build script to compile the HTML file from headers and footers, navigation, etc. after graduation. But this requires some effort.

Keep in mind that this is not an AJAX v / s issue, not related to AJAX, and the final output file is the same in both cases, except for file extensions.

+4
source share
5 answers

A document extension (* .html / *. Php / *. Aspx) does not make any difference to the ranking of your search engine. If you leave the page content for a while, it’s important with regard to the URLs:

  • A logical and consistent URL structure, ideally a tree structure.
  • using the correct keywords in your dash separated urls.
  • if it is possible to avoid using the query strings "?" in your URLs (becoming less important, but still relevant for small search engines).
  • general "crawl" of your site (with an XML map with text links to all pages of the site, the correct use of robots.txt exceptions)

You can easily “hide” the type of file extension on almost all systems by doing something like www.acme.com/mycms. php / pagename / and then mycms.php parse the requested URL.

Good, modern web frameworks allow you full control over the structure of URLs, examples of Django and ASP.NET MVC .

One of the difficult tasks is localization. There are many suggestions:

  • use a separate website for each language (acme.com/acme.co.uk/acme.de/acme.ch)
  • use a separate subdomain ( en .acme.com / de .acme.com)
  • use the extension www.acme.com/pagename. ru .html
  • use the root folder "www.acme.com/ ru / pagename

I think that at the moment I decided to use the "root folder", but there are good arguments for other approaches.

For an example of a good URL structure, look at this site. :-)

+6
source

"Normal HTML" and the generated by the HTML server must be the same. You can also use server handlers to force, for example, querystrings to behave in an “SEO friendly” way.

+3
source

An HTML and javascript page that uses AJAX to display content actually reduces the visibility of your search engine, since the spidering search engine is not going to bother interpreting your javascript. The search engine will not see any of your content.

Fortunately, most search engines understand RSS or ATOM, so be sure to include the news feed from your site.

+2
source

Static HTML pages are slightly faster than those created by the server, and speed is a factor in SEO, but not significant.

0
source

I think that choosing to display generated HTML over server-side HTML may be a good idea in some scenarios, especially if you do this with an automated script: -

  • If you do not need to download data from the server from the database.
  • When pages will not change often, and not in response to user interaction.
  • If you want to save precious seconds (processing time script to generate HTML)

But, frankly, today the use of some server-side scripts has become almost mandatory if you want to create a popular website. This is because the specifications and requirements of the website are changing rapidly, and new requirements are often implemented easiest and faster using server scripts.

So, I think that it is best for you to invest if you choose server-side scripts (Any PHP / ASP / JSP) to serve your data.

Now about Ajax, I don’t know how you can do this job very well without server-side scripts if your active content is not extracted from the static html content.

If you intend to use databases, you will need a script.

0
source

More articles:


All Articles