Forum Moderators: open
i have a lot of pages that previously were:
<--virtual include from cgi script-->
and nothing else on an .shtml page and they got indexed by google no problems.
For various reasons, I have now had to change that to:
<HTML>
<HEAD>
<TITLE>blah blah blah</TITLE>
</HEAD>
<BODY>
<IFRAME SRC="http://blahblahblah.com" HEIGHT="2000" WIDTH="100%"></IFRAME><!-- Same text as title -->
</BODY>
</HTML>
I have heard that google doesn't like iframe content but what will happen in this case where 95% of a page's content is iframe. Will i be helped by the page title being google-readable? And the main query....what will google do to my already-indexed pages now they have changed to iframe? The urls are all exactly the same...just changed the content. Will they hang onto the index for a while or get dumped pronto?
would it help if I put some <NOFRAME> content on the page too....what would an <IFRAME> enabled browser see at that point?
greg
>> would it help if I put some <NOFRAME> content on the page too
With IFRAMES you don't use NOFRAME but rather put that between the IFRAME tags:
From w3c here [w3.org]:
<IFRAME src="foo.html" width="400" height="500"
scrolling="auto" frameborder="1">
[Your user agent does not support frames or is currently configured
not to display frames. However, you may visit
<A href="foo.html">the related document.</A>]
</IFRAME>
<added> Sorry jamesa, didn't see your link above.
Further information on the <iframe> element can be found at the above link. Google will not index the content of the <iframe src>. Unless of course that page resides on your own site and can stand on its own (outside of the <iframe> element).
<iframe> should be treated just like <frameset>. The area between <iframe>Content Here</iframe> is what the indexing spider will see. It is also what the user will see if they do not have a frames enabled browser which is going to be few and far between. But, there are other usability issues at hand and your <iframe> should be set up to appeal to all user agents.
Pay special attention to this...
longdesc = uri [CT]
This attribute specifies a link to a long description of the frame. This description should supplement the short description provided using the title attribute, and may be particularly useful for non-visual user agents.
Put other content on the page outside the iframe?
I would definitely go for that option. When I utilize the <iframe> element, I always have content above and below, or to the left or right. I also utilize the longdesc attribute if the content on the page is not sufficient for the user to interpret the contents of the <iframe>.
If the pages within the <iframe> reside on your site, I would try to make them so they can stand on their own (outside of the <iframe> element). Link them together with a text link navigation somewhere on the pages. You can also go one step further and utilize the link rel tag. ;)
There are also solutions to bring the user back into the <iframe> environment if they land on one of those pages outside of the <iframe>.
Now I have to use <IFRAME> to take in the xml feed from an affiliate program. There is no alternative there...I just now need to make the results google-friendly. I CAN put other stuff on the page but wasn't too sure where would be most effective for googlebot...outside or inside the iframe tags.
Would you put testimonials in iframe? Are there disadvantages of using iframe for pages with high competition in Google?
