| Members: 43896 |
| Language: English |
|
Group categories:
|
| More group info » |
|
| Sep 8 |
|
| Aug 24 |
|
| Aug 22 |
|
| Aug 20 |
|
| Aug 2 |
|
| Aug 2 |
|
| Jul 29 |
|
| Jul 19 |
|
| Jun 15 |
|
| May 21 |
|
Q: How many unique visitors per marker / map point will trigger logging and indexing?
A: The number will be tweaked over time after we start logging data and while we experiment with the feature. So, we can't tell it for certain at this early stage. If you have concerns about private data being indexed, you can opt out of the logging as described in the blog post and FAQ. Q: How is Google crawling the data from my mashups? What is user agent of the crawler? A: The data is not being "crawled" as done by typical robots for web search. The Maps API JavaScript will asynchronously log data back to Google's servers as your mashup is being rendered and used. Q: Is it possible to allow logging only for specific portions of the info window content? or only some of the info windows on a given map? A: No, this is not possible. If you would like to opt out of the indexing, this applies to the map (by using "indexing=false" in your request for the API JavaScript) or to the whole page or more (by using robots.txt). Q: How and where are the mashups going to be displayed or linked? How do you plan to link to pages that are dynamic and load data asynchronously? A: We will treat the information logged via the Google Maps API in a way similar to web search. If the information is displayed, for example in a search result, we will show only a snippet of the information and will include a link back to the original page and provide the user with enough context to decide if they should click through. Q: Will the extra logging logic impact the performance of my mashup? A: We've tried to implement logging in a way that minimizes the impact on performance, both in terms of CPU and bandwidth. If you feel that that logging is impacting your application's performance in a noticeable way, we recommend that you turn it off and give us feedback so that we can improve the feature. Q: How does this feature interact with KML feeds/Sitemaps? A: If you are also providing KML Sitemaps, these will be considered together with content we log from your mashups as we expose relevant information to end users. In particular, we will be looking at the logged data for additional information that can support, corroborate, and extend what's in the KML feed. Q: How does Google log content from info windows if the content is dynamic, e.g. it's streamed and refreshed? A: At this point, we will only be logging content that is displayed in the info window when it's first rendered. This may change as we iterate and improve this feature. Q: Does Google log content from ExtInfoWindow? A: No, not at this time. Q: If my map is in an iframe that is part of a larger page, which URL or page will you link to? A: See the background information below (and the related article it links to) on how Google handles frames and iframes in general. http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=34445
|
|
| Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy |
| ©2010 Google |