Google Webmaster

From HaFrWiki
Jump to: navigation, search

Introduction

Google Search formerly Google Webmaster is the tools to submit websites to a search machine such as Google and/or Duckduckgo.
For a description of the issues on this page see also the Get started with Search: a developer's guide[1].

Making your content search-friendly matters because it's how you get more relevant users viewing your content.
This is called Search Engine Optimization (SEO), which can result in more interested users coming to your site.
If Google Search has trouble understanding your page, you're possibly missing out on an important source of traffic.

This guide covers what developers can do to make sure that their sites work well with Google Search.
In addition to the items in this guide, make sure that your site is secure, fast, accessible to all, and works on all devices.

To get started

Follow the following steps.

  1. Test your site in the Mobile-Friendly Test to see how Googlebot sees your site.
    • Googlebot is Google's web crawling bot that discovers new and updated pages and adds them to the Google index.
      For more information about the process, go to How Google Search Works.
  2. Javascript and googlebot


Keep Google updated

To make sure that Google finds your new or updated pages quickly:

If you're still having trouble getting your page indexed, check your server logs for errors.

Sitemaps

Whats is

A Sitemap is a file where you provide information about the pages videos's and other files on your site.
Search engines like Google read this file to more intelligently crawl your site.
A sitemap tells Google which pages and files you think are important in your site, and also provides valuable information about these files:
For example, for pages, when the page was last updated, how often the page is changed, and any alternate language versions of a page.

You might need a sitemap if:

  • Your site is really large.
    As a result, it's more likely Google web crawlers might overlook crawling some of your new or recently updated pages.
  • Your site has a large archive of content pages that are isolated or not well linked to each other.
    If your site pages do not naturally reference each other, you can list them in a sitemap to ensure that Google does not overlook some of your pages.
  • Your site is new and has few external links to it.
    Googlebot and other web crawlers crawl the web by following links from one page to another. As a result, Google might not discover your pages if no other sites link to them.
  • Your site has a lot of rich media content (video, images) or is shown in Google News.
    Google can take additional information from sitemaps into account for search, where appropriate.

Links


Recrawl URL

Indexing API

PageSpeed Insights

PageSpeed Insights (PSI) reports on the performance of a page on both mobile and desktop devices, and provides suggestions on how that page may be improved.
PSI provides both lab and field data about a page. Lab data is useful for debugging performance issues, as it is collected in a controlled environment. However, it may not capture real-world bottlenecks. Field data is useful for capturing true, real-world user experience - but has a more limited set of metrics. See How To Think About Speed Tools for more information on the 2 types of data.

  • Lab data
    A depiction of a man standing in front of a bunch of abstract technical concepts and icons. Lab data is performance data collected within a controlled environment with predefined device and network settings. This offers reproducible results and debugging capabilities to help identify, isolate, and fix performance issues.
  • Field Data (Also called Real User Monitoring or RUM)
    Field data is performance data collected from real page loads your users are experiencing in the wild.

Google Performance Tools

Google has put out a lot of guidance around performance data and performance tooling. The goal of this infographic is to consolidate this guidance for developers and marketers to help them understand how to think about performance and navigate all of Google's performance tool offerings. [2]

  • Lighthouse
    Gives you personalized advice on how to improve your website across performance, accessibility, PWA, SEO, and other best practices.
  • WebPageTest
    Allows you to compare performance of one or more pages in controlled lab environment, and deep dive into performance stats and test performance on a real device (created by Catchpoint). You can also run Lighthouse on WebPageTest.
  • TestMySite
    Allows you to diagnose webpage performance across devices and provides a list of fixes for improving the experience from Webpagetest and PageSpeed Insights.
  • PageSpeed Insights
    Shows speed field data for your site, alongside suggestions for common optimizations to improve it.
  • Speed Scorecard
    Allows you to compare your mobile site speed against your peers in over 10 countries. Mobile site speed is based on real-world data from the Chrome User Experience Report.
  • Impact Calculator
    Allows you to estimate the potential revenue opportunity of improving your mobile site speed, based on benchmark data from Google Analytics.
  • Chrome Developer Tools
    Allows you to profile the runtime of a page, as well as identify and debug performance bottlenecks.

See also

top

Reference

top

  1. Developers google.com Search, get started.
  2. Google Fundamentals Perfromance Speed tools.