Welcome to WebmasterWorld Guest from 22.214.171.124
Forum Moderators: incrediBILL
The text that is displayed within the frames is the display of another page i.e.
My design page is called 'design.htm' my text is called 'design text.asp' on my design page I have the following code:
<iframe src ="design text.asp"> </frame>
Will search engines just pick up the text in 'design text.asp" and direct people to that page?
thanks in advance
Now that could only happen if Google did index the iframe page. So, because of these members reports, I'm sure that Google at least indexes links into an iframe (anchor tags with a target="iframename" attribute). The only thing I'm not sure about is the original iframe document, designated by the src= attribute inside an iframe tag.
Also, there have been several reports recently of Google devaluing <noframes> content because there is strong potential for abuse/spam there. So even if there is a problem with iframes, noframes may not be the best answer today - although it certainly worked well in the past.
I'm beating the bushes for some clarification on this, and we'll report back as soon as we have the word.
But Googlebot definitely can and does index iframe content. In fact, there are some posts here with people trying to keep their iframes content OUT of the index because Googlebot is finding it and they don't want that.
If I had a site where I wanted some insurance that Google would index the iframe content, I'd put some straight links at the bottom of the page - pointing right to the docs that normally appear in iframes.
Then I'd put a script inside those docs that slapped them back into their parent page if they were displaying as orphans. That would create a simple, direct link trail for Googlebot that should not ever be problematic. You might also include a <noscript> tag with some minimal navigation back into your main pages, just for those surfers with js turned off.
According to the research I've done on the <iframe>, typically the content inside the frame itself is not indexed although there have been reports that contradict that as tedster points out above.
Also, if the users browser does not support <iframe>s, the content between the <iframe> and </iframe> is what the user will see. I tested all this back when <iframes> were first being discussed. I use them on a few sites to allow viewing of various items that don't require full pages. I think their cool, a window anywhere on the page that you want it!
That area between the <iframe> and </iframe> serves the same purpose as the <noframes> tag does.
Typically the content should be either a link to the embedded document or a copy of the content of its body. In the latter case, the copy must not include the head part (title etc.) or body tags, just the part that is inside the body element in the full document. Some suitable authoring tools or server side mechanisms could be used to make the copying automatic.
P.S. It is suggested that you wrap your <iframe></iframe> inside a <div></div> to prevent IE5 on the Mac from displaying the content inside the <iframe></iframe> tags.
<div><iframe>Content for browsers that do not support the iframe element.</iframe></div>
Remember, <iframe> is an inline element and can be wrapped in various block level elements. The <div> is suggested as the container element.
The joy here - NN4 and only NN4 understands the ilayer tag. So other browsers ignore it but render the iframe; and NN4 ignores the iframe and renders the ilayer.
IE 4 up and NN6 up all support iframe, as do all other modern browsers.