A practice page is live, answers a real client question, and appears in the firm’s sitemap. Search Console still says “Duplicate, Google chose different canonical than user.” It is tempting to change the canonical tag immediately. First identify the two URLs and decide whether they actually serve the same reader. Google’s choice is evidence about how it has grouped the pages, not proof that a plugin setting alone caused the problem.
A canonical URL is the representative page Google chooses from a set it sees as duplicate or very similar. Google may choose a different representative from the URL you nominate. Its canonicalization explanation says that ordinary duplicate content is not by itself a spam violation. For a law firm, the practical risk is that the wrong service or location page becomes the result a prospective client sees. Treat the issue as a page-purpose decision before a technical ticket.
Identify both URLs and the actual difference
Open the affected URL in Search Console’s URL Inspection and record the user-declared canonical and the Google-selected canonical. Note whether the inspected URL is indexed, when it was last crawled, and what its live test currently returns. Google’s troubleshooting guidance starts with that comparison. Search Console reports Google’s indexed view, while a live test reflects the present page; a recent edit can leave the two temporarily different.
Now open both public URLs without an editor login. Compare the title, H1, first screen, service area, attorney proof, FAQs, contact action, and the queries each is intended to answer. A family-law overview and a child-custody service page may share language yet serve different tasks. Two pages that merely swap neighboring city names while carrying the same promise, attorney bio and FAQs may offer no material distinction. Record the difference in one sentence a client could understand. If you cannot, the pages may need consolidation or a substantial rewrite, not a new canonical declaration.
Check the site’s own links and sitemap. Does navigation, the practice hub and relevant posts point to the intended destination, or do they repeatedly send visitors to its near-duplicate? The content inventory is where to list the two URLs, the query each owns and the decision to keep, merge or retire. This prevents the team from “fixing” an inspection warning while preserving the same competing architecture.
Choose the repair that matches the relationship
If the URLs are genuine duplicates and one has no reason to remain reachable, use a permanent server-side redirect to the page you want users to land on. Update internal links and the sitemap to that destination. If both URLs must stay accessible but carry substantially the same content, use a consistent rel=canonical preference on the duplicate and a self-referential canonical on the preferred page. Google’s canonical methods guide calls redirects and canonical annotations strong signals and sitemap inclusion a weaker one; none guarantees Google will follow the preference.
If both pages deserve to exist, give them distinct jobs. A practice hub can orient a visitor among services; a custody page should answer custody questions, explain who it serves, and lead to a relevant consultation path. Change the body and internal anchors to support those jobs. A self-canonical tag on each page is useful, but two nearly interchangeable pages will still look interchangeable. The question is whether a reader would choose a different page for a different task.
Avoid using noindex, robots.txt blocking or the removals tool as a casual canonical repair. Google’s guidance says robots.txt is not a canonicalization mechanism, and noindex removes a page from Search rather than expressing a preference among similar URLs. Those controls have other uses, but they can make an important service page disappear if applied without a clear indexing decision. Do not send Google conflicting signals such as a sitemap listing URL A, internal links favoring B, and a canonical on A pointing to C.
Verify the public signals before asking for recrawl
After a change, request the bare public URL, follow any redirects and inspect the final HTTP status. Confirm that the canonical tag in the rendered head points to the intended absolute URL, that the page is not inadvertently noindexed, and that the final page presents the service and location promised by its title. Test the phone layout and the contact action. A successful WordPress save, or a canonical field that looks right in an SEO plugin, is not public proof.
Check the affected links from the hub and from supporting articles; they should lead to the preferred URL and return a useful page. If a redirect replaced an old page, do not leave navigation pointing through the redirect forever. Google’s documentation recommends consistent internal links to the canonical URL. This is also a better reader journey than sending a prospect through a chain of legacy URLs.
Keep a small before-and-after record: inspected URL, Google-selected canonical, declared canonical, public status, intervention date and intended query. Wait for Google to recrawl before judging the result. A live test showing the new tag does not mean the indexed choice has already changed. Reinspect later and compare the same URL pair. Search visibility and enquiries should be checked separately in the reporting process; choosing the intended canonical is not a promise of more traffic.
When two practice pages seem to compete, the right fix begins with what each page is supposed to do for a real person. If you need a clear keep/merge/rewrite decision for a law-firm site, ask Rubiks for a page-pair review. We will identify the two URLs, the public signals and the recommended owner page before making a change.