Define the relationship before choosing a URL
A duplicate warning is a reason to inspect the relationship between pages. It is not an instruction to point every affected page at the homepage. Put the inspected address, the site's declared canonical and Google's selected canonical in separate columns. Record when you collected the result.
Open each candidate and compare its main content and intended audience. Ask the content owner whether the pages are alternate addresses for the same material, an old and new version, or genuinely distinct resources. Resolve that business question before changing a template.
Create a decision record
For each candidate, record its purpose, language, current availability, internal links and whether the team plans to maintain it. Add the proposed preferred URL and one sentence explaining the choice. A useful record should let a colleague challenge the decision without needing to reconstruct the whole website.
If two pages answer different customer questions, consider whether the actual content makes that distinction clear. Do not consolidate them simply because their introductions share a sentence. Conversely, changing a title alone does not create a meaningful difference between two copies of the same service description.
Align the signals you control
Google describes redirects and canonical annotations as stronger canonicalization signals than sitemap inclusion. It advises keeping the signals consistent and linking internally to the preferred address. Include a self-referencing canonical on the preferred page and use a complete URL for the annotation.
Have the technical owner check the final page head, the sitemap entry and the important source links against the decision record. The purpose of this check is consistency: the site should not nominate one address in the page and a different version elsewhere. Google still determines the canonical it uses.
Worked example: a campaign copy of a service page
Illustrative example: a team creates a second public address for a campaign, containing the same service text as its maintained service page. Both remain accessible because the campaign link is already in circulation. The owner chooses the maintained service page as the preferred version and asks the developer to review the appropriate canonical setup.
Before release, the reviewer opens the campaign URL, the preferred URL and the site's main services hub. They compare each with the written decision and ensure the enquiry journey still works. If the campaign page later becomes obsolete, that is a separate decision about its lifecycle, not a reason to silently change the implementation during this review.
Keep language and exclusion decisions separate
For language alternatives, Google's guidance is to specify a canonical in the same language where one exists. An Arabic service page should not be casually treated as a duplicate of its English counterpart just because both describe the same offer. Document which address is preferred within each language.
Do not use noindex as a shortcut for choosing between duplicates within your site; Google's guidance favors canonical annotations for that purpose. Keep privacy and access controls in their own review. A canonical decision answers which version represents similar content, not who may access a private resource.
Verify implementation, then observe Google separately
Keep a release checklist with the intended URL, actual annotation, sitemap entry and links checked. Save the before-and-after values. Mark the technical change complete only after those values match the approved decision.
Then revisit the inspection record and compare observation dates. Do not describe a changed setting as proof that Google has adopted it. If a later result selects a different page, return to the candidate comparison and investigate the evidence rather than repeatedly replacing annotations without a reason. Store this record alongside your website-audit task for the next reviewer.