Tweet
Re: Help with listing mp3 downloads on page
The above method is simply a way to place a hyperlink in a scrolling textbox (either using an iFrame or not) to direct to the top of a Parent page .... it does nothing to "place" Content within the scope of how a Search Engine attributes Content to the Parent Page at all, either as a scroller or a true iFrame.
This "Navigational compensation" is not a solution to how it affects Site Search or Page Content vales/attributes that the Search Engines register.
Hyperlinks or page navigation have never been an issue: the links needed on the page are simple download links to an audio or video file (which has been uploaded to the server), which, when clicked will open a player on the User side, not on another page.
In the case of a PDF or document 'download' the link will open a new browser Tab. Or, to "workaround" any other type of "display" the link could be Styled using TARGET="_blank" or an onclick/pop-up window.
If a Visitor truly wishes to "download" the file, the manner remains the same: RIGHT-CLICK > SAVE TARGET AS
These 'download' links also need to remain associated with the page's Content, all of which needs to remain "Searchable" and attributable to the page values, and using an iFrame of any sort will defeat this purpose!
Digging deeper into this, it may be possible to use Naval's "BV + PHP" method as an "include" although there is no clear (documented) understanding on how using a scrolling textbox will affect the "searchability" of the text within the scroller itself for Site Search. I tend to think it may indeed attribute the values to the page (being an 'include' that is code included to the page), but how it "places it" on the page within a scroller is still undefined.
In the least, this method (the PHP method) is far more favorable than using an iFrame for so many reasons, even if it is not proven to be 'Site-Search Safe'!
The above method is simply a way to place a hyperlink in a scrolling textbox (either using an iFrame or not) to direct to the top of a Parent page .... it does nothing to "place" Content within the scope of how a Search Engine attributes Content to the Parent Page at all, either as a scroller or a true iFrame.
This "Navigational compensation" is not a solution to how it affects Site Search or Page Content vales/attributes that the Search Engines register.
Hyperlinks or page navigation have never been an issue: the links needed on the page are simple download links to an audio or video file (which has been uploaded to the server), which, when clicked will open a player on the User side, not on another page.
In the case of a PDF or document 'download' the link will open a new browser Tab. Or, to "workaround" any other type of "display" the link could be Styled using TARGET="_blank" or an onclick/pop-up window.
If a Visitor truly wishes to "download" the file, the manner remains the same: RIGHT-CLICK > SAVE TARGET AS
These 'download' links also need to remain associated with the page's Content, all of which needs to remain "Searchable" and attributable to the page values, and using an iFrame of any sort will defeat this purpose!
Digging deeper into this, it may be possible to use Naval's "BV + PHP" method as an "include" although there is no clear (documented) understanding on how using a scrolling textbox will affect the "searchability" of the text within the scroller itself for Site Search. I tend to think it may indeed attribute the values to the page (being an 'include' that is code included to the page), but how it "places it" on the page within a scroller is still undefined.
In the least, this method (the PHP method) is far more favorable than using an iFrame for so many reasons, even if it is not proven to be 'Site-Search Safe'!
Comment