tags:

views:

182

answers:

2
+1  Q: 

Will <noscript> hide the rest of the static content to Google crawlers?

This should be an easy one for someone:

Will the <noscript> element cause the HTML page to serve only the content within the <noscript> tag itself to google crawlers and hide all the rest of my static content causing it so not to be indexed?

Thanks!

+3  A: 

No. The crawlers will see all your content, both within the <noscript> element and everywhere else.

Crawlers behave a lot like browsers with JavaScript turned off - they see all the static content plus the <noscript> content, but not anything JavaScript-dependent.

RichieHindle  2009-08-22 17:32:49
thanks - now it's clear :)
JohnIdol  2009-08-22 18:32:19
+2  A: 

The whole HTML file is served in response to a GET request. Google should honour robots.txt and not spider directories marked with that.

Steve Gilham  2009-08-22 17:33:18

related questions

How do you know what a good index is?
What datatype should be used for storing phone numbers in SQL Server 2005?
What is the best way to build an index to get the fastest read response?
How would I go about creating a custom search index much like Lucene?
What is a Covered Index?
When should you use full-text indexing?
SQL/Oracle: when indexes on multiple columns can be used
Best use of indices on temporary tables in T-SQL
On Disk Substring index
How to implement a "related" degree measure algorithm?
Non-Clustered Index on a Clustered Index column improves performance?
HTML Help keyword location
One or Two Primary Keys in Many-to-Many Table?
Strategies for keeping a Lucene Index up to date with domain model changes
Do indexes work with "IN" clause
Table Scan vs. Add Index - which is quicker?
Why does SQL Server work faster when you index a table after filling it?
PostgreSQL: GIN or GiST indexes?
What's the difference between a Table Scan and a Clustered Index Scan?
Database Case Insensitive Index?
Testing for inequality in T-SQL
Tables with no Primary Key
How do I index a database field
How does database indexing work?
Why doesn't SQL Full Text Indexing return results for words containing #?