The Fetch as Google feature in
Webmaster Tools gives webmasters the consequences of Googlebot endeavoring to
bring their pages. The server headers and HTML indicated are helpful to
diagnose specialized issues and hacking symptoms, however now and again make
twofold checking the reaction hard: Help! What do these codes mean? Is this
truly the same page as I see it in my program? Where might we eat? We can't
assist with that last one, however for the rest; we've as of late stretched
this instrument to likewise indicate how Googlebot would have the capacity to
render the page. Google+
Seeing
The Rendered Page
Keeping in mind the end goal to
render the page, Googlebot will attempt to discover all the outside documents
included, and get them also. Those documents regularly incorporate pictures,
CSS and Javascript records, and also different records that may be by
implication inserted through the CSS or Javascript. These are then used to
render a review picture that shows Googlebot's perspective of the page.
You can discover the Fetch as Google
gimmick in the Crawl segment of Google Webmaster Tools. In the wake of
submitting a URL with "Bring and render," sit tight for it to be
handled (this may take a minute for a few pages). When it’s primed, simply
click on the reaction column to see the results.
Taking
care of assets hindered by robots.txt
Googlebot takes after the robots.txt
orders for all records that it gets. On the off chance that you are forbidding
creeping of some of these documents (or on the off chance that they are
installed from an outsider, server that is refusing Googlebot's slithering of
them, we won't have the capacity to demonstrate to them to you in the rendered
perspective. Thus, if the server neglects to react or returns lapses, then we
won't have the capacity to utilize those either (you can discover comparable
issues in the Crawl Errors segment of Webmaster Tools). In the event that we
run crosswise over either of these issues, we'll demonstrate to them underneath
the sneak peak picture.
We suggest verifying Googlebot can
get to any implanted asset that definitively helps your site's unmistakable
substance, or to its design. That will make Fetch as Google simpler for you to
utilize, and will make it workable for Googlebot
to discover and file that substance too. A few sorts of substance –, for
example, online networking catches, text styles or site dissection scripts –
tend not to genuinely help the unmistakable substance or design, and could be
left denied from slithering. For more data, please see our past blog entry on
how Google is attempting to comprehend the web better.
We trust this overhaul makes it
simpler for you to diagnose these sorts of issues, and to uncover substance
that is inadvertently obstructed from slithering. On the off chance that you
have any remarks or inquiries, let us know here or drop by in the webmaster
help discuss
0 comments:
Post a Comment