Google Bulk Indexer
Python script for automatically submitting website pages for indexing in bulk to Google Search Console(GSC). This is a Python version of the original work in google-indexing-script
Functionality
This script submits the website URLs found on a site that you own to GSC for indexing. There is no guarantee that the page requested for indexing will be indexed by Google.
Requirements
- Python >= 3.9
- A Google Cloud account: You will have to create a service account under a Google cloud project and download the private key JSON file.
- GSC account with a verified site (property).
Before you run the script
Follow the guide by Google Cloud to setup Google Cloud account and service account. You should have the following by the end:
- A google cloud account with a project that has both
Google Search Console APIandWeb Search Indexing APIenabled. - A service account and a private key json file downloaded on your PC.
- The service account email added to your property (site) as Site owner.
Running the script
- Clone this repository on your local PC which has Python installation.
- Install the required packages by running the below command
pip install -r requirements.txt
- Copy the private key file that you downloaded from the Google cloud account in the same folder. Private key is needed for submitting URLs to Google Search Console for indexing.
- Run the following command to start submitting URLs for indexing
- If you have verified your site as a
Domainproperty in GSC run the following command
python ./main.py -p <your-domain.xyz>
- If you have verified your site as a
URL Prefixproperty, run the below command
python ./main.py -p https://<your-domain.xyz> - If you have verified your site as a
If you have the private key json file somewhere else on your PC, you can specify the path while running the script
python ./main.py -c <path to private key file> -p <site domain>
Run the script with --help to know about command line options.
Metadata
Release files for gsc-bulk-indexer 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gsc_bulk_indexer-0.1.0.tar.gz | 8.7 kB | Without provenance | Details for gsc_bulk_indexer-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gsc_bulk_indexer-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for gsc_bulk_indexer-0.1.0-py3-none-any.whl |
Total release size: 18.4 kB
Release files / gsc_bulk_indexer-0.1.0.tar.gz
| Download URL | gsc_bulk_indexer-0.1.0.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a9b37c07c77264e796cc711f88934933597c40c72a8a360f781a9ce24d4ae339
|
|
BLAKE2b-256 checksum How to use checksums |
2b30fc6c3aa59ba93cc2a5926b903fc1946ef2f72487beedab1543e57ebb318a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.9.18 Darwin/21.4.0
|
Release files / gsc_bulk_indexer-0.1.0-py3-none-any.whl
| Download URL | gsc_bulk_indexer-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b5bfc779b73672789ca75689407c54bf7d8682f0367c32d809db771f5d67ddfa
|
|
BLAKE2b-256 checksum How to use checksums |
e0dd7b188ceab27b903a1a68114db3c80bc99eb6eee69eca49d88d6c80360800
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.9.18 Darwin/21.4.0
|
Security for gsc-bulk-indexer 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.