Technical SEO Tutorials related to PageSpeed and Google Indexing API

Technical SEO Tutorials

Tutorials in English

layout

By default, the <title> tag for this page is determined by the title field (in the Content group). You can override the tag value here.

metaTitle

featuredImage

bottomSections

markdown_content

The description tag is used by search engines and for social sharing. By default, the tag is not set.

metaDescription

If enabled, the title suffix defined in the site configuration is appended to the title tag of this page.

addTitleSuffix

Set the image used when sharing this page on social networks (e.g. Facebook, Twitter). If not set, the default social image defined in the site configuration is used.

socialImage

To add or override any meta tag for this page, add entries to this list. Entries defined here take precedence over any other defaults.

metaTags

title

date

author

excerpt

What about your DevTools Snippets?

I hope you found these examples practical. These snippets are saving me tons of time in double checking and validating SEO Governance and Technical SEO JIRA tickets within the enterprise, on daily basis. I hope you come up with a few of your own, do share them over [Twitter/X @riadjosephs.](https://twitter.com/riadjosephs)


9 Snippets for SEO Efficiency with Chrome DevTools

Using Chrome DevTools for SEO

You might also like

## Index up to 200 URLs per day rapidly

By WebForGood

This tutorial is for those who wish to test out the Google Indexing API. It's suitable for novice users, website managers and webmasters alike. The [original tutorial is in French language on WebForGood](https://webforgood.fr/blog/tutoriel-google-indexing-api-nodejs/ "Google indexing API tutorial in French") 🇫🇷

### Table of content

*   [Concept](#concept)
*   [Quota](#quota)
*   [Before you begin](#before-you-begin)
*   [Summary for agencies, webmasters & devs](#summary-for-agencies-webmasters--devs)
*   [Step by step tutorial](#step-by-step-tutorial)
    *   [1 - Get the source code](#1---get-the-source-code)
    *   [2 - Google Cloud Platform](#2---google-cloud-platform)
        \- [a) Create an account in Google Cloud Platform](#a-create-an-account-in-google-cloud-platform)
        \- [b) Create a new project](#b-create-a-new-project)
        \- [c) Go to API and services](#c-go-to-api-and-services)
        \- [d) Create Credentials](#d-create-credentials)
        \- [e) Create a Service account](#e-create-a-service-account)
        \- [f) Get the private JSON Key](#f-get-the-private-json-key)
        \- [g) The JSON Key content](#g-the-json-key-content)
    *   [3 - Google Search Console](#3---google-search-console)
        \- [a) Open the console](#a-open-the-console)
        \- [b) Settings](#b-settings)
        \- [c) Go to Users and Permissions](#c-go-to-users-and-permissions)
        \- [d) The Service Account email](#d-the-service-account-email)
    *   [4 - Run the indexing script](#4---run-the-indexing-script)
        \- [a) Gather the URLs](#a-gather-the-urls)
        \- [b) Run the code](#b-run-the-code)

### Concept

The aim is to tell Google about new or existing pages, and get their status updated or indexed as soon as possible. You can process multiple URLs (pages) without having to inspect them manually in Google Search Console.

### Quota

200 URLs per day

## Before you begin

Ideally, you would test the API if your website is not in the JobPosting or BroadcastEvent niches. <a href="https://developers.google.com/search/apis/indexing-api/v3/quickstart" rel="noopener noreferrer" target="_blank">As per Google, the API is reserved for JobPosting and BroadcastEvent websites.</a>

You will need the following tools installed on your computer (Mac and PC versions avaiable):

*   Visual Studio Code or equivalent [download from Visual Studio website](https://code.visualstudio.com/ "Visual Studio Code editor")

*   Node JS [Website of Node JS](https://nodejs.org/fr/ "Site de Node JS")

*   And Google Search Console: make sure it is configured for your website and that you have **Owner** rights. [Start page of Google Search Console](https://search.google.com/search-console "Google Search Console")

## Summary for agencies, webmasters & devs

\*If you find this summary too vague, you can read the detailed \*[*step by step tutorial below*](#etapes-detaillees-pour-debutants)

*   Clone this [GitHub repository](https://github.com/swalker-888/google-indexing-api-bulk "Github repo") and run the command "npm i"

```
npm i
```

*   Create an account with **Google Cloud Platform > Console** and then create a new project

*   Search for the [Indexing API](https://console.cloud.google.com/apis/library/browse?q=indexing%20api) in the Library

*   Activate the API **and** its key

*   Create and activate the "Service Account". You should get the **email address of the service account** under the Credentials section.

*   Add this email address as **owner** to your **Google Search Console**

*   Back to Google Cloud Platform, go to "IAM and admin" section, select Service Accounts in the vertical menu on the left handside

*   Click on that email address and go to the Keys tab. Add Key > Create New Key > Choose **format JSON**

*   Allow the private JSON key to download to your computer. Open it in the code editor and copy all of its content and paste it in `service_account.json` by replacing its content. Remember you have downloaded that file from GitHub

*   You are now ready to start **adding the URLs** of the pages you wish to update onto `urls.txt`. Do not leave any empty lines.

*   Open the terminal et run the command `node index.js`

Rince and repeat.

## Step by step tutorial

Assuming you have followed the ["before you begin section"](#avant-de-commencer), proceed with the following steps.

### 1 - Get the source code

a) Download the source code from [Github](https://github.com/swalker-888/google-indexing-api-bulk "Github repo") onto your computer.

![](https://d33wubrfki0l68.cloudfront.net/cdfa124dd7640220aca02ad4e4ee16d0fda62bf0/b9723/images/github-repo-google-indexing-api.png)

b) Create a folder, let's call it "google-indexing-api" for ex, it doesn't really matter what you call it.

c) Click on Download from GitHub and unzip it in the folder you have just created. It should contain 5 files and 1 folder called node_modules.

*Here's an example:*

![](https://d33wubrfki0l68.cloudfront.net/776f43215aa32044d503d3c867c1a905ae56a9c5/89ae2/images/node-modules-et-le-script.png)

d) Open the folder with Visual Studio Code

Then open the terminal small window.

![](https://d33wubrfki0l68.cloudfront.net/46854108377936e89760367398b778a4bb2ae168/4e78e/images/ouvrir-terminal-command.png)

And run the command "npm i" to install the required modules. This is important.

![](https://d33wubrfki0l68.cloudfront.net/4a7a06a2ab67c8efb1f5f2308467b766571120e0/7ec7b/images/apres-ouverture-terminal.png)

It is normal that it should take some time to complete, as long as you're connected to the internet, you'll be fine, and while you wait for it to complete jump to the next step.

***

### 2 - Google Cloud Platform

This is where you create an account (it's free) and then a new project, in order to request the API and its keys, that we are going to need in Visual Studio to start making the requests for Google to index or remove pages.

You got that right, the script runs from your computer (connected to the internet of course).

###### a) Create an account in Google Cloud Platform

Click on "Console" after you have logged in [to the Google Cloud](https://cloud.google.com/ "Google Cloud Platform")

![](https://d33wubrfki0l68.cloudfront.net/b156732f6385147309f7617809d4eb90dc85a745/daf1b/images/cloud-console.png)

###### b) Create a new project

The name of the project is a must have, but the name of the organisation can remain as default "No organisation".

![](https://d33wubrfki0l68.cloudfront.net/9ace2b27cb2b73fa0598dd7c8e74d8a4678c4866/ef258/images/creer-projet.png)

###### c) Go to API and services

Under the vertical menu (left handside), Click on API and services then "Library".

Search with the word "Indexing" and select "Indexing API" .

![](https://d33wubrfki0l68.cloudfront.net/7473f78a2a4988858ff5644d363ff7d3ca62e5f0/798d3/images/api-services-bibliotheque.png)

Activate the API:

![](https://d33wubrfki0l68.cloudfront.net/f04a53b37f0785735133a961197415c48a29c65d/c0f8b/images/activer-api.png)

###### d) Create Credentials

Under the same window of API and services, Click on Credentials (left vertical menu). Click "+ Create Credentials" then "API Key" which you can save (but not mandatory).

![](https://d33wubrfki0l68.cloudfront.net/5a384a5ab3add567c9bd5f7108eebf76cbec736d/2c10a/images/creer-identifiants.png)

###### e) Create a Service account

This is a crucial step, but why?

Because it will generate the unique email address that we need to add to the GSC as owner so that all components are connected.

Give it a name that you can distinguish in the future

As for the ID, it does generate automatically by clicking the small icon on the right handside in that field

![](https://d33wubrfki0l68.cloudfront.net/7978ce196d1861396ea7e333c8b8683d45f5afa0/3f525/images/compte-de-service.png)

Click "Create and continue". A new window opens. Select the role as "Owner".

![](https://d33wubrfki0l68.cloudfront.net/d8ef1e954916859eb1367112e961ec35f0502a20/b8bac/images/role-proprio.png)

Click OK in blue to finalize, you'll see a page like this one below.

In the "Service accounts" section, copy the email address and save it somewhere you can go back to, and add it to the GSC as Owner.

But first we need its private key in JSON format. We will use it as the service_account.json file in a while.

![](https://d33wubrfki0l68.cloudfront.net/72ce86dc4fa4521a3fce5af5a230b53aaf5e5554/b3b0c/images/cle-et-compte.png)

###### f) Get the private JSON Key

In the same window, Click on the email address, a new window opens up.

Click on the KEYS tab (on top).

![](https://d33wubrfki0l68.cloudfront.net/cd29956e882ac041764408829a85906ab6543c06/2a897/images/cle-json\_1.png)

Click Add Key, then Create Key and select JSON format.

![](https://d33wubrfki0l68.cloudfront.net/3c8ae7f872a856e71c6eded4a355a28689b18260/f3295/images/cle-json\_2.png)

![](https://d33wubrfki0l68.cloudfront.net/cf586e9ecb690b35b6c2411b0b4eda0d8350db95/3d26f/images/cle-json\_3.png)

The JSON file will download to your computer and a message appears confirling that.

###### g) The JSON Key content

Copy all of the content of the JSON file after opening it in your code editor. Here's an example of how it should look like.

And paste the content onto the file `service_account.json`replacing all the original code that was downloaded from GitHub.

![](https://d33wubrfki0l68.cloudfront.net/1fc87a446f9ebb9f3bcf5b478a6841936782c020/5c2b4/images/cle-privee-json.png)

The `service_account.json` file should look like this:

![](https://d33wubrfki0l68.cloudfront.net/153d4fd1376bc47d2c806dad9a101e2fcee20b2b/e4c9e/images/copier-coller-cle-privee.png)

Wonderful, so far so good, you're almost there ⭐️

***

### 3 - Google Search Console

Again, the aim here is to add the email address of the Service Account as Owner of that particular Google Search Console account.

###### a) Open the console

You can visit the [Google Search Console](https://search.google.com/search-console "Google Search Console") and choose your website in question.

###### b) Settings

Visit the Settings page, found under the left handside vertical menu.

![](https://d33wubrfki0l68.cloudfront.net/3680e42b17f32130c6e66b36afc9125194a78f48/a89e6/images/gsc-proprio.png)

###### c) Go to Users and Permissions

Click on Add user, and set the Permission to Owner.

![](https://d33wubrfki0l68.cloudfront.net/e41d023668956a94525e2073ac24979b135455cc/67318/images/utilisateur-proprio.png)

###### d) The Service Account email

Add that email as owner

![](https://d33wubrfki0l68.cloudfront.net/00ae37e1eda7a9e935acf807469314c70be9efdb/92c85/images/ajouter-proprio.png)

💫 Congrats! You are set and ready to start indexing rapidly 200 URLs per day 🏆

***

### 4 - Run the indexing script

This is done from your Visual Studio Code or code editor.

###### a) Gather the URLs

Gather the URLs of the pages that you'd like indexed and paste them in the file called `urls.txt`. Do not leave empty lines.

Example :

![](https://webforgood.fr/images/Screenshot%202022-03-28%20at%2000.03.02.png)

###### b) Run the code

Now that the URLs are set in the file `urls.txt.`

The file `index.js` will do the work for us, we just need to run it. Here's how:

In the terminal window, type `node index.js` and hit enter

Here's an example response from the server:

![](https://webforgood.fr/images/Screenshot%202022-03-28%20at%2001.21.36.png)

In a few minutes/hours, your pages will be indexed ✨

***

Questions, comments, errors, something not working, not clear? Ask on [Discord](https://discord.com/invite/2tABYc3kDn "Discussions sur Discord") or Twitter[@webforgoodf](https://twitter.com/webforgoodf) or Facebook [@webforgoodf](https://www.facebook.com/WebForGoodFr)

Thank you for following along 🚀

Credits and thanks to Steve from Journey Further for the source code on GitHub.


Tutorial: How to use Google Indexing API, for fast and bulk indexing of URLs, using Node JS

Using Google Indexing API - English Tutorial

Speed and performance bulk testing with PageSpeed Insights API

Manually testing page performance can be time-consuming. With this tutorial, test multiple URLs at once using Google's PageSpeed Insights API and a NodeJS.

Technical SEO Tutorials

Tutorials in English

Using Chrome DevTools for SEO

Using Google Indexing API - English Tutorial

A Comprehensive Guide to Bulk Testing Multiple URLs with Google PageSpeed Insights API