Blogger SEO checker: diagnose URLs and metadata

A Blogger SEO check should sample a recent article, a label or archive page, and an old link. This distinguishes page-group robots policies from blog-wide configuration mistakes.

Read an article anonymously

Request the post on the domain being promoted and record its status and returned content. If it is inaccessible, investigate reading permissions before editing metadata or sitemaps. For an unexpected noindex, compare search visibility and the post's custom robots settings. A deliberately excluded archive is not proof that every article is blocked.

Follow a previously shared permalink

Choose an old address from another post or an external reference. Record its destination and confirm that it answers the same need. Redirect a deleted article only when a genuine replacement exists. Otherwise, a suitable not-found response is more accurate than sending everyone to an unrelated general page. Review internal references and images after address changes so the corrected route does not leave broken elements within the article.

Compare the template on two different posts

Read titles, H1 text, and descriptions to detect a theme repeating homepage information. Inspect alt text for informative images; it should describe the image rather than duplicate the entire article title. Compare post and archive robots directives and document deliberate exceptions. After changing a theme or crawler settings, request the samples again. Use updated Search Console evidence to establish whether Google has seen the release rather than assuming a successful public request proves immediate indexing.

A worked publishing scenario

Illustrative scenario: a new post carries noindex although the homepage remains indexable. Compare its custom robots tags with the Post and page tags setting; archive rules can be intentionally different. After correction, load the article anonymously and inspect an older post as a second sample. Do not infer article-level permissions from homepage behavior alone. Retain the exact article URL, response directive, and publication time so later Search Console observations can be compared with the configuration actually served.

Run a check and interpret the evidence

Submit one representative public URL to the free SEO checker below. Record its status, title, description, and canonical alongside the exact address and time of the check. Group repeated issues by their responsible template or configuration so a single targeted fix can be retested on multiple pages. A missing field and an intentional exclusion need different decisions.

An HTTP/HTML audit observes public responses. It does not sign into the platform, inspect every administrative setting, reproduce every client-side rendering behavior, or prove that Google has indexed a page. For search-engine evidence, compare Search Console URL Inspection and subsequent crawl data. Recheck the original URL after publication and cache refresh instead of interpreting a changed score alone as proof that the underlying issue is resolved.

Tools and related guidance

• Read the Blogger configuration guide
• Check a public URL
• Inspect a redirect chain

Official references

• Blogger: help people find your blog