Old Integration Links Keeping Pages Out of Google
By Gianna Stead | SEO Manager, Maisona | 3 min read
One of our clients had an online shop wired to an integration somebody set up years ago, and nobody had looked at the links it left behind. We crawled the site and found internal linking issues under hundreds of pages. Search Console listed a long run of them as “Not indexed”.
Every link worked when you clicked it, because the redirects did their job. That’s why nobody had spotted it.
The Integration Built Its Own Structure
An integration usually builds its own structure on your site. In a WooCommerce shop that means brand and category terms, archive pages and product data, with links to all of them in menus, product descriptions and templates. Later a migration, a rebrand or a plugin swap moves the pages. The links stay where they were and point at addresses that don’t exist any more.
On this site the brand taxonomy had the worst of it. Terms from the old integration still had archive pages, and some listed the same products as the current brand pages. The main menu and a stack of product descriptions linked to the old ones.
Menus and footers multiply the damage. A footer link sits on every page, so on a 400-page site one stale link is 400 stale links. Google works through them one at a time as it finds and indexes your content, and it meets the same dead end every time.
Doesn’t a Redirect Take Care of That?
Only for visitors. Search Console labels a redirecting URL “Page with redirect”, and Google won’t index it. That’s fine for an old address nothing links to. It’s a problem when your own menu sends Google there on every crawl.
Each of those visits ends at a page Google’s already decided to skip. The page you want indexed gets fewer direct links, so it looks less important and Google visits it less often. When one redirect leads to another, Google has extra hops to make before it reaches anything useful.
Google Ignored the Canonical Tags
The clearest case we found was on product pages. Google had flagged a batch as “Duplicate, Google chose different canonical than user” and wouldn’t index them.
Each of those pages carried the right canonical tag, pointing at its own current /product/ address. Google ignored it and picked the old /solutions/ version of the same product, from before the taxonomy changed. That old page no longer existed. It redirected, and it wasn’t in the sitemap. Google still had it from earlier crawls, and on some pages an old internal link was still pointing at it.
A canonical tag is a request. Google’s documentation calls it a strong signal, and says that linking consistently to the URL you want helps Google understand your preference. Old links pointing the other way are a likely reason Google kept disagreeing.
The Usual Suspects
You’ll find the same handful of problems on most sites we audit:
- Menu and footer links pointing at old category and brand URLs
- Archives that list the same products as a newer archive
- Product descriptions and blog posts linking to retired paths
- Redirect chains, usually two or three hops long
- Links that run on a click script, not a plain <a href>, which Google can’t reliably follow
A different client had a version of this after a URL migration. Their case studies and blog posts still carried editorial links to the old addresses, and nobody had gone back through them.
How We Fixed It
1. Export Every Internal Link That Redirects
Run a Screaming Frog crawl, open the Response Codes tab and filter to Redirection (3xx). Click any URL and the Inlinks pane at the bottom lists every page linking to it. Then go to Bulk Export, Response Codes, Redirection (3xx) Inlinks to download the full list. Sort it by how many pages link to each URL and start at the top.
2. Fix the Menu
Change each menu and footer item to the final URL. One stale item counts hundreds of times, so it’s the quickest win on the site.
3. Edit the Remaining Links
Update the product descriptions, templates and body copy so each link points at the final URL. Then leave the redirects where they are. They send old bookmarks and external links to the right page. Remove them and each one becomes a 404, including whatever Google crawled years ago. Once you’ve fixed your own links, the redirects only have to handle visitors from outside.
4. Pick One Archive for Each Brand
Where two archives list the same products, keep the one with the cleaner URL and the longer history. Check Search Console clicks before you choose, because an old archive that still earns traffic may be the one to keep. Redirect the other with a 301, because a 302 tells Google the move is temporary and it keeps the old URL around. Yoast has a switch for each archive type that controls whether it appears in search results, so use it on whatever’s left over.
Then open the sitemap. It should list only the archives you kept. A sitemap showing the old ones keeps sending Google there regardless of what the menu says. Yoast usually drops an archive from its sitemap once you set it to noindex, but check the sitemap file yourself, because one stale entry undoes the menu fix.
5. Validate in Search Console
Open the Page indexing report, pick the issue and click Validate Fix. Google says validation typically takes about two weeks, and it can run longer.
Crawl It Again
Crawl again. You want no internal links returning a 3xx or 4xx, and no chains. Then watch the “Page with redirect” row in the Page indexing report shrink as Google recrawls.
A crawl after every integration, migration or plugin swap is a short job while the list is new. If your site’s been through any of those and nobody’s checked the links since, our team can run the crawl and show you where Google’s hitting dead ends.
FAQs
What are internal linking issues?
They’re links between pages on your own site that point at redirected, broken, duplicate or unfollowable URLs. Google struggles to crawl and index the pages behind them.
Do redirects hurt SEO?
A single redirect is a safety net and does no harm. Trouble starts when your own menu and content link through redirects or chains, because Google won’t index the redirecting URL and has to make extra hops to reach the real page.
How long does Google take to reindex pages after you fix the links?
Search Console validation typically takes up to about two weeks, and sometimes longer. Pages appear in the index as Google recrawls them.
Can a link built with JavaScript stop a page being indexed?
It can. Google can’t reliably follow links that aren’t plain anchor tags with an href, so a page that’s only reachable through a click script may never be found.
Why does Google ignore my canonical tag?
A canonical tag is a strong signal, not a command. Google also weighs redirects, internal links and its own earlier crawls, so an old URL it still remembers can win over the one you declared.
When should you check your internal links?
After any integration, migration or plugin swap, before the stale links pile up.