List of ping services - does it still work in 2026?

In the WordPress dashboard, under Settings > Writing, there is still a small field called “Update Services”. For years, “magic ping lists” with hundreds of addresses (rpc.pingomatic.com, technorati and so on) circulated online, supposedly getting your post into Google within 5 minutes. In 2026 those lists are outdated and ineffective. This article explains why pinging lost its value and what to do instead to get your site indexed by search engines.

#Does pinging in WordPress still work in 2026

Pinging in WordPress is a relic of the past, and for most webmasters today it does more harm than good. Most services on those old lists no longer exist, and the ones still running are not followed by any serious search engine. Google has not relied on RPC “pings” since 2012, and Microsoft promotes its own IndexNow protocol instead of traditional pinging. Googlebot is now advanced enough to discover pages on its own through crawling and sitemap analysis.

Search engine algorithms have evolved to the point where the old ways of announcing new content no longer carry much weight. Modern Google crawlers work continuously and automatically, watching for changes on websites without needing explicit notifications. So even if your WordPress site sends a ping to a ping service, the search engine will check your sitemap first and only then (if at all) pay attention to any extra signals.

In practice, adding hundreds of ping services to the “Update Services” list in WordPress will not speed up indexing in Google. It can even slow down publishing, because WordPress tries to connect to every service on the list and waits for a confirmation. With inactive or unreachable services this can take several seconds, which gets particularly annoying when you publish many posts at once.

#Why pinging stopped working

Before moving on to modern indexing methods, it helps to understand why traditional pinging stopped being effective. That background makes it easier to follow how indexing has evolved and to pick the right strategy for your own site deliberately.

Technical reasons pinging declined:

The first and most important reason is that ping services shut down en masse over the last fifteen years. Services such as Technorati, Google Blog Search and Weblogs.com, once the backbone of the blogging ecosystem, have long since disappeared or stopped supporting the XML-RPC ping protocol. Pinging services that no longer exist brings no benefit at all and adds needless delays and server load.

The second key reason is a fundamental change in how search engines discover and index content. Google officially announced in 2012 that it does not rely on ping services to discover new pages. Instead, the company focused on building out its own crawler infrastructure, which can find new pages on its own by analysing links and sitemaps. This strategic shift was a response to the growing amount of ping spam and fake notifications.

The third factor is the standardisation of the XML sitemap format, which became the preferred way for webmasters and search engines to communicate. SEO plugins such as Yoast SEO or Rank Math generate sitemaps automatically and update them whenever content on the site changes. This automation is far more reliable and complete than traditional pinging, because it covers every content type, not just blog posts.

The fourth reason is security. Ping services were repeatedly abused for DDoS attacks and other misuse. Many servers blocked outbound traffic on the ports used by the XML-RPC protocol, which limited the reach of pinging even further. Current security practice favours controlled, centralised notification methods such as the Google Indexing API.

What this means in practice for site owners:

The consequences for site owners are clear. A ping to a service that no longer exists does not speed up indexing, and it delays publishing the post, because WordPress waits for a reply from every service on the list. Repeated pings waste server resources and add network load. Most importantly, relying on pinging can create a false sense of security while the site owner neglects the technical SEO methods that actually matter.

#History of pinging in WordPress since 2003

Knowing the history of pinging explains why the technique was considered effective for so long and why it is outdated today. It is also a good window into how the web evolved and how the approach to indexing content changed.

#How pinging worked from 2003 to 2008

In the early days of blogging, pinging was a new idea that changed how search engines found new content. When you published a new post, WordPress sent an XML-RPC signal to content aggregators. Those services then visited your site, indexed the content and published a link to your article in their directory. The whole process could take just a few minutes, which was unthinkable compared with the weeks of waiting for indexing through traditional methods.

A typical ping list from those years contained dozens or even hundreds of services. The most important ones were: http://rpc.pingomatic.com/, the aggregator of aggregators, which distributed pings to many services at once; http://technorati.com/ping/, then the most popular blog service and in effect a blog search engine; http://weblogs.com/, one of the first ping services, running since 1999; http://blogsearch.google.com/ping/, Google Blog Search, Google’s dedicated blog search engine; http://ping.feedburner.com/, FeedBurner, a service for managing RSS feeds; and http://rpc.weblogs.com/RPC2, Weblogs.com, a blog aggregator.

Pinging worked for a few key reasons that may seem obvious now but were a breakthrough at the time. First, search engines depended on external signals to discover new pages, because their own crawlers were far less advanced than today’s. Second, ping services often created backlinks to the pinged sites, which was a form of natural link building. Third, indexing was unprecedentedly fast: a post could be indexed within minutes, not hours or days.

#Why pinging lost its value between 2008 and 2015

As Google and its own crawler developed, pinging steadily lost importance. Googlebot learned to discover pages more efficiently by analysing links from already indexed pages, XML sitemaps and browser add-ons for webmasters. Ping services began closing one after another: Technorati stopped handling pings around 2010, Google Blog Search was shut down in 2011, and FeedBurner lost relevance after Google acquired it.

During this period SEO plugins started promoting XML sitemaps as the preferred indexing method. Yoast SEO, which in 2010 was still at version 1.0, introduced automatic sitemap generation as one of its key features. Somewhat paradoxically, this shift coincided with Google’s algorithms growing ever more complex, which pushed site owners towards a more thorough approach to technical SEO.

#How indexing changed from 2016 to 2026

The last decade brought a complete change in how indexing works. Google focused on Core Web Vitals and user experience as key ranking factors. The introduction of mobile-first indexing in 2019 forced site owners to go responsive and optimise for mobile. In 2026 Google promotes AI Overviews and expects Schema.org structured data for content that should appear in synthesised answers.

At the same time, Microsoft introduced the IndexNow protocol as an alternative to traditional pinging. IndexNow is far more advanced than the old RPC pings: it uses cryptographic keys to verify site ownership and supports notifications about deleted pages, not just new ones. Bing and Yandex actively promote the protocol, which makes it a real alternative to Google’s methods.

#Which indexing methods work in 2026

Rather than wasting time on outdated ping lists, focus on the methods that deliver results. Below is a detailed look at every modern indexing method, with practical implementation tips.

#1. XML sitemap in WordPress

The XML sitemap is the absolute baseline of any indexing strategy in 2026. It is an XML file listing every URL on your site, together with extra information such as the last modification date, change frequency and priority. SEO plugins generate sitemaps automatically and update them whenever content changes.

For standard WordPress sites:

Yoast SEO automatically generates /sitemap_index.xml plus separate sitemaps for individual content types. The Yoast sitemap structure includes post-sitemap.xml for posts, page-sitemap.xml for pages, category-sitemap.xml for categories, tag-sitemap.xml for tags, and many more for custom post types and taxonomies. Rank Math builds a similar structure but usually uses a single sitemap.xml file as the main entry point. All in One SEO generates /sitemap.xml as the main sitemap.

XML sitemap structure:

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="https://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://example.com/post-sitemap.xml</loc>
    <lastmod>2026-01-29T10:00:00+00:00</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/page-sitemap.xml</loc>
    <lastmod>2026-01-28T15:30:00+00:00</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/category-sitemap.xml</loc>
    <lastmod>2026-01-29T08:00:00+00:00</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/product-sitemap.xml</loc>
    <lastmod>2026-01-29T09:45:00+00:00</lastmod>
  </sitemap>
</sitemapindex>

Adding a sitemap to Google Search Console:

Adding a sitemap to Google Search Console is simple, but the details matter. First, sign in to Google Search Console and pick your site from the property list. Then open the “Sitemaps” section in the left-hand menu. In the “Add a new sitemap” field, enter the URL of your main sitemap, for example https://your-site.com/sitemap_index.xml for Yoast SEO or https://your-site.com/sitemap.xml for Rank Math. Click “Submit” and wait for confirmation. Google usually confirms receipt of the sitemap within a few minutes, but full indexing can take 24 to 48 hours.

Advanced sitemap configuration:

// functions.php - zaawansowana konfiguracja sitemap w Yoast SEO

// Dostosuj priorytety w sitemap
add_filter( 'wpseo_sitemap_post_priorities', 'wppoland_sitemap_priorities' );
function wppoland_sitemap_priorities( $priorities ) {
    // Najwyższy priorytet dla strony głównej
    $priorities['home'] = '1.0';
    // Wysoki priorytet dla stron i wpisów
    $priorities['post'] = '0.8';
    $priorities['page'] = '0.8';
    // Średni priorytet dla produktów
    $priorities['product'] = '0.7';
    // Niższy priorytet dla archiwów
    $priorities['archive'] = '0.3';
    // Bardzo niski priorytet dla załączników
    $priorities['attachment'] = '0.1';
    return $priorities;
}

// Wyklucz określone strony z sitemap
add_filter( 'wpseo_sitemap_exclude_post_type', function( $exclude, $post_type ) {
    return $exclude || $post_type === 'nasz-wykluczony-typ';
}, 10, 2 );

// Dodaj niestandardowe URL do sitemap
add_filter( 'wpseo_sitemap_additional_urls', 'wppoland_custom_sitemap_urls' );
function wppoland_custom_sitemap_urls( $urls ) {
    $urls[] = [
        'loc' => 'https://twoja-strona.pl/strona-bez-wordpressa/',
        'prio' => 0.5,
        'changefreq' => 'monthly',
        'lastmod' => date( 'c' ),
    ];
    return $urls;
}

#2. Google Indexing API for shops and job listings

The Google Indexing API is an advanced tool for sites that need immediate indexing. It is a dedicated API that lets you notify Google directly about new, updated or deleted pages. Unlike traditional pinging, the Indexing API gets an almost immediate response from Googlebot.

When the Indexing API is worth using:

The Indexing API is especially useful for sites with dynamic content that changes often and needs to be indexed right away. Online shops can use it to tell Google about new products, price changes and stock levels. Job boards can announce new listings immediately. Event sites can update information about upcoming events. Real estate sites can announce new listings.

Implementing the Indexing API in WordPress:

<?php
/**
 * Google Indexing API dla WordPress
 * Wymaga: Google Cloud Console project z włączonym Indexing API
 * Wymaga: Serwis account key JSON file
 */

class WPPoland_Indexing_API {

    private $api_key;
    private $service_account_file;
    private $site_url;

    public function __construct() {
        $this->api_key = defined('GOOGLE_INDEXING_API_KEY') ? GOOGLE_INDEXING_API_KEY : '';
        $this->service_account_file = defined('GOOGLE_SERVICE_ACCOUNT_FILE') ? GOOGLE_SERVICE_ACCOUNT_FILE : '';
        $this->site_url = get_site_url();

        // Hook do powiadamiania przy publikacji
        add_action( 'publish_post', [ $this, 'notify_google' ] );
        add_action( 'publish_page', [ $this, 'notify_google' ] );

        // Dla niestandardowych typów postów
        add_action( 'publish_product', [ $this, 'notify_google' ] );
        add_action( 'publish_job', [ $this, 'notify_google' ] );
    }

    /**
     * Powiadom Google o zmianie na stronie
     */
    public function notify_google( $post_id ) {
        $url = get_permalink( $post_id );
        return $this->send_notification( $url, 'URL_UPDATED' );
    }

    /**
     * Powiadom o usunięciu strony
     */
    public function notify_deletion( $url ) {
        return $this->send_notification( $url, 'URL_DELETED' );
    }

    /**
     * Wyślij powiadomienie do Google Indexing API
     */
    private function send_notification( $url, $type = 'URL_UPDATED' ) {
        $endpoint = 'https://indexing.googleapis.com/v3/urlNotifications:publish';

        // Użyj OAuth 2.0 z serwis account
        $access_token = $this->get_access_token();

        if ( ! $access_token ) {
            error_log( 'Google Indexing API: Nie udało się uzyskać access token' );
            return false;
        }

        $headers = [
            'Content-Type' => 'application/json',
            'Authorization' => 'Bearer ' . $access_token,
        ];

        $body = [
            'url' => $url,
            'type' => $type,
        ];

        $response = wp_remote_post( $endpoint, [
            'headers' => $headers,
            'body'    => json_encode( $body ),
            'timeout' => 30,
        ] );

        if ( is_wp_error( $response ) ) {
            error_log( 'Google Indexing API Error: ' . $response->get_error_message() );
            return false;
        }

        $response_body = json_decode( wp_remote_retrieve_body( $response ), true );

        // Sprawdź czy Google potwierdził otrzymanie
        if ( isset( $response_body['urlNotificationMetadata']['latestUpdate']['status'] ) ) {
            return true;
        }

        return false;
    }

    /**
     * Uzyskaj access token z serwis account
     */
    private function get_access_token() {
        if ( empty( $this->service_account_file ) || ! file_exists( $this->service_account_file ) ) {
            return false;
        }

        $credentials = json_decode( file_get_contents( $this->service_account_file ), true );

        if ( ! isset( $credentials['private_key'] ) ) {
            return false;
        }

        $jwt = $this->create_jwt( $credentials );

        // Wymień JWT na access token
        $token_url = 'https://oauth2.googleapis.com/token';

        $response = wp_remote_post( $token_url, [
            'body' => http_build_query([
                'grant_type' => 'urn:ietf:params:oauth:grant-type:jwt-bearer',
                'assertion' => $jwt,
            ]),
            'timeout' => 30,
        ] );

        if ( is_wp_error( $response ) ) {
            return false;
        }

        $body = json_decode( wp_remote_retrieve_body( $response ), true );

        return isset( $body['access_token'] ) ? $body['access_token'] : false;
    }

    /**
     * Utwórz JWT dla serwis account
     */
    private function create_jwt( $credentials ) {
        $header = [
            'alg' => 'RS256',
            'typ' => 'JWT',
        ];

        $now = time();
        $exp = $now + 3600; // Token ważny przez godzinę

        $payload = [
            'iss' => $credentials['client_email'],
            'sub' => $credentials['client_email'],
            'aud' => 'https://oauth2.googleapis.com/token',
            'iat' => $now,
            'exp' => $exp,
            'scope' => 'https://www.googleapis.com/auth/indexing',
        ];

        $base64_header = rtrim( strtr( base64_encode( json_encode( $header ) ), '+/', '-_' ), '=' );
        $base64_payload = rtrim( strtr( base64_encode( json_encode( $payload ) ), '+/', '-_' ), '=' );

        // Podpisz JWT (uproszczona implementacja - w produkcji użyj biblioteki)
        $signature = '';
        openssl_sign( $base64_header . '.' . $base64_payload, $signature, $credentials['private_key'], 'sha256WithRSAEncryption' );

        return $base64_header . '.' . $base64_payload . '.' . rtrim( strtr( base64_encode( $signature ), '+/', '-_' ), '=' );
    }
}

// Inicjalizacja (dodaj w functions.php lub mu-plugins)
// require_once get_template_directory() . '/indexing-api.php';
// new WPPoland_Indexing_API();

Alternative: the Rank Math Instant Indexing plugin:

If you do not want to implement the Indexing API yourself, you can use Rank Math, which has a built-in “Instant Indexing” feature. Once Rank Math is installed and the Indexing API is configured in Google Cloud Console, the plugin automatically notifies Google about every change on the site. This is a much simpler solution that needs less technical setup.

#3. IndexNow for Bing and Yandex

IndexNow is a protocol created by Microsoft that lets you notify search engines immediately about new and updated content. Unlike traditional pinging, IndexNow uses cryptographic keys to verify site ownership, which rules out fake notifications.

Supported search engines:

IndexNow is currently supported by Bing and Yandex. Microsoft actively promotes the protocol as an industry standard and encourages other search engines to adopt it. Yandex plays a small role in most Western markets, but it is widely used in Russia and neighbouring countries.

Implementing IndexNow in WordPress:

<?php
/**
 * IndexNow dla WordPress
 * Protokół Microsoft/Bing do natychmiastowej indeksacji
 */

// Definiuj klucz IndexNow w wp-config.php
// define( 'INDEXNOW_API_KEY', 'twój-unikalny-klucz-32-znaków' );

add_action( 'wp_head', 'wppoland_indexnow_key_tag' );
add_action( 'publish_post', 'wppoland_notify_bing_indexnow' );
add_action( 'publish_page', 'wppoland_notify_bing_indexnow' );

/**
 * Dodaj meta tag z kluczem IndexNow do sekcji head
 */
function wppoland_indexnow_key_tag() {
    if ( ! defined( 'INDEXNOW_API_KEY' ) || empty( INDEXNOW_API_KEY ) ) {
        return;
    }

    // Dodaj klucz tylko na stronach pojedynczych
    if ( is_singular() ) {
        echo '<meta name="key" content="' . esc_attr( INDEXNOW_API_KEY ) . '" />' . "\n";

        // Opcjonalnie: dodaj lokację klucza
        $key_location = get_site_url() . '/' . INDEXNOW_API_KEY . '.txt';
        echo '<meta name="keyLocation" content="' . esc_url( $key_location ) . '" />' . "\n";
    }
}

/**
 * Powiadom Bing o nowym/zaktualizowanym wpisie
 */
function wppoland_notify_bing_indexnow( $post_id ) {
    if ( ! defined( 'INDEXNOW_API_KEY' ) || empty( INDEXNOW_API_KEY ) ) {
        return;
    }

    // Sprawdź czy to jest publikacja (nie rewizja)
    if ( wp_is_post_revision( $post_id ) ) {
        return;
    }

    $url = get_permalink( $post_id );
    $key = INDEXNOW_API_KEY;
    $key_location = get_site_url() . '/' . $key . '.txt';

    $bing_endpoint = 'https://www.bing.com/indexnow';

    $response = wp_remote_post( $bing_endpoint, [
        'body' => json_encode([
            'host' => parse_url( get_site_url(), PHP_URL_HOST ),
            'key' => $key,
            'keyLocation' => $key_location,
            'urlList' => [ $url ],
        ]),
        'headers' => [
            'Content-Type' => 'application/json',
        ],
        'timeout' => 15,
    ] );

    // Loguj wynik dla celów debugowania
    if ( is_wp_error( $response ) ) {
        error_log( 'IndexNow Error: ' . $response->get_error_message() );
    } else {
        $status = wp_remote_retrieve_response_code( $response );
        if ( $status == 200 ) {
            error_log( 'IndexNow: Successfully notified Bing about ' . $url );
        }
    }
}

/**
 * Utwórz plik klucza IndexNow w katalogu głównym strony
 * Wywołaj tę funkcję przy aktywacji motywu lub wtyczki
 */
function wppoland_create_indexnow_key_file() {
    if ( ! defined( 'INDEXNOW_API_KEY' ) || empty( INDEXNOW_API_KEY ) ) {
        return;
    }

    $key_file = ABSPATH . INDEXNOW_API_KEY . '.txt';

    // Jeśli plik nie istnieje, utwórz go
    if ( ! file_exists( $key_file ) ) {
        $handle = fopen( $key_file, 'w' );
        fwrite( $handle, INDEXNOW_API_KEY );
        fclose( $handle );
    }
}
register_activation_hook( __FILE__, 'wppoland_create_indexnow_key_file' );

Creating the IndexNow key file:

You also need to create a text file with your IndexNow key in the root directory of your site. The file name must match your key, and the file must contain only the key. For example, if your key is abc123def456ghi789jkl012mno345pqr, create the file abc123def456ghi789jkl012mno345pqr.txt in the root directory of the site (where wp-config.php lives) and put the key inside it.

#4. Submitting your RSS feed to aggregators

RSS feeds remain an important content distribution channel in 2026, although their role in indexing is smaller than it used to be. Feed aggregators such as Feedly, Bloglovin’ and Inoreader automatically fetch and index content from subscribed feeds, which can help search engines discover a site sooner.

WordPress feed URLs:

WordPress automatically generates several types of feeds for your site. The main feed for the whole site lives at https://your-site.com/feed/. A feed for a specific category is https://your-site.com/category/category-name/feed/. A feed for a tag is https://your-site.com/tag/tag-name/feed/. A feed for a specific author is https://your-site.com/author/author-name/feed/. A feed for a custom post type is https://your-site.com/feed?post_type=type-name.

Registering feeds with aggregators:

Feedly (https://feedly.com) is the most popular RSS aggregator in the world. Users only need to enter your feed URL in Feedly to get automatic notifications about new content. Feedly also indexes feeds in its own search, which can increase the visibility of your content. Bloglovin’ (https://www.bloglovin.com) is popular with bloggers and people who follow trends. Inoreader (https://inoreader.com) offers advanced automation features and can be used to set up alerts for specific keywords.

#5. WordPress embeds and oEmbed

oEmbed is a protocol that lets one site embed content from another without copying HTML code. When another site links to your article using oEmbed, it signals to search engines that your content is valuable and worth indexing.

WordPress automatically supports oEmbed for many popular services, including YouTube, Twitter/X, Instagram, Vimeo and many others. If another WordPress site links to your article, WordPress automatically tries to fetch the metadata and show a preview of your article. This process generates signals that can help with indexing.

#6. Submitting to Google News and industry indexes

For specialised content, it is worth considering submission to dedicated indexes and industry directories. Google News (https://news.google.com) is a news index that is particularly valuable for sites publishing news and current information. Bing News is the Microsoft equivalent. Google Scholar (https://scholar.google.com) is an index of academic publications, ideal for scientific content. Industry-specific directories can be valuable for particular niches.

#Sitemap vs Indexing API vs IndexNow compared

The right indexing method depends on the type of site, how often it is updated and the resources available. The table below compares all the methods discussed:

Recommendations by site type:

For a personal blog, an XML sitemap plus Google Search Console is enough. Pingomatic is optional but will not hurt. Avoid adding hundreds of ping services to the list in WordPress.

For an online shop, an XML sitemap plus the Google Indexing API is recommended. IndexNow for Bing is optional. Set up automatic notifications for new products and price changes.

For a job board, the Indexing API is essential. Job listings lose value if they are not indexed immediately. Set up URL_UPDATED notifications for updates and URL_DELETED for removed listings.

For a multilingual site, set up separate sitemaps for each language. Use hreflang in the HTML. Submit each sitemap separately to Google Search Console.

For a local business site, an XML sitemap plus links from your Google Business Profile are key. Consider LocalBusiness Schema.org markup. Submit the site to local directories.

#How to optimise indexing in WordPress

#Sitemaps in Yoast SEO, Rank Math and All in One SEO

Yoast SEO is the most popular SEO plugin for WordPress, with more than 12 million active installations. It automatically generates /sitemap_index.xml with all content types. It offers Google Search Console integration directly from the WordPress dashboard. It updates the sitemap automatically when you publish new posts. It has built-in schema.org and E-E-A-T features. It requires WordPress 6.0 or later.

Rank Math is a lighter, increasingly popular alternative. It builds multiple sitemaps under a single /sitemap.xml file. It has a built-in “Instant Indexing” module for the Google Indexing API. It offers automatic notifications about new content. It has built-in support for Schema.org and local SEO. It is compatible with WooCommerce and Easy Digital Downloads.

All in One SEO is a simple plugin for beginners. It generates /sitemap.xml with basic data. It offers settings import and export. It has a simple step-by-step setup wizard. The Pro version adds WooCommerce integration and Video SEO.

#How to send IndexNow and pings automatically on publish

<?php
/**
 * Automatyzacja indeksacji w WordPress
 * Ten kod dodaje automatyczne powiadomienia przy publikacji
 */

// Wywołaj powiadomienie przy każdej publikacji
add_action( 'publish_post', 'wppoland_notify_indexing_services' );
add_action( 'publish_page', 'wppoland_notify_indexing_services' );
add_action( 'publish_product', 'wppoland_notify_indexing_services' );
add_action( 'publish_job', 'wppoland_notify_indexing_services' );

function wppoland_notify_indexing_services( $post_id ) {
    // Pomiń rewizje
    if ( wp_is_post_revision( $post_id ) ) return;

    // Pomiń automatyczne zapiski
    if ( wp_is_post_autosave( $post_id ) ) return;

    // Pomiń wpisy z noindex
    if ( get_post_meta( $post_id, '_yoast_wpseo_meta-robots-noindex', true ) ) return;

    $url = get_permalink( $post_id );

    // 1. Pingomatic (tradycyjny ping - niskie znaczenie)
    wp_remote_post( 'http://rpc.pingomatic.com/', [
        'body' => xmlrpc_encode_request( 'weblogUpdates.ping', [ get_bloginfo( 'name' ), $url ] ),
        'timeout' => 5,
    ]);

    // 2. IndexNow dla Bing (jeśli skonfigurowany)
    if ( defined( 'INDEXNOW_API_KEY' ) && ! empty( INDEXNOW_API_KEY ) ) {
        wp_remote_post( 'https://www.bing.com/indexnow', [
            'body' => json_encode([
                'host' => parse_url( get_site_url(), PHP_URL_HOST ),
                'key' => INDEXNOW_API_KEY,
                'urlList' => [ $url ],
            ]),
            'headers' => [
                'Content-Type' => 'application/json',
            ],
            'timeout' => 10,
        ]);
    }

    // 3. Opcjonalnie: Indexing API dla Google (wymaga konfiguracji)
    // Tutaj dodaj kod z sekcji Google Indexing API

    log_indexing_notification( $post_id, $url );
}

/**
 * Logowanie powiadomień indeksacji
 */
function log_indexing_notification( $post_id, $url ) {
    if ( defined( 'WP_DEBUG_LOG' ) && WP_DEBUG_LOG ) {
        error_log( sprintf( '[Indexing] Powiadomienie wysłane dla: %s (ID: %d)', $url, $post_id ) );
    }
}

#What is changing in indexing in 2026

#How Core Web Vitals and AI Overviews affect indexing

2026 brings several significant changes in how search engines index and evaluate websites. Understanding these trends will help you adapt your indexing strategy to current requirements.

Core Web Vitals carry more weight, a trend continuing from previous years. Slow pages get indexed less often, because Googlebot has a limited crawl budget and prefers pages that load quickly. Pages with good LCP (Largest Contentful Paint), FID (First Input Delay) and CLS (Cumulative Layout Shift) scores get higher indexing priority. Optimise images, minimise JavaScript and use lazy loading to improve your Core Web Vitals.

AI Overviews in Google is a feature that shows synthesised AI answers to user queries. For your content to be included in AI Overviews, it needs to be well structured and carry Schema.org data. Implement JSON-LD schema for articles, products, FAQ, HowTo and other content types. Unique, in-depth content has a better chance of appearing in synthesised answers.

Mobile-first indexing is now the standard rather than a trend. Google primarily indexes the mobile version of a site. Make sure your site is fully responsive and all content is available on mobile devices. Avoid hiding content on mobile with display: none, as it can hurt indexing.

Multi-modal indexing means Google gives growing weight to images and video during indexing. Optimise alt text for images, use modern formats (WebP, AVIF) and add transcripts for video. VideoObject structured data for videos can noticeably improve visibility in search results.

#How to prepare your site for indexing changes

To be ready for future changes in indexing, put these practices in place now: implement JSON-LD schema for every content type on the site, not only products and articles but also organisations, people, BreadcrumbList and other relevant types; optimise LCP and CLS by monitoring Core Web Vitals in Google Search Console and using tools such as PageSpeed Insights; use modern image formats such as WebP and AVIF, which compress better without quality loss; build natural internal links with appropriate anchor text between topically related pages; follow algorithm changes through Google’s official blogs and SEO industry publications.

#How to check whether a page is indexed in Google and Bing

#Indexing reports in Google Search Console

Google Search Console is a free Google tool that is absolutely essential for managing a site’s indexing. Its “Sitemaps” report shows the status of every submitted sitemap and the number of indexed URLs. The “Pages” report shows which pages are indexed and which were excluded for reasons such as noindex, duplicate content or robots.txt issues. The “URL Inspection” tool lets you check the indexing status of a single URL and request reindexing. The “Core Web Vitals” report shows how site performance affects indexing and ranking.

#Indexing reports in Bing Webmaster Tools

Bing Webmaster Tools is the Bing equivalent of Google Search Console. It offers a “Sitemaps” report with sitemap status, a “URL Index” report with indexing details, IndexNow API integration and tools for diagnosing indexing problems.

#How to submit sitemap URLs with a bash script

For advanced users who want to automate indexing tasks, command-line tools are available:

#!/bin/bash
# notify-google.sh - powiadom Google o nowej wersji strony

SITEMAP_URL="https://twoja-strona.pl/sitemap_index.xml"
GSC_API="https://www.googleapis.com/searchconsole/v1/urlsubmit/v3"

# Pobierz nowe URL że sitemap
NEW_URLS=$(curl -s $SITEMAP_URL | grep -oP '(?<=<loc>)[^<]+' | head -20)

for url in $NEW_URLS; do
    echo "Powiadamianie o: $url"

    # Wyślij URL do Google Indexing API
    curl -X POST -H 'Content-Type: application/json' \
        -d '{"url": "'"$url"'"}' \
        "$GSC_API?key=YOUR_API_KEY"

    # Poczekaj chwilę między żądaniami
    sleep 1
done

#What speeds up indexing in Google instead of pinging

#Myths about pinging in WordPress

MYTH #1: “You need to ping 100 services”. FACT: Pingomatic alone is enough, or switch it off entirely. Traditional ping lists are outdated and ineffective.

MYTH #2: “Pinging = faster indexing in Google”. FACT: Google uses sitemaps and its crawler, not RPC pings. Pinging may help with smaller search engines, but not with Google.

MYTH #3: “The more pings, the better”. FACT: Inactive ping services slow down publishing and waste server resources.

MYTH #4: “You have to submit every page manually”. FACT: Automatic sitemaps and APIs are far more effective than manual submissions.

#Which indexing methods work best

First place, with the highest priority, goes to the XML sitemap: the foundation that must be set up correctly on every WordPress site. Second is Google Search Console, required to monitor and manage indexing in Google. Third is the Google Indexing API, essential for shops, job listings and sites with dynamic content. Fourth is IndexNow, recommended for better visibility in Bing. Fifth is internal linking, the best way to guide crawlers naturally through the site. Sixth is content quality: unique content attracts crawlers and links.

#Recommended indexing setup for WordPress

// Optymalna konfiguracja indeksacji - co zrobić w 2026

// 1. Używaj wtyczki SEO (Yoast lub Rank Math) z automatyczną sitemap
// 2. Zgłoś sitemap w Google Search Console
// 3. Rozważ Indexing API dla dynamicznych treści
// 4. Skonfiguruj IndexNow dla Bing (opcjonalnie)
// 5. Zostaw ping_sites puste lub tylko z Pingomatic
// 6. Skup się na jakości treści i linkowaniu wewnętrznym

// Kod w Ustawienia > Pisanie > Usługi aktualizacji:
// Zostaw tylko: http://rpc.pingomatic.com/
// Lub całkowicie wyczyść to pole

// Konfiguracja Rank Math Instant Indexing:
// W Rank Math > Instant Indexing > Google API
// Dodaj credentials z Google Cloud Console

#How to speed up indexing of a new page

#What to check before publishing a new page

• Check that the page has unique content (at least 300 words for articles)
• Make sure there is no noindex tag in the SEO settings
• Check that the page is accessible to Googlebot (robots.txt)
• Add at least one internal link to the new page from another page
• Make sure the URL is SEO friendly and contains the keyword

#What to do after publishing a page

• Wait 24-48 hours for automatic indexing through the sitemap
• If it is urgent, submit the URL through Google Search Console (the “URL Inspection” tool)
• For shops and job listings, use the Indexing API
• Monitor the status in Google Search Console under “Pages”
• Check whether the page shows up in site:your-domain.com results

#Why a page is not indexed and how to fix it

#Conclusions

Pinging in WordPress is a relic of the past, and in 2026 it matters very little for indexing. Instead of worrying about ping service lists and maintaining outdated “Update Services” lists, focus on modern indexing methods that actually deliver results.

A properly configured XML sitemap is the foundation, and it has to be set up correctly and submitted to Google Search Console. The Google Indexing API is essential for shops and sites with dynamic content. IndexNow offers a simple alternative for faster indexing in Bing. Content quality and internal linking are the factors that most affect how well indexing works.

You can leave Update Services in WordPress empty or keep only http://rpc.pingomatic.com/. Do not add any other services: they will not help and they can slow down publishing. Instead, invest your time in optimising sitemaps, configuring Google Search Console and creating valuable content that naturally attracts links and search engine crawlers.

Keywords: WordPress pinging, ping list, Update Services, XML Sitemap, Google Indexing API, IndexNow, pingomatic, Google indexing, Google Search Console, Yoast SEO sitemap, Rank Math Instant Indexing, ping services, RPC ping, site indexing, SEO indexing 2026, sitemap.xml, submit sitemap, how to get a site indexed, fast indexing, shop indexing, job listing indexing, Core Web Vitals, E-E-A-T.

See our SEO and visibility optimisation services if you want to put this area in order in your project.