Library·SOP·SEO
Tell Google which version of duplicate or very similar WordPress pages you’d prefer to appear in search results.
Last reviewed: · Editorial review
Clarity, structure and references reviewed in this version. This is not a test in a live account.
Tell Google which version of duplicate or very similar WordPress pages you’d prefer to appear in search results.
This SOP covers:
This does not cover:
A canonical URL is a search-engine hint that names the preferred address for duplicate or very similar pages. It does not send a visitor from one address to another. WordPress SEO plugins normally use a page’s own address by default, so leave that behavior in place unless a clear same-site preferred page exists.
Compare the main text and sections of the selected page with the same-site page you think should be preferred. Decide whether they are exact copies, near-duplicates serving the same need, or different content; then choose the control that matches what you want visitors to experience.
If this page has its own useful content, or is already the page you want people to reach from search, keep the plugin’s default that points the page to itself. For example, keep a current tutorial and a different tutorial at their own URLs when each teaches different steps.
Keep the default. If this page is unique or already the page your site wants visitors to reach, leave its automatic self-canonical in place.
Use a canonical. Choose this when two same-site URLs have the same or very similar main content and both should stay available. For exact copies, use the URL your site has chosen as the primary address. For near-duplicates, choose the more complete or accurate page that serves the same reader need. A shared topic alone is not enough. For example, if /guides/email-marketing/ and /email-marketing-tips/ contain nearly the same advice and sections, the site may prefer the maintained guide. A separate guide about email subject lines is different content.
Use a permanent redirect. If visitors should stop using the old URL, ask the site owner for a permanent redirect. A canonical does not send visitors anywhere; a redirect does, and Google treats redirects as a stronger signal.
Use noindex for separate content. If this is different content that should stay out of search results, leave this method and use the noindex procedure. A canonical does not remove separate content from search.
This procedure changes one page only. If a Search Console report shows a group of affected URLs, use the linked report guide to decide which pages matter before changing any settings.
If you chose a custom canonical, compare the pages’ main text and sections. For exact copies, choose the URL your site intends as the primary address. For near-duplicates, choose the more complete or accurate page that serves the same reader need. A shared topic alone is not enough.
Open the proposed preferred URL in a new tab. Confirm that the expected page loads and that the address bar stays at its final public URL. Use that exact HTTPS address, including the site’s www or non-www choice and trailing slash.
If you cannot confirm that search engines can crawl both the duplicate page and the preferred page, inspect each URL in Search Console using the linked page-checking guide before continuing. A page Google has not indexed yet can still be eligible; the important point is that neither page is marked noindex or blocked.
A page-level field overrides the plugin’s automatic choice for this page only. Keep the page’s public address separate from the preferred page’s address.
In the WordPress block editor, open the Rank Math SEO panel from its icon at the top right, choose Advanced, and find Canonical URL. If Advanced is not available, ask the site administrator to expose Rank Math’s advanced controls.
Apply your choice in this page’s Canonical URL field. If this is already the preferred page, leave the custom value blank so the plugin points the page to itself. If you chose another page, use the child step to enter its exact public HTTPS URL. Leave out tracking-only query strings and #fragments. If a query string changes what visitors see, ask the site owner; filtered page variants are outside this guide.
If you are changing a nonblank custom value, make a private note in your usual notes app titled “Canonical setting backup.” Record the source page URL and the exact current Canonical URL field value. Keep the note until the live check passes. If the field is blank and you are keeping the default, no backup is needed.
For a custom preference, enter the full HTTPS address of the preferred page. To return to the automatic self-canonical, clear the saved custom value. Rank Math may show the current page address as a placeholder when no custom canonical is saved. Clear only a saved custom value; leave the placeholder empty so Rank Math uses its default.
Click WordPress’s Save button and wait for the page-updated confirmation. Do not change the page body or its permalink as part of this task.
The editor field shows what you entered. The public page source shows what visitors and search crawlers receive. Check the published output before calling this complete.
After saving, check the original page’s public source. If you set a custom canonical, check the preferred page’s source too.
When you set a custom canonical, open the preferred page’s own public source and confirm its canonical points to itself and the page is not marked noindex. Do not create a chain where the preferred page points to a third URL.
Use the preferred URL for any new link to this content. If you know a sitemap, menu, or existing internal link still promotes the duplicate, ask the site owner to align it; this one-page procedure does not change site-wide links or sitemap settings.
If the live page has no canonical tag, has a different URL, or shows multiple conflicting canonical tags, reopen the page field and restore the exact previous value or clear the custom value to return to the plugin default. Save and check the public output again; ask the site administrator to investigate if the mismatch remains.
