301 chain301 chain
Permanent redirects stacked one after another.
Found by Redirect checker →
302302
A temporary redirect on a page that moved for good.
Found by Redirect checker →
Technical SEOUpdated

Meta tags: machine-readable page instructions and previews

In short

Meta tags are HTML elements in a page’s head that can describe the page, control crawler behavior or supply social-preview metadata, depending on the tag.

Meta tags have different jobs

Meta tags are machine-readable HTML elements in a page head. Some describe a page, some direct crawlers, and some provide social-preview data. They should be selected by function: a robots directive controls indexation eligibility, a meta description may be used as a search snippet, and social metadata supports link previews. None turns thin or unavailable content into a useful search result.

The title element is related but is not itself a meta tag. Search engines can generate title links from several visible and structured signals, so a title and heading should agree with the page rather than repeat a phrase mechanically. Meta descriptions are suggestions for snippets; Google can use other visible text when it better matches the query.

The diagram shows the main inputs, checks and decision path for Meta tags: machine-readable page instructions and previews.

Robots directives and snippets

ElementPrimary functionTest
meta robots noindexTell crawlers not to index an HTML pageIt is present in the crawled HTML and the page is crawlable
X-Robots-TagSend a robots directive in HTTP headersResponse header is returned for the intended URL
meta descriptionSuggest page-summary textIt accurately reflects visible content
Open Graph metadataSupply a social previewA debugger sees the final canonical page values

For a PDF or image, X-Robots-Tag is often the applicable directive because there is no HTML head. For an HTML page, meta robots and header directives should not contradict each other. A page blocked in robots.txt may not be crawled to see a noindex rule, so blocking and deindexing are separate decisions.

Inspect the response

  1. Fetch the canonical URL and inspect both HTML and response headers.
  2. Check title, description, canonical and robots values against the visible page purpose.
  3. Test alternate hosts, trailing slash variants and filtered URLs for contradicting directives.
  4. Use URL Inspection as later crawler evidence, not as the only implementation test.
  5. Recheck after caching or deployment changes, because templates can overwrite page-level values.

Example: a paginated category may have a useful title and description for its current products but should not inherit a noindex from a filter template. Compare the actual response, the canonical target and sitemap inclusion before changing a tag.

Conflicting signals

Common defects are a 200 page with an error message, a canonical to a redirected URL, a noindex page placed in a sitemap, and a generic description copied across hundreds of pages. The remedy is not more tags; it is one intentional state across HTTP response, visible content, canonical, robots directive, internal links and sitemap.

Treat robots directives as indexation controls and descriptions as preview hints. Verify them in the rendered response, not only in a CMS field.

FAQ

No. It is a suggestion. Google may choose different visible content when it better answers the query.
No. A crawler generally needs access to see a noindex directive. Crawling and indexing controls have different roles.
Inspect the live response HTML and headers for the canonical URL and representative variants, then compare the values with rendered content and sitemap policy.