Googlebot to Submit Web Forms
I saw recently on the Google blog that the Googlebot will start submitting web forms.
Specifically, when we encounter a
<FORM>element on a high-quality site, we might choose to do a small number of queries using the form. For text boxes, our computers automatically choose words from the site that has the form; for select menus, check boxes, and radio buttons on the form, we choose from among the values of the HTML.
They also listed some important limitations, which makes this seam much less extreme as it did when I first read about it.
The Googlebot will NOT submit forms that:
- "Use terms commonly associated with personal information such as logins, userids, contacts, etc"
- Have a form action that is forbidden in
- GoogleBot Runs AJAX? - December 6, 2006
- Pinging Search Engines when Sitemaps Change - July 18, 2007
- Sitemap hint in robots.txt - June 13, 2007
- Uploading Files Like GMail Attachments - October 6, 2006
- It takes more than just PageRank - December 12, 2005
I assume that they will still recommend that you use Google SiteMaps to have your site fully indexed. I wonder what the driving force behind this is. It seems a bit odd to me. After all, isn't most data behind any kind of "Search" form accessible in some other way (drill down through menus and navigation)?
Yes, I find it a bit odd as well. If your content is in sitemaps google will find it, but probably won't have nearly as much weight as it would if you created a HTML page on your site with links to the deep items (a real sitemap). My guess is that they will only use this on a small number of sites, perhaps those that are popular but don't appear to have much content. I think this feature is more for those sites with nonexistent search engine optimization.
Just to clarify, I was talking about XML vs HTML sitemaps in the second paragraph. Both are good to use but if you had to pick just one, I'd go with HTML.
Google has been submitting forms both for a long time.. ajax too.
pimapen panjur sineklik aluminyum
It seems a bit odd to me. After all, isn't most data behind any kind of "Search" form accessible in some http://tophotely.com
- Updating Java on ColdFusion or Lucee
- ColdFusion returning empty response with server-error: true
- Careful applying CF11u16, CF2016u8, CF2018u2
- Sessions don't work in Chrome but do in IE
- csrfVerifyToken does not invalidate the token
- The cf_sql_ is optional in cfqueryparam
- Cookie Expires / Max-Age 1969-12-31T23:59:59.000Z
- Burst Throttling on AWS API Gateway Explained