How Blog AI helps Google find new posts

A new post can only bring visitors from Google once Google has found it, read it and added it to its index. That usually takes a few days to a few weeks. Blog AI watches each new post for you, tells you in plain words whether Google has it yet, and shows you the one thing you can do to speed it up.

What Blog AI does after a post goes live

• Checks whether Google has indexed it. If your site is connected to Google Search Console, Blog AI asks Search Console about each new post about 2 days after it goes live, then on days 5, 10, 15 and 21, and stops as soon as Google has it. It also starts again if a live post's address changes.
• Shows the answer on the post. Open the post in Blog AI and look for On Google? next to the editor. You'll see one of:
  • Google: Indexed: the post can appear in search results.
  • Discovered, not indexed: Google knows the address but hasn't read the page yet. Common for new posts, especially on newer or smaller sites.
  • Not indexed yet (checked 3 Oct 2026): Google hasn't added it yet, with the reason in plain words (for example, it hasn't found the address yet, or it read the page but hasn't added it).
  • Not indexed, with something to fix: the page tells Google not to index it (a "noindex" setting), robots.txt blocks it, or Google couldn't open the page.
• Flags posts that are stuck. If new posts still aren't on Google a week after going live, your Actions list shows "new posts aren't on Google after 7 days", linking to the oldest one.
• Links new posts from older ones. Links from your other posts are one of the main ways Google finds a new page. Blog AI suggests 2–3 of them after you publish (Link it in on the post page).

Checking is free and read-only: Blog AI only reads what Search Console reports. It never changes anything in your Search Console account.

What Google allows (and what it doesn't)

Google doesn't let any tool ask it to index ordinary blog posts automatically:

• Google's Indexing API is only for job listings and livestream videos. Using it for blog posts is against Google's rules, so Blog AI doesn't.
• The old way to "ping" Google with a sitemap was switched off in 2023.
• Only you, as the site owner, can press Request indexing in Search Console.

So Blog AI does the parts it can: it checks, explains, and takes you straight to the right place in Search Console.

Request indexing in Search Console

When a post isn't indexed yet, the On Google? card has a Request indexing in Search Console button.

1. Open the post in Blog AI and find On Google? next to the editor.
2. Click Request indexing in Search Console. Search Console opens in a new tab, signed in as your Google account. After Blog AI's first check it opens on this post's inspection; before that it opens URL inspection for your site, and you paste the post's address (use Copy the post's address on the card) into the search bar at the top.
3. Click Request indexing. Google tests the live page, which takes a minute or two, then adds it to its crawl queue.
4. Wait. Google decides when to crawl. Requesting the same page again doesn't make it faster, and Search Console limits how many requests you can make a day.

If the card says something blocks the page (such as "noindex"), fix that first, then request indexing.

Sitemaps

A sitemap is a file that lists your site's pages so search engines can find them. Most sites already have one: WordPress has a built-in sitemap at /wp-sitemap.xml, and SEO plugins such as Yoast SEO and Rank Math replace it with their own.

• Tell Search Console about it once. In Search Console, open Sitemaps, enter the sitemap address and click Submit. You don't need to submit it again for each post: Google re-reads sitemaps it knows about by itself.
• Make sure new posts appear in it. WordPress, Ghost and most other platforms add a published post to the sitemap automatically.

Blog AI has read-only access to Search Console, so it can't submit sitemaps for you.

Bing and other search engines

Bing, Yandex, Seznam, Naver and Yep share new pages through a system called IndexNow. AI assistants that search the web with Bing benefit too.

• WordPress: version 1.3.0 of the free Blog AI Connector plugin sends each new or updated post to IndexNow from your own site. It's on by default; turn it off under Settings → Reading in WordPress.
• Other platforms: some platforms and hosting services send to IndexNow themselves. Blog AI doesn't send your posts to IndexNow from its own servers, because IndexNow only accepts them from your site.

Google doesn't use IndexNow, so the steps above still matter for Google.

If a post isn't indexed after a few weeks

• Check it's linked. A post nothing links to is harder for Google to find and looks less important. Use Link it in on the post page.
• Make it worth indexing. Google doesn't index every page it reads. A post that adds little beyond what's already on your site or elsewhere may stay out. A refresh with more specific, useful detail helps.
• Look for duplicates. If you have two posts on the same subject, Google may index only one. See Merge posts.