Section breaks and causes it to end early, throwing out a lot of tags like canonical or hreflang in the <body> section, where they are not supported. Why aren't these tags supported in the body? Probably because it would allow hijacking of pages from other websites. Check redirects and header responses You can do any of these checks with the Chrome Developer Tools, or to make things easier, you can check out extensions like Redirect Path or Link Redirect Trace. It is important to see how your redirects are handled.
If you're concerned about a certain path and the signals are consolidating, check the "Links to your site" report in Google Search Console and look for links that lead to pages earlier in the chain to see if they're there. in the report for the page and displayed jewelry retouching service as "Via this intermediate link". If so, it's a safe bet that Google is counting the links and consolidating the signals to the latest version of the page. For header responses, things can get interesting. Although rare, you may see canonical tags and hreflang tags here that may conflict with other tags on the page. Redirects using the HTTP header can also be problematic.
More than once I've seen people set the "Location:" for the redirect without any information in the field, then redirect people to the page with, say, a JS redirect. Well, the user goes to the right page, but Googlebot processes location:first and goes into the abyss. They are redirected to nothing before they can see the other redirect. Search multiple tag sets Many tags can be in more than one place, such as the HTTP header, <head> section, and sitemap.