One service, several URLs: build a canonical map before fixing duplicates: working record
Use this six-field worksheet to resolve preferred service URLs and conflicting signals without misusing noindex or robots controls.
No signup. Enter reference codes, add records and download a CSV. Entries stay in the browser tab. Filled fields do not establish completion, approval or compliance.
| Observed URL | Content relationship | Preferred URL | Existing signals | Chosen correction | Public verification |
|---|---|---|---|---|---|
| Illustrative: /brake-service | Equivalent to current service page | /services/brakes | Conflicting internal route | Developer review required |
- The starting row is fictional, not merchant evidence. Replace it with your own verified record. Blank fields remain unresolved.
- Create one row per decision or observation described in the article. Use the worked example to understand the method, not as proof about your business.
- Record exact public URLs and collection dates where relevant. Unknown, failed and not checked are different from a verified pass.
- Keep customer information, account credentials and private documents outside this worksheet. Use role names or internal references.
- A completed row does not prove publication, authorization, indexing, rankings or revenue. Record the actual acceptance check separately.
- Export the record to approved business storage if needed. Browser edits are cleared on reload.
One service page can show up under an old address, a new slug, and a tracking URL. That doesn’t automatically mean the website is penalized. The real job is picking the page that represents the service and making the website’s signals match.
Use with this guide
website audit tool
Review the current scope and workflow for website audit tool.
business website tool
Review the current scope and workflow for business website tool.
Decide whether the pages are actually equivalent
Read the pages before you group them as duplicates. Similar titles don’t prove two URLs cover the same service or location. Sometimes the content is identical, and only a tracking parameter changes. Google’s canonicalization guidance explains how preferred URLs help consolidate signals and make tracking simpler. It also says Google may choose a canonical even when the site doesn’t specify one. The website audit tool should show the URLs it found and the evidence. But the business still decides whether those pages serve the same purpose. Don’t merge distinct services just to cut the scanner’s warning count.
Sources for this section: Google Search Central: specifying canonical URLs
Choose the customer’s preferred destination
Pick the page with accurate, current content and a useful, stable address. Replacing a retired page with an equivalent one? A permanent redirect may fit. Google treats redirects and canonical annotations as strong signals. Sitemap inclusion is weaker. Make sure those signals don’t point to conflicting destinations. The business website tool helps manage content, but control over redirects and metadata depends on how it’s built. Ask the developer responsible to explain the planned change. Don’t use robots.txt to handle canonicalization, or casually add noindex to a page you want eligible for search.
Sources for this section: Google Search Central: specifying canonical URLs
Use a small URL-map example
Picture a fictional shop with /brake-service, /services/brakes and /brake-service?campaign=fall. The first two pages contain equivalent current information. The third is a tracking variation. After checking existing links and implementation needs, the owner picks /services/brakes as the preferred public page. The job is to line up the relevant redirect, canonical and internal links, not treat all three URLs as separate services. Don’t assume every platform needs the same setup. Record the actual response and markup evidence for your site. And keep unrelated location pages out of the group when they contain genuinely different business information.
Sources for this section: Google Search Central: specifying canonical URLs
Check discovery after the correction
Check the navigation and contextual links. Do they use the chosen URL? Review sitemap inclusion and public canonical evidence through the authorized technical workflow. Google’s link guidance recommends linking consistently to useful destinations with descriptive text. If the old address should redirect, test it directly. A saved editor setting doesn’t prove the server or generated HTML changed. Search Console may take time to show the new state, so separate the live correction from Google’s later processing. Don’t promise a ranking boost from consolidating URLs. The immediate win is a clearer route for customers and crawlers.
Sources for this section: Google Search Central: link best practices
Use the canonical decision worksheet
List every observed URL in a suspected duplicate group. Explain the relationship in plain language, then record the preferred URL and the evidence behind that choice. Note conflicting signals and the authorized correction owner. Keep separate verification results for the public response, metadata, and internal link. If content differences aren’t resolved, mark them. Don’t force a merge. This worksheet plans the work. It isn’t an automated instruction to redirect everything. BlueFinch’s website audit gives bounded observations and suggested work. Changes to another host’s site still need the owner’s or developer’s authorized implementation, plus a proportionate retest.
A sample decision should explain why two pages match, not just name the chosen address. “Same service, same location, same current offer” is a much better reason than “shorter URL.” If those facts change later, the maintenance team will know the original consolidation assumption needs review instead of preserving it blindly.
Primary sources
BlueFinch last reviewed these sources on October 23, 2026. Check the linked sources for current requirements and product details.
Use this page for general business information. It is not legal, tax, or accounting advice.