Your page declares a preferred URL, but Search Console shows a different Google-selected canonical. That does not prove the element is missing. Google considers several signals and decides how similar pages are grouped.
Two fields represent different observations
Fictional example: /guides/delivery/ declares itself canonical, while Google still selects /blog/delivery/. Most internal links continue using the old path, and both pages remain accessible.
In URL Inspection, compare the user-declared and Google-selected addresses. Note the last crawl date. A live test examines the current fetch; it does not replace the stored index record or conclusively predict Google’s later selection.
Compare the two pages’ content. Then inspect redirects, canonicals, sitemap entries and internal links. Check whether the desired destination responds and is intended for indexing.
If the same page has permanently moved, old entry points should support the chosen new URL. If the pages contain different information, that distinction needs to be clear in their content.
Record changes with dates and inspect Google’s stored state again later. Requesting indexing forces neither an immediate crawl nor the desired canonical selection. Adding more canonical elements will not resolve contradictions between existing signals.
Related check: Check a canonical redirect destination.
If conflicting URL output originates in several technical components, the Technology and stack review can assess their interaction. It cannot guarantee Google’s selection.