মূল বিষয়বস্তুতে যান

Blog Meta Tags: Which Ones to Use and How to Check Them

LinkinTech SEO Editorial Team· Editorial Team· 17 min read
Blog Meta Tags: Which Ones to Use and How to Check Them

Quick Answer

Blog meta tags are HTML declarations that describe an individual blog post to search engines, browsers, and social platforms. Start with an accurate page title, a useful meta description, appropriate robots directives, and Open Graph properties for social sharing. Also check your canonical URL and structured data, although neither is technically a meta tag. Google can rewrite search titles and descriptions, so correct implementation matters more than trying to force a particular search-result appearance.

Key Takeaways

  • The HTML title identifies a page and helps Google generate its search-result title; technically, it is not a meta tag.
  • A meta description summarizes a post and may appear in its Google search snippet, but Google can choose different text.
  • Robots directives control certain indexing and search-presentation behaviors. An accidental noindex can prevent a post from appearing in Google Search.
  • Open Graph metadata supplies information for social-sharing previews.
  • Canonical links and BlogPosting structured data serve different purposes and are not meta tags.
  • Google ignores the historical meta keywords tag for indexing and ranking.
  • Inspect the rendered HTML after publishing instead of assuming your CMS settings produced the expected result.

What Blog Meta Tags Actually Do

When someone publishes a blog post, the visible article is only part of the webpage. The browser also receives information in the document's HTML <head> section.

This information helps describe the page, establish technical settings, provide instructions to crawlers, and prepare content for social sharing.

For example, a blog post about email marketing might contain:

  • A title identifying the article.
  • A description summarizing its main subject.
  • Robots instructions indicating whether search engines may index it.
  • Open Graph properties defining its social-sharing title and image.
  • A canonical URL identifying the preferred version of the page.

These elements do not all perform the same job. Some are actual HTML meta elements, while others are separate HTML elements or structured data.

Google documents the supported elements and their behavior in its guide to meta tags and attributes that Google supports.

The important distinction is that adding more tags does not automatically make a webpage more search-friendly. Each declaration should serve a specific purpose and accurately describe the published page.

The Essential Metadata for a Blog Post

1. HTML Title: Identify the Page Clearly

The HTML title is one of the most important pieces of information in a blog post's head section. It is written using the <title> element, not a <meta> element.

Example:

<title>Email Marketing Strategies for Small Businesses</title>

This title identifies the page and provides information Google can use when generating its search-result title link.

However, the title you provide is not necessarily the exact wording Google will display. Google can also consider the visible page title, headings, prominent text, links pointing to the page, Open Graph information, and other signals.

Its official documentation explains how Google generates and influences title links in Search.

Keep the HTML title accurate, distinctive, and consistent with the article's actual subject. Avoid using a title that promises information the post does not contain.

The process of selecting and naturally using relevant terms in an SEO title is a separate topic. See our guide to choosing keywords for your SEO title for that specific task.

2. Meta Description: Summarize the Article

The meta description provides a short summary of a webpage. Search engines may use it when creating a search-result snippet.

Example:

<meta name="description" content="Discover practical email marketing strategies, campaign planning tips, and ways to improve your business communication.">

A useful description should tell readers what they will find after opening the article. It should accurately represent the page rather than simply repeat its title.

For example, consider a blog post explaining how to maintain a WordPress website. A relevant description might mention updates, backups, security checks, and performance maintenance if those subjects are genuinely covered.

Does Google always display the description you write?

No. Google may use your meta description when it considers that description a suitable summary. It can instead select relevant text from the visible page when that better matches the search.

There is also no fixed maximum description length imposed by Google. Search-result snippets can be shortened according to the available display space and other factors.

A concise description is still a useful editorial practice, but treating 150–160 characters as a compulsory Google requirement is incorrect.

For practical guidance, see Google's documentation on writing effective meta descriptions.

3. Robots Meta Tag: Control Search Instructions

The robots meta tag provides instructions about how search engines should handle a particular page.

Example:

<meta name="robots" content="index, follow">

Two commonly discussed directives are:

  • index: permits the page to be considered for indexing.
  • follow: indicates that links on the page may be followed.

Google generally treats indexing and link-following as defaults, so explicitly adding index, follow is not necessary for an ordinary public blog post.

More important directives include:

Directive Purpose
noindex Instructs Google not to show the page in search results.
nofollow Provides instructions concerning links on the page.
nosnippet Restricts the display of a text snippet.
max-snippet Specifies a maximum text-snippet length.
max-image-preview Controls the permitted image-preview size.
max-video-preview Controls the permitted video-preview duration.

The most important warning for blog publishers is accidental noindex.

For example:

<meta name="robots" content="noindex">

If this declaration is present on a normal public article, it tells Google not to show that page in search results.

This can happen when a website is being developed in a staging environment and a restrictive setting remains after publication. It can also happen when a CMS visibility option or SEO plugin is configured incorrectly.

Before changing robots settings, identify why the directive exists. A private account page and a public educational article have different requirements.

Google explains the available directives, crawler behavior, and the HTTP alternative in its robots meta tag specifications.

One additional detail matters: crawlers must be able to access the page to read its robots meta directives. Blocking a page in robots.txt can prevent a crawler from seeing a page-level noindex declaration.

4. Googlebot Meta Tag: Give Google-Specific Instructions

The Googlebot meta tag provides instructions specifically for Google's crawler.

Example:

<meta name="googlebot" content="noindex">

It can be useful when a publisher needs crawler-specific behavior rather than instructions intended for all compliant crawlers.

However, most ordinary blog posts do not need a separate Googlebot declaration. A general robots directive is usually sufficient when the same instructions should apply to multiple crawlers.

Avoid adding conflicting robots and Googlebot instructions. Check the combined directives before publishing, especially when an SEO plugin generates them automatically.

5. Open Graph Tags: Improve Social-Sharing Previews

Open Graph metadata describes a webpage when someone shares its URL through a supporting social platform.

For example, a shared blog link may display a headline, short description, and image. Open Graph properties help publishers supply the information used for that preview.

The four basic properties are:

Property Purpose
og:title Defines the social-sharing title.
og:type Identifies the type of shared object.
og:image Specifies the image associated with the shared content.
og:url Specifies the object's canonical URL for sharing purposes.

Two additional useful properties are og:description and og:site_name.

Example:

<meta property="og:title" content="Email Marketing Strategies for Small Businesses">
<meta property="og:description" content="Practical advice for planning and improving email campaigns.">
<meta property="og:image" content="https://example.com/images/email-marketing.jpg">
<meta property="og:url" content="https://example.com/email-marketing-guide/">
<meta property="og:type" content="article">
<meta property="og:site_name" content="Example Blog">

Replace the example values with the actual post information and a publicly accessible image URL.

A useful social-sharing image should accurately represent the article and remain accessible to the platforms retrieving it. An image stored behind a login or on a blocked resource may not be available to a sharing crawler.

Open Graph is a social-sharing protocol, not a replacement for search metadata. Its purpose and properties are documented by the official Open Graph Protocol.

6. Charset: Specify Character Encoding

The charset declaration tells the browser which character encoding the document uses. For most modern websites, UTF-8 is the appropriate choice.

Example:

<meta charset="UTF-8">

This helps browsers interpret letters, punctuation, symbols, and characters from different languages correctly.

For example, a multilingual blog containing English, Bengali, or other scripts needs consistent character encoding to avoid unexpected display problems.

The charset declaration is a technical document setting. It is not a direct ranking shortcut.

7. Viewport: Support Mobile Display

The viewport declaration helps browsers determine how a webpage should be displayed on different screen sizes.

A common implementation is:

<meta name="viewport" content="width=device-width, initial-scale=1">

This tells the browser to use the device's viewport width and an initial scale of 1.

Without appropriate viewport configuration, a page may behave unexpectedly on mobile devices, particularly when its layout was designed for desktop screens.

Viewport metadata is important for responsive presentation, but simply adding it does not make an otherwise poorly designed page mobile-friendly. The layout, images, typography, and interactive elements must also work at different screen widths.

Meta Tags vs. Canonical Links vs. Structured Data

One of the most common implementation mistakes is treating every declaration inside the HTML head section as a meta tag. These technologies are related, but they have different formats and responsibilities.

Blog Post Metadata Decision Matrix

Item HTML implementation Primary purpose Important distinction
HTML title <title> Identifies the page and informs search title generation Not a meta tag
Meta description <meta name="description"> Provides a search-snippet summary Google may rewrite it
Robots <meta name="robots"> Provides indexing and presentation instructions Incorrect noindex can affect search visibility
Googlebot <meta name="googlebot"> Provides Google-specific instructions Crawler-specific behavior
Open Graph title <meta property="og:title"> Defines the social preview title Not a guaranteed Google title
Open Graph image <meta property="og:image"> Defines the social preview image Image must be accessible
Charset <meta charset="UTF-8"> Defines character encoding Technical document metadata
Viewport <meta name="viewport"> Helps configure mobile viewport behavior Not a ranking shortcut
Canonical <link rel="canonical"> Declares a preferred URL Not a meta tag
BlogPosting JSON-LD structured data Describes article information Not a meta tag
Meta keywords <meta name="keywords"> Historical keyword list Google ignores it for indexing and ranking

Canonical Link: Identify the Preferred URL

A canonical declaration is an HTML link element, not a meta tag.

Example:

<link rel="canonical" href="https://example.com/email-marketing-guide/">

It indicates the preferred URL when multiple URLs contain duplicate or substantially similar content.

For example, a blog post might be accessible through tracking parameters or different URL variations. A consistent canonical declaration can help communicate which URL should be treated as the preferred version.

Canonicalization is not a command that guarantees Google will select the declared URL. Google considers multiple signals when choosing a canonical URL.

See Google's documentation on consolidating duplicate URLs for implementation guidance.

BlogPosting Structured Data: Describe the Article

Structured data provides information about a webpage in a format that supported systems can interpret.

For blog posts, publishers commonly use the BlogPosting type from Schema.org vocabulary in JSON-LD format.

It can describe information such as:

  • Article headline.
  • Publication date.
  • Last modification date.
  • Author.
  • Main image.
  • Publisher.

A simplified example looks like this:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Email Marketing Strategies for Small Businesses",
  "datePublished": "2026-11-18",
  "dateModified": "2026-11-18",
  "image": "https://example.com/images/email-marketing.jpg"
}
</script>

These are example values. Replace them with accurate information about the actual article.

Structured data is not a meta tag. It is a separate markup mechanism that describes the content and its properties.

Google supports Article, NewsArticle, and BlogPosting structured data types. Its Article structured data documentation explains supported properties and implementation considerations.

Meta Keywords: Is This Tag Still Useful?

The historical meta keywords tag allowed website publishers to list keywords associated with a page.

It looks like this:

<meta name="keywords" content="email marketing, email campaigns, marketing strategy">

Some older SEO tutorials still recommend adding it to every article.

For Google Search, however, this is outdated advice. Google ignores the meta keywords tag for indexing and ranking.

Spending time maintaining this field is therefore unnecessary if your goal is improving Google Search visibility. Focus instead on accurate page information, useful content, technical accessibility, and appropriate metadata.

A Practical Blog Post HTML Head Example

The following example combines the main elements discussed above. It is a reusable starting point, not a requirement to copy every declaration into every page.

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1">

    <title>Email Marketing Strategies for Small Businesses</title>

    <meta name="description"
          content="Learn practical email marketing strategies, campaign planning, and ways to improve business communication.">

    <!-- Use appropriate robots instructions for this page. -->
    <!-- Ordinary indexable pages generally need no explicit index, follow tag. -->

    <link rel="canonical"
          href="https://example.com/email-marketing-guide/">

    <meta property="og:type" content="article">
    <meta property="og:title"
          content="Email Marketing Strategies for Small Businesses">
    <meta property="og:description"
          content="Practical advice for planning and improving email campaigns.">
    <meta property="og:image"
          content="https://example.com/images/email-marketing.jpg">
    <meta property="og:url"
          content="https://example.com/email-marketing-guide/">
    <meta property="og:site_name" content="Example Blog">
</head>
<body>
    <h1>Email Marketing Strategies for Small Businesses</h1>

    <p>Your actual article content begins here.</p>
</body>
</html>

Before using this example, make several adjustments:

  1. Replace example.com with your actual website domain.
  2. Write a unique title and description for the individual article.
  3. Set the canonical URL to the intended preferred URL.
  4. Replace the social-sharing image with an accessible image representing the post.
  5. Confirm that the robots configuration does not unintentionally prevent indexing.
  6. Use accurate publication information if you add structured data.

Notice that the example does not force an explicit index, follow declaration. Ordinary pages generally use those default behaviors, so adding redundant instructions is not necessary.

Most importantly, never copy a noindex directive from a development or private-page configuration into an ordinary public blog post without understanding its consequences.

How to Add Blog Meta Tags in WordPress

WordPress publishers can generally configure post-level SEO information through their editor, platform settings, or an installed SEO plugin. The exact process depends on which WordPress environment you use.

WordPress.com

WordPress.com provides documented controls for configuring SEO titles and meta descriptions on individual posts and pages.

A general workflow is:

  1. Open the post you want to edit.
  2. Locate its SEO settings or search-engine preview interface.
  3. Enter an accurate SEO title.
  4. Add a relevant meta description.
  5. Review the available visibility and indexing settings.
  6. Save or update the post.
  7. Inspect the published page to confirm the expected HTML output.

Some features depend on the WordPress.com plan and the available platform controls.

The official WordPress.com guide to optimizing posts and pages explains its documented workflow.

Self-Hosted WordPress

Self-hosted WordPress installations can use different themes, plugins, and configurations.

Depending on the setup, an SEO plugin may provide fields for titles, descriptions, canonical URLs, robots directives, and Open Graph properties.

However, installing several plugins that perform the same metadata functions can introduce duplicate declarations or conflicting settings.

Before changing your configuration:

  • Check whether your theme already generates metadata.
  • Identify which plugin controls SEO titles and descriptions.
  • Avoid enabling overlapping metadata features unnecessarily.
  • Check whether the published HTML contains duplicate declarations.
  • Review the page after saving changes.

For publishers managing many posts, a consistent editorial workflow can help keep metadata accurate across the website.

A structured SEO article publishing workflow may also help teams coordinate article preparation and publishing, although metadata still needs to be checked on the rendered pages.

How to Check and Troubleshoot Blog Meta Tags

Entering information into a CMS is only the first step. You also need to verify that the published webpage contains the correct declarations.

Use the following process after publishing or updating an article.

Step 1: Inspect the Published HTML

Open the published blog post in your browser.

You can use the browser's View Page Source feature or Developer Tools to inspect the HTML.

Look inside the <head> section for the title, description, robots directives, Open Graph properties, and canonical link.

Do not rely exclusively on the CMS editing screen. A theme or plugin may change the final output.

Step 2: Check the Title and Description

Confirm that:

  • The HTML title accurately identifies the article.
  • The meta description summarizes the actual content.
  • Neither field contains accidental placeholder text.
  • The page does not have multiple conflicting descriptions.
  • The title and visible article heading are reasonably consistent.

If the title or description is missing, investigate the theme and SEO plugin configuration before adding another declaration manually.

Step 3: Review Robots Directives

Search the rendered HTML for:

<meta name="robots">
<meta name="googlebot">

Check whether any directive contains noindex, nofollow, or restrictive snippet settings.

If an ordinary public post unexpectedly contains noindex, investigate the CMS visibility setting, plugin configuration, and any deployment-related settings.

Also remember that robots directives may be delivered through an HTTP response header. The absence of a meta robots element does not prove that no robots instruction exists.

Step 4: Check Open Graph Properties

Verify that the social-sharing title, description, and image accurately represent the post.

Pay particular attention to the image URL. It should be publicly accessible and point to the intended image rather than a temporary or private file.

If a social platform displays an outdated preview, its cached information may differ from the current HTML. Check the platform's available sharing-preview tools and refresh options where supported.

Step 5: Verify the Canonical URL

Find the canonical declaration:

<link rel="canonical" href="https://example.com/email-marketing-guide/">

Compare it with the URL you intend search engines to treat as the preferred page.

Look for problems such as:

  • A canonical URL pointing to another unrelated article.
  • A staging-domain URL appearing on the live website.
  • An inconsistent HTTP or HTTPS version.
  • A canonical declaration pointing to an outdated URL.

Investigate these problems before assuming that the page's metadata is correct.

Step 6: Validate Structured Data Separately

If your post includes BlogPosting or Article structured data, inspect it separately from ordinary meta elements.

Check that its headline, dates, image, and other supplied properties accurately describe the visible article.

Do not assume that valid structured data guarantees a rich result or improved rankings. Eligibility and actual search presentation depend on Google's requirements and other factors.

Step 7: Review the Actual Search Appearance

Finally, compare the metadata you supplied with the title and snippet Google actually displays, when the page has appeared in Search.

A difference does not automatically indicate a technical error. Google can generate a different title link or snippet based on the query and page content.

If the displayed information is misleading, improve the accuracy and consistency of the page title, headings, description, and visible content rather than repeatedly submitting the same metadata.

Common Blog Meta Tag Mistakes to Avoid

Even a technically functioning website can contain metadata problems that make pages confusing or difficult to manage.

Mistake Why it matters Better approach
Reusing one description across every post Descriptions may not accurately summarize individual articles Write a relevant description for each important post
Accidentally adding noindex Can prevent a public post from appearing in Google Search Check robots settings before publishing
Treating the title as a meta tag Confuses different HTML elements Use the <title> element correctly
Adding obsolete meta keywords Google ignores this field for indexing and ranking Spend time on useful content and supported metadata
Using an incorrect canonical URL Can send misleading preferred-URL signals Check the canonical against the intended page URL
Repeating Open Graph declarations Can create conflicting social-preview information Identify and correct duplicate output
Using inaccessible social images Sharing platforms may not retrieve the intended image Use a publicly accessible image URL
Treating structured data as a meta tag Confuses separate markup technologies Validate JSON-LD independently
Assuming Google must use your description Google can generate a different snippet Make both the description and visible page content useful

A good metadata workflow is not about maximizing the number of declarations. It is about providing accurate information and avoiding instructions that contradict the page's purpose.

Frequently Asked Questions

What Are Blog Meta Tags?

Blog meta tags are HTML elements in a webpage's head section that provide information about the page to browsers, search engines, and other systems. Common examples include meta descriptions, robots directives, and Open Graph properties.

Which Meta Tags Are Most Important for a Blog Post?

Start with a useful meta description, appropriate robots configuration, and relevant Open Graph information when social sharing matters. Also provide a meaningful HTML title, although the title element is not technically a meta tag. Check the canonical URL separately.

Do Blog Meta Tags Improve Google Rankings?

Metadata helps describe and manage a webpage, but adding meta tags does not guarantee better rankings. Google ignores the historical meta keywords tag for indexing and ranking. Focus on accurate metadata, useful content, and sound technical implementation.

Does Google Always Use My Meta Description?

No. Google may use your description when generating a search snippet, but it can select relevant text from the page instead. The displayed snippet can also vary according to the search query.

Is the Meta Keywords Tag Still Useful?

Not for Google Search rankings or indexing. Google ignores the meta keywords tag, so publishers generally do not need to add or maintain it for Google SEO.

Is a Canonical Tag a Meta Tag?

No. A canonical declaration uses the HTML <link> element with rel="canonical". It communicates a preferred URL and is separate from meta elements.

Are Open Graph Tags Important for Google SEO?

Open Graph properties primarily describe content for social-sharing previews. They should not be confused with Google's indexing directives or treated as guaranteed direct Google ranking factors.

How Do I Check Whether My Blog Meta Tags Are Working?

Inspect the published HTML source or browser Developer Tools. Check the title, description, robots directives, Open Graph properties, and canonical URL. If you use structured data, validate it separately. Finally, review actual search and social previews without assuming they must reproduce every supplied value.

Final Thoughts

Effective blog meta tags are about clarity, accuracy, and correct implementation—not adding as many HTML declarations as possible.

A well-prepared blog post should have a meaningful title, an accurate description, appropriate indexing instructions, and social metadata where useful. Its canonical URL should point to the intended preferred page, while structured data should describe the article accurately when implemented.

The most valuable habit is to check the published HTML after every important metadata change. This helps catch duplicate declarations, incorrect URLs, inaccessible images, and accidental noindex settings before they become persistent problems.

When you understand which elements are actual meta tags and which are separate technologies, managing blog metadata becomes much easier. You can give search engines and social platforms accurate information without relying on outdated SEO practices or expecting metadata alone to deliver rankings or indexing.