Help Google discover posts and use Search Console data

For ordinary blog posts, support discovery with a sitemap and crawlable internal links. Use Search Console URL Inspection when you need to request a crawl of an individual URL you manage. A crawl request is not a guarantee of indexing or search visibility.

1. Check the published page

Open the canonical public URL. Confirm that it returns the intended article, has crawlable content, and is not blocked by authentication or an unintended noindex directive. Scheduled drafts and preview URLs are not substitutes for a published page.

2. Maintain the sitemap and internal links

Include canonical public articles in the site’s XML sitemap. Link a new article from its relevant parent guide or resource index so people and crawlers can find it. Submit or inspect the sitemap through Search Console. A sitemap is a discovery signal; it does not guarantee that every submitted page will be indexed.

3. Use URL Inspection for individual requests

In Search Console, inspect the public URL on a property you manage. Review the reported status and use Request indexing if available. Google documents owner or full-user access for this action. This is a manual Search Console workflow, not the Search Console URL Inspection API: that API provides inspection data and does not submit indexing requests. Repeated requests for the same URL do not make Google crawl it faster.

4. Optionally use query data in Blogoose planning

Blogoose can read Search Console query data for connected-site planning. This does not need the Indexing API crawl option turned on.

1. Use a Google Cloud project and enable the Google Search Console API.
2. Create a service account and a JSON key if that is your organization’s approved authentication method. Keep the key private and out of source control.
3. Give the service-account email appropriate Search Console access to the website property.
4. In the saved Connected Site, provide the service account JSON and enable Use Search Console queries when planning topics. Keep the ordinary-post Indexing API option off.
5. Use Sync now and check the property and query count reported by the app.

The current implementation requests up to 5,000 query rows from the last 90 days and refreshes on its sync schedule. This is a product implementation limit, not the total number of searches your site received. Search Console may omit queries for privacy and its data is not instantaneous. Topics without matching evidence should remain Unknown demand.

5. Understand the Indexing API restriction

A standard article does not become eligible by adding unrelated JobPosting or livestream markup. If you operate a genuine eligible page, follow Google’s official prerequisites and verify its visible content and structured data. An accepted API notification confirms receipt of the request; it does not confirm that the page was crawled, indexed, or ranked.

Troubleshoot missing pages

• Check the correct URL-prefix or domain property and inspect the canonical URL.
• Check the HTTP response, robots rules, indexing directives, and canonical selection.
• Check that the sitemap contains the published URL and that relevant pages link to it.
• If synchronization fails, check Search Console access and whether the Search Console API is enabled. Do not enable the Indexing API as a workaround for query sync.
• If no query rows are returned, distinguish an empty or filtered dataset from an authorization failure. Do not invent demand numbers.

Official references: requesting a recrawl, Indexing API restrictions, and Search Analytics query documentation. Continue with the sitemap guide or reviewed publishing workflow.