Internal link to a redirecting page
link_to_redirectShort answer
Links on your pages point to URLs that 301 somewhere else — typically old slugs, http:// or non-www addresses left in content after a migration. Google follows redirects without losing value, so this is about speed and crawl efficiency: update the links to the final URL.
Why it matters
Each redirected internal link costs the visitor a round trip and the crawler a request. Thousands of them (the usual case after a domain or scheme change) add up to a measurable share of crawl budget on large sites and a visible delay on mobile. They also hide the real link structure from you: the link graph on the Pages screen is computed on final URLs, but the extra hops still happen.
How Glimana detects it
A site-level rule: links from current, non-redirecting 200 pages to targets that respond with a redirect. Links found on pages that themselves redirect (old copies) are ignored, because visitors never see them.
How to fix it
If the pattern is site-wide (every link is http:// or non-www), a database search-and-replace fixes it at once. Otherwise edit the links in content and templates.
Better Search Replace (or WP-CLI wp search-replace 'http://www.example.com' 'https://www.example.com') for scheme/host changes; edit individual links for slug changes.
Edit the navigation items and the content; Shopify does not search-replace across resources, so prioritise menus and the most-linked pages.
Search-and-replace in the content store; use route helpers in templates.
How the fix is verified
Affected pages are re-crawled; the task closes when their internal links resolve directly to 200.