How to Set a Canonical URL and How the Canonical Field Works

Overview

The Canonical URL tells search engines which version of a page is the “master” copy to index, preventing duplicate or near-duplicate content from being treated as separate pages. In SureRank, leaving this field blank does not mean “no canonical tag.” It means “auto-generate one,” pointing back to the page’s own URL. 

Where to Find It

Open the post, page, or term, then go to the SureRank panel → Advanced tab → Canonical URL field.

SureRank’s own field description reads: “The Canonical URL tells search engines which version of a page should be indexed to avoid duplicate content issues. Leave blank to let SureRank set it automatically.”

What “Blank” Actually Resolves To

A canonical tag is always output. Blank just changes what it points to.

What Happens When You Enter a Custom URL

Whatever URL you type is used exactly as-is. SureRank doesn’t require it to be on the same domain, which is useful if this content is a syndicated copy of an original published elsewhere. Because there’s no validation, double-check the URL for typos before saving, since a wrong value won’t be flagged automatically.

How to Change Canonical URL

1. Open the post, page, or term.
2. Go to the SureRank panel → Advanced tab.

3. In Canonical URL, either:
   • Leave it blank to let the page self-reference (recommended for almost all normal content), or
   • Enter a specific URL if this page duplicates another page and search engines should credit that other page instead.
4. Save or update.
5. Verify by viewing the page source (right-click → View Page Source, or Ctrl/Cmd+U) and searching for rel=”canonical” to confirm what was actually output.

Troubleshooting

Canonical tag in page source doesn’t match what’s expected:

Check whether a multilingual plugin like WPML is active on the site. These can rewrite the canonical URL after SureRank generates it.

Canonical looks wrong or old on an Elementor/Bricks/Divi-built page 

This isn’t page-builder-specific behavior in SureRank, and it can happen due to stale permalinks or cache issues. Try clearing the cache once; if it does not work, escalate to the support team.