跳至正文
技术 SEO 与抓取索引 · Google SEO

Blog Posts Not Indexed by Google? Check Publishing Settings and Follow-Up

// / / 光算科技

When a blog post is not indexed by Google, confirm its URL-level state first, then investigate publication settings, the sitemap, rendered content and the usefulness of the answer. Verified ownership, a successful sitemap submission and a passing live test do not individually prove that the post is indexed.

This guide follows a post from publication through follow-up. If Search Console already shows a specific problem, start with our three categories of submitted-URL indexing problems to choose the relevant investigation.

Choose a real post and check its production URL

Open the post from your blog listing and copy the final address into URL Inspection. Do not substitute an editor preview, sharing shortlink or old redirect. One site: search or an unsuccessful title search cannot establish the URL's complete indexing state.

Record the publication date, last substantive revision, reported last crawl and indexing status. Compare several posts using the same template. If both old and new posts share noindex or fetch failures, investigate shared settings first. If one URL behaves differently, check its content, canonical and individual configuration.

Check the Search Console property and verification method

Ownership verification gives you access to the relevant management tools. It is not an approval process for index inclusion: Google can discover websites without registration, and verification does not award rankings.

PropertyScope and inputVerification
DomainEnter the domain without a protocol or path; it covers that domain, subdomains and protocol variantsDNS verification, using the record type and name/value supplied by Search Console
URL-prefixEnter a complete prefix such as https://www.example.com/; only matching URLs are coveredHTML file, meta tag, DNS, Analytics or Tag Manager methods may be available under their respective conditions

If the blog uses another hostname or protocol, make sure the selected property includes it. DNS may be managed somewhere other than the registrar. Follow the active DNS provider's naming rules, copy the supplied values accurately and retain the verification record after success.

For file verification, use Google's supplied file at the specified address. For a meta tag, place it in the homepage head, not an “Additional CSS” field. Analytics verification requires the same Google account, appropriate edit access and the required existing tracking snippet. Typing a measurement ID into Search Console is not the procedure. Choose a method that fits your access rather than installing a new tracking stack merely to verify ownership.

Confirm that the post is public and identify indexing controls

Visit while signed out. The article should be published and accessible without a password, login or challenge, rather than a title-only preview. Inspect its HTTP response and HTML for errors or unintended indexing restrictions.

WordPress: check Reading settings, then the post and SEO plugin

In Settings → Reading, review Discourage search engines from indexing this site. Correct an accidental setting on a production site intended for Search; retain deliberate controls on development or private sites. Individual post, post-type and archive settings in an SEO plugin may also affect output.

Verify the final response, including the HTML robots meta directive and X-Robots-Tag header. If the public page still serves an old instruction after a dashboard change, investigate page, server and CDN caches. A correct dashboard setting alone does not establish what visitors or Google receive.

robots.txt and noindex serve different purposes

robots.txt primarily controls crawling; it is not a reliable way to keep a discovered URL out of results. noindex controls index inclusion, and Google needs access to read it. Do not copy old rules that block necessary CSS, JavaScript or the entire post directory, or clear all legitimate restrictions to fix one article.

Find the active sitemap and inspect the post's entry

Identify what generates the sitemap before changing it. A theme, plugin and old static file can otherwise maintain different versions. The sitemap itself may carry noindex: it is a machine-readable URL list and does not need to appear as a normal search result.

  • Yoast SEO: follow the current instructions: Yoast SEO → Settings → Site features → Technical SEO → XML sitemaps. Enable it and use the viewing link to find the actual output. Post types marked noindex are excluded from its sitemap.
  • Hugo: it provides built-in sitemap templates. A monolingual project generates sitemap.xml at the output root; multilingual projects also generate the corresponding index. Check build settings and deployed files before adding another generator.
  • Other platforms or custom blogs: find the actual sitemap through platform configuration, a robots declaration or the generated output. Generate entries from published canonical URLs, rather than assuming every HTML file on disk belongs in Search.

Google's sitemap requirements specify fully qualified URLs and UTF-8. Split a file if it exceeds either 50MB uncompressed or 50,000 URLs. Google ignores priority and changefreq; lastmod should reflect a genuine significant update, not a daily artificial date change.

Submit the actual sitemap in Search Console's Sitemaps report, inspect processing errors and verify that the article is listed. A successful sitemap result establishes processing of that file; use page-level reports to check index inclusion.

Check rendered content and the canonical page

Run a live URL inspection and view the tested HTML, screenshot and resource information. The main answer should be present rather than a loading placeholder. Images, tables and promised downloads should work. An HTTP 200 response and a complete article are different findings.

Compare the user-declared and Google-selected canonical URLs. Print, parameter and mobile variants may be alternates; when the correct canonical is indexed, every variant does not need separate inclusion. If an unrelated article or the homepage is declared instead, trace the template or plugin's canonical configuration.

Keep a useful route to the post from its category or topic page, and add a crawlable contextual link where an existing article needs that next answer. There is no universal three-to-five-link indexing quota.

Put structured data in its proper role

Article or BlogPosting markup can help Google understand an article's title, author, dates and images. Match the visible content and use real authorship and dates. Check what the CMS already emits before adding a second, contradictory entity through another plugin or a manual snippet.

Valid syntax, feature eligibility and actual display are separate. JSON-LD can appear in the head or body; it does not have to be within the first 200 body bytes for indexing. Validators do not establish every semantic fact, and invented review ratings do not become valid evidence because code parses.

As of this revision, Google stopped displaying FAQ rich results on May 7, 2026. HowTo rich results left desktop Search on September 13, 2023. Useful questions and tutorials can remain on the page, but these retired features are not shortcuts to blog indexing. See our structured-data implementation guide for further checks.

If it was crawled, review the answer rather than a quota

The Page Indexing report distinguishes “discovered — currently not indexed,” which has not been crawled, from “crawled — currently not indexed,” which may or may not be indexed later. The first is not proof of a completed content review; the second alone is not proof of a penalty.

After confirming technical readability, ask who the post helps, what task it resolves, whether important judgments have sources and conditions, and what it adds beyond existing pages. Google's helpful-content guidance does not provide a universal word count, originality percentage, dwell-time threshold or weekly publication quota for indexing.

Editorial example: a hypothetical equipment-quotation guide that merely says “send specifications” could explain which specifications are needed, their units and who can confirm missing values, with a clearly labelled sample form. That adds usable information. If you have not tested the product, cite verified manufacturer information rather than inventing a customer case. Our beginner's blog-writing workflow develops this kind of evidence-led outline.

If you suspect copied passages, use article-similarity and source checks to locate the original material and inspect quotation or licensing. A similarity percentage alone does not identify an indexing cause or prove that the answer is useful.

Keep a record of revisions and follow-up

Under Google's recrawl guidance, use URL Inspection for a few important new or substantially changed pages and a sitemap for many URLs. Repeated requests do not accelerate crawling of the same address. Ordinary blog posts are also outside the Indexing API's documented scope, which covers JobPosting pages or BroadcastEvent embedded in VideoObject.

RecordPurpose
URL, current status and last crawlIdentify which version Google knows about
Actual issue, revision and deployment timeVerify the relevant change and avoid unrelated edits
Public response, live test and later indexing resultSeparate deployment, current access and search processing
Query impressions, clicks and subsequent enquiriesEvaluate useful outcomes separately from index inclusion

Set follow-up according to the issue: server failures need prompt attention; content improvements need a later crawl and subsequent observation. Continue publishing around genuine needs and verifiable material, rather than a mechanical schedule intended to “train” a crawler. A working page, an updated index and valuable visits each require their own evidence.