How to Check Noindex and Canonical Tags Before Publishing

Skip to content

Search publishing · worked example

How to Check Noindex and Canonical Tags Before Publishing

Read the rules together, decide which URL you want, then verify the saved page.

A useful pre-publication check starts with two questions: should this page be available in search, and which URL represents its content? A robots meta tag addresses the first decision. A canonical annotation suggests a representative URL. Reading one tag while overlooking another can leave the saved page expressing a different intention from the editor’s plan.

This guide uses an invented four-tag fragment that you can reproduce in the ProSEO Robots Meta & Canonical Checker. It produces a specific review list. It does not establish whether a live page is indexed.

Start with the intended page

Our sample page is https://example.com/guides/publishing/?ref=email. For this exercise, the editor wants the main publishing guide to appear in search and wants the untracked URL, https://example.com/guides/publishing/, to represent the content. The query parameter is included in the original page URL so the comparison can show the difference accurately.

Use your actual address when reviewing your own page. Copy the contents between its head tags, without the head, html or body wrappers. Keep the original fragment as a recovery copy. A shortened sample can omit another relevant tag, and this local tool cannot verify where the copied tags appeared in the full document.

Run the four-tag example

Open the checker, choose Load conflicting example, then Check head tags. The supplied markup is:

<meta name="robots" content="index, follow, max-snippet:160">
<meta name="googlebot" content="noindex, nofollow">
<link rel="canonical" href="/guides/publishing/">
<link rel="canonical" href="https://example.com/guides/old-publishing/">

The worked result contains two robots meta tags, two canonical link tags and two distinct resolved canonical URLs. Its Googlebot summary reports both noindex and nofollow. The CSV keeps all four reviewed tags, including the original relative canonical value. These counts let you compare your run with the example before adding a real page’s markup.

Supplied tagObserved resultReview decision
robots: index, followContributes positive tokens; snippet limit remains visibleRead the second meta tag before deciding
googlebot: noindex, nofollowRestrictive tokens remain in the Googlebot summaryCompare with the page’s intended search availability
Relative canonicalResolves to the untracked publishing guideConfirm that this is the intended representative URL
Old publishing canonicalA second, different destinationFind the source of the extra annotation

Read the restrictions together

For Googlebot, a generic robots instruction and a Googlebot-specific instruction can both apply. A positive index token does not cancel a noindex restriction. In this sample, index and follow in the first tag therefore do not override the restrictive tokens in the second. The shorthand none also means noindex and nofollow.

The checker computes only that index/follow summary. It retains max-snippet:160 as supplied text without validating snippet behavior. Other crawler tags can appear in the inventory, but they do not contribute to this Googlebot summary. An empty summary is an observation about the supplied sample, rather than evidence that a page is indexable.

Compare the two canonical targets

The first canonical resolves to https://example.com/guides/publishing/. The second resolves to https://example.com/guides/old-publishing/. Both differ from the original address, whose query string remains part of the comparison. This is why the tool shows two different URLs on the same origin rather than declaring the first one self-canonical.

A different canonical target can be intentional. Here, the editor has already chosen the untracked URL, so the old guide is the unexpected destination. Check whether a theme, SEO setting or custom snippet supplied it. Avoid deleting a tag without identifying the component that will recreate it on the next save.

Use an explicit absolute canonical URL for the intended destination. Review any base href in the supplied markup because it changes how relative references resolve. Fragment targets and canonical links carrying alternate-version qualifiers also deserve inspection. A resolved address is not evidence that the destination exists or contains equivalent content.

Choose the intended outcome before editing

For our publishable guide, the proposed replacement fragment is:

<meta name="robots" content="index, follow, max-snippet:160">
<link rel="canonical" href="https://example.com/guides/publishing/">

This removes the sample’s Googlebot restriction and leaves one preferred URL. The checker should now report no noindex or nofollow token in the supplied tags, one canonical and one resolved destination. It will still show a different URL on the same origin because the original page address retains its tracking query. That relationship is expected for this exercise.

A private preview requires a different decision. If the page should stay out of search, retaining noindex may be appropriate. A canonical tag does not turn that preview into a publishable page, and noindex is not a substitute for choosing a representative URL for duplicate content. Keep a written sentence describing the desired outcome so later edits do not reverse it accidentally.

The checker’s separate self-canonical example uses a canonical containing the original query string. It demonstrates URL equality, not a recommendation to keep campaign parameters in every canonical. Use it to understand the comparison before choosing your site’s preferred address.

Verify the published result separately

Download the tag review CSV before changing the site. The checker exports all reviewed rows within its limit, while the on-page table previews the first 100. Formula-like cell text receives an apostrophe prefix, so keep the original markup alongside the working export.

After applying an intentional edit, inspect the saved page’s head again. Check the HTTP response for X-Robots-Tag and canonical Link headers, look for redirects, and confirm that the intended page is accessible to the relevant crawler. Use Search Console inspection when available to investigate Google’s observed state. None of those live checks is supplied by a pasted-fragment analysis.

When the preferred URL is settled, review important internal links with the HTML Link Analyzer and use the internal link review guide to record the changes. If you need replacement head markup, the Meta Tag Generator can prepare escaped tags from your chosen values.

Documentation checked 14 October 2026: Google Search Central’s robots meta tag reference and canonical URL guidance. The examples and editing decisions above were created for this guide.