Why Google sitelinks point to the wrong pages
Trace unwanted Google sitelinks to their destinations, audit how your navigation labels them, and choose a fix that preserves useful pages in search.
By Crawlito · 6 min read
In short
- Sitelinks are generated automatically for individual search results.
- A prominent link with a vague label is worth checking in both the mobile and desktop navigation.
- A page-level indexing directive affects the destination beyond its appearance as a sitelink.
On this page
If Google shows an old offer, a login page, or the wrong department beneath your main result, open each sitelink and trace how the rest of your site links to that destination. Repair redirects, unclear page names, and prominent links to retired sections. Google selects sitelinks automatically, so the work you can test directly is the route a person or crawler follows through your website. Google’s sitelinks guidance
Identify the destination behind each label
Capture the entire result for the query someone reported. On a brand search, a row reading “Training” might send people to a workshop archive, the current course list, or an anchor halfway down the homepage. A screenshot shows the words. Opening the link identifies which document those words represent. Copy the final address as well as the address you initially opened. A redirect can make a label seem inaccurate even though it once described its source well.
Classify each destination according to its purpose today. A current section is still useful but may need clearer navigation. An archive can be useful to past customers but no longer belongs in the main menu. A retired campaign with a true successor needs a maintained route for its old links. These differences determine what to change. Rolling all three into a request to “remove the wrong pages” tends to produce indexing changes that hide material existing customers still need.
If the extras lead to different headings on the same long page, examine the heading labels and anchor targets on that page. If they open separate URLs, begin with site navigation and the destination titles. Record which situation you saw. Keep the wide search result distinct from the site's own menu, since the latter is under your direct control.
Read your navigation without its visual styling
Start with the home, a popular article, and one page in the affected section. Inspect the HTML links in the header, footer, mobile menu, and content. A visitor might see two large cards with different photos; a crawler can receive two links that both say “Learn more.” Look for the link destination alongside the text that would help someone choose between those cards. A responsive menu might have its own data source and still put last year's course calendar first.
<nav aria-label="Workshops">
<a href="/workshops/">Current workshops</a>
<a href="/workshops/past/">Past workshop materials</a>
</nav>Those labels tell a visitor which route to choose before opening either link. They also remain meaningful when the links are read outside the surrounding card design. A navigational label can be concise while preserving the distinction between a schedule, a sign-in area, and an archive. See the guide to crawlable JavaScript links if a menu opens correctly on click but you cannot find an anchor with the expected address.
Write down how often each destination appears in the shared layout and where the links are placed. Frequency is a debugging aid, not a formula for sitelinks. A retired page in a shared header could appear on every article because one menu entry survived a redesign. Fixing that single entry gives visitors a better route everywhere the header is reused.
Decide what should happen to an old section
Imagine a retailer replaced its “Corporate gifts 2025” campaign with a year-round business gift service. If the old page contained only the expired offer, and the new one meets the same need, the team can point the retired URL directly to the service and update links in menus and evergreen articles. Verify that the destination explains the remaining offer. A redirect to a general homepage requires the visitor to solve the original navigation problem again.
Now change the example. The old page contains instructions for redeeming vouchers already bought. Removing it could leave customers without instructions. Keep it accessible, label it “Redeem a 2025 voucher,” and move the link into the customer support area. Make the service page the primary link where the buyer is shopping. Both documents earn a place in the site, with clearer expectations attached to each route.
Google lists removal of the underlying page or a noindex directive as options for removing a sitelink destination from Search. Consider what else the page contributes before choosing either. A help article with an unwanted position under the brand result may still answer a very specific troubleshooting query. Review the indexing directive guide before making a page disappear from those searches too.
Check the journey on both layouts
After the release, start at each entry page you sampled and follow the links as a logged-out visitor. Check that the mobile menu opens, the links lead directly to the expected documents, the visible headings match their labels, and a back navigation returns to a useful place. On the archive, confirm that someone looking for the current offer can reach it without guessing which navigation item to choose. Use the broken internal link guide for destinations that return an error or land on a generic fallback.
Keep a compact change record for the people who monitor search. Include the query, the old label and destination, changed navigation locations, the final URL, and the release date. Save a later search observation with its own date. Sitelinks can vary by query, and Google can omit them when it finds no useful set. A shorter row beneath one search result does not by itself establish whether the new navigation helped customers.
To evaluate the visitor outcome, compare a simple task before and after the change. Can someone arriving on a current product page find this month's workshops? Can an existing customer find their old voucher terms without opening a sales form? Observe the clicks or run the exercise with a colleague who did not build the menu. These checks give you evidence even on days when the search result looks the same.
Read the incoming links to one misleading destination
Take the specific URL from the unwanted sitelink and search your published navigation configuration or crawl export for pages that link to it. Group the results by shared component. Forty references inside a common footer may have one owner, whereas three links in old feature articles may require three editorial decisions. Review what a visitor reading each source page would expect on arrival.
For example, the anchor “Support” in the top bar might point to an outdated customer portal, while “Support” in a historic incident report correctly points to a record of the old service. Updating the top bar directs new users toward the current portal. Keeping the incident report historically accurate can still make sense if its link remains useful and clearly labeled. Write the intended destination for each group before making the changes. Rerun the link search afterwards to check whether remaining references are deliberate and explainable.
Frequently asked questions
Can I submit a preferred list of sitelinks?
Google describes an automated selection process. Publish a logical site structure and descriptive internal links to the destinations you want people to find.
Will adding a sitemap set the display order?
A sitemap can help with discovery. It offers no control for setting the order of sitelinks under a specific result.
Should I remove a useful login page from the index?
First determine who arrives there from a branded search and where people would sign in instead. A change to indexing affects all searches for that page.
Inspect the main entry page
Use the free page check on the homepage or section hub that sends visitors to the wrong destination. Start the navigation repair at the page that supplies the link.
Filed under Structure and schema. Topics: google, internal-links, navigation