Forum Moderators: open
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
[b]<title>Your title here</title>
<meta name="description" content="Your description here.">[/b]
<script type="text/javascript" src="your-javascript.js"></script>
<style type="text/css">@import "your-stylesheet.css";</style>
</head> I think that just about covers it - you will also need a meta charset tag if you haven't defined the character encoding in the HTTP header.
All the other millions of meta tags are a waste of space.
** Many thanks for this, much appreciated.
you will also need a meta charset tag if you haven't defined the character encoding in the HTTP header.
** What are these 2 different ways please? Does anyone know which one is the best, as far as pleasing Mr Google?
o that makes a lot of my code below redundant?
<html>
<head>
<title>sample</title>
<meta name="description" CONTENT="sample">
<meta name="keywords" CONTENT="sample">
<link HREF="http://www.sample.com" REL="BOOKMARK" TITLE="sample">
<meta HTTP-EQUIV="expires" CONTENT="TUE, 01 JAN 2002 00:00:01 GMT">
<link rel="stylesheet" type="text/css" href="styles.css">
</head>
you will also need a meta charset tag if you haven't defined the character encoding in the HTTP header.** What are these 2 different ways please? Does anyone know which one is the best, as far as pleasing Mr Google?
>> HTTP header.
I believe that encyclo is referring to Apache (or whatever is serving your pages) sending the charset. Read the thread "charset declared in .htaccess? [webmasterworld.com]" for a bit of reference on Apache's AddDefaultcharset. Apache.org and Google can provide more in-depth information on how to declare the charset in your .htaccess file. (Assuming your site in being hosted on a server running Apache.)
>> meta charset tag
These threads should provide a little more insight:
[webmasterworld.com...]
[webmasterworld.com...]
[webmasterworld.com...]
[webmasterworld.com...]
W3C.org has full documentation on charsets, although much of it may read like stereo instructions.
>> pleasing Mr Google?
On this one, I'd say worry less about pleasing Google and more about providing pages that your users will be able to view properly.