- Sitemaps in SureRank
- How to Enable Video Sitemap in SureRank Pro
- How to Enable the News Sitemap in SureRank
- How to Show the HTML Sitemap on Your Site in SureRank Pro
- How to Regenerate the Sitemap After Excluding a Post Type in SureRank
- Change the Sitemap URL in SureRank
- How to Enable Author Sitemap in SureRank
- How to Fix WWW and Non-WWW Version Redirects to Improve Your SEO
- How to Fix: No H1 Heading Found on Your Homepage
- How to Fix Missing H2 Headings on Your Homepage
- Re-run Checks Button in SureRank
- Fix Critical Error: Another SEO Plugin Detected in SureRank
- Fix Warning: Site Tagline Is Not Set in SureRank
- How to Fix Multiple SEO Plugins Detected on Your Site
- How to Fix: Homepage is Not Indexable by Search Engines
- Warning: Homepage Does Not Contain Internal Links
- How to Fix Missing Alt Text on Homepage Images
- How to Fix: Search Engine Title is Missing on the Page
- Page Level SEO: Broken Links Detected
- How to Fix Missing Alt Text on Images
- How to Fix Page URLs That Are Too Long
- Page Level SEO Warning: No Links Found on This Page
- Page Level SEO Warning: No Images or Videos Found
- Page Level SEO Warning: Missing Search Engine Description
- Page Level SEO Warning: No Subheadings Found on This Page
- Page Level SEO Warning: Canonical Tag is Missing
- Page Level SEO Warning: Open Graph Tags Missing
- What is Google Search Console and how does SureRank use it?
- Recommended Image Sizes
- SureRank – SEO Check Severity Guide
- Using SureRank with Other SEO Plugins – Best Practices
- Import/Export Feature – SureRank Plugin
- What is llms.txt and Does SureRank Support It?
- Does SureRank offer a keyword rank-tracking feature?
- Does SureRank Come With Google Analytics Integration?
- Email Summary in SureRank
- SureRank Role Manager
- Using the Google Indexing API with SureRank
- Customize Final Title Tag surerank_final_title
- Customize Post Type Archive Title Output surerank_post_type_archive_title
- Customize Archive Page Title with surerank_archive_title
- CustomizeModify the Search Results Page Title surerank_search_title
- Customizing the 404 Page Title surerank_not_found_title
- Customizing the Title Separator surerank_title_separator
- How to Remove Archive Prefixes from Titles Using SureRank
- Customize Homepage Pagination Format surerank_homepage_pagination_format
- Customize Maximum SEO Title Length surerank_title_length
- Enable/Disable Pagination in SureRank Archives surerank_show_pagination
Using the Google Indexing API with SureRank
SureRank allows you to notify Google when your pages are updated or deleted using the Google Indexing API. This helps Google discover important changes more quickly. Before getting started, please complete the setup steps outlined below.
Step 1: Create a Google Cloud Project
To use the Google Indexing API, you must first create a Google Cloud project and enable the API. Open Google Cloud Console.
Open the Project Selector
In the top left corner of the console, click on the project dropdown. It may show an existing project name or say “Select a project”.
Create a New Project
- Click on “New Project”.
- Enter a name for your project. The Project ID will be generated automatically. If applicable, select an organization. Otherwise, leave it as the default.
- Then click on Create
Enabling the Indexing API Using Direct Link
After creating the Google Cloud project, visit this link.
From the project list, select the Google Cloud project you created earlier.
After selecting the project, you will be redirected to the Indexing API enablement screen.Google will ask you to confirm whether you want to enable the API for the selected project.
Click on Enable to activate the Indexing API for the project.
Step 2: Create a Service Account
Next, create a service account in your Google Cloud project and download the JSON key file.
To create a service account, visit: https://console.cloud.google.com/
Once logged in, select the project you recently created. Click on the menu icon

Navigate to IAM & Admin, then select Service Accounts.
Next, you will be redirected to the Service Accounts page. Click on Create Service Account.
Enter a service account name that suits your project or business requirements. A Service Account ID and email address will be generated automatically. Make sure to save this email address for future reference.
After saving the email address, click Done. This will create the service account.
Once the service account is created, you will be redirected to the Service Accounts page, where the newly created account will be listed.
Click on the three dots next to the service account and select Manage keys.
Inside the Manage keys section, click on Add key and then select Create new key.
Select JSON as the key type and click Create.
Once you click on Create, the JSON key file will be automatically downloaded to your device.
Step 3: Add the Service Account to Google Search Console
After downloading the JSON key, you need to grant the service account access to Google Search Console.
Open Google Search Console for your website.
Go to Settings and then navigate to Users and permissions.
Click on Add User.
Enter the service account email address that you saved earlier and assign Owner permission.
Once added, the service account will appear in the users list with Owner access.
Step 4: Configure Google Indexing in SureRank
After completing the setup in Google Cloud and Google Search Console, you can configure Google Indexing in your WordPress dashboard.
Open the WordPress dashboard and navigate to SureRank.
Go to the Advanced section and click on Google Indexing Settings.
Enable Automatic Google Indexing if you want SureRank to automatically notify Google about page updates.
Open the Service Account JSON key file that was downloaded earlier. Copy the entire JSON content and paste it into the Service Account JSON Key field.
Make sure there are no extra spaces at the beginning or end of the pasted content.
Click on Save and Test Connection.
If everything is configured correctly, the connection status will be shown as successful.
We don't respond to the article feedback, we use it to improve our support content.