The “Our services” menu item leads to the account area and asks visitors to sign in. The site owner is logged in and doesn’t notice the problem. Sign out or open the site in a private window. A link to a service description should show it to an ordinary visitor, while the account sign-in should remain a separate item.
Open the site as a guest
Google discovers links primarily through ordinary links with an href attribute—the address in the link code. Official documentation.
For a logged-in employee, /account/services/ may show a convenient list, while a new visitor sees a sign-in form. If a public card promises a service description, this address doesn’t meet a guest’s expectations. Start in a clean session with no cookies from the work account. Check that the page doesn’t show an employee’s name or a sign-out button. If private browsing still automatically signs you in, use a separate browser profile that isn’t logged in. Keep the link’s visible text and its destination in separate columns. A “Sign in” link may correctly lead to the account area, while “Service description” pointing to the same path would be a navigation error.
Distinguish a service link from a sign-in button
| Element or session | What the visitor expects | What to do | What to check while signed out |
|---|---|---|---|
| Service in the menu | Public information is expected | Check as a guest | No sign-in screen |
| Sign in button | Authentication is expected | Keep it separate | Clear purpose |
| Catalog card | Public navigation | Check the href | Correct page |
| Logged-in employee | Different access | Don’t treat as a guest | Check separately |
Check the href and final URL
Read the element’s href, then open it in a guest session and record the final address. Check whether there is a server-side redirect to login or a client-side interception after the page loads. Record the document status and the visible result separately. If the link works for an employee but not for a guest, include both results without any personal information from the account area. If the link is generated by a shared component, find its input parameter or route map. Several identical incorrect links may have a single source, so don’t fix each instance manually.
In the inspector, select the link, then run this in the Chrome console:
({ записано: $0.getAttribute("href"), адрес: $0.href });Open the address in a private window without signing in. “Service description” should show the service, and “Sign in” should lead to authentication. If the link goes to login, save the original href and the redirect address from the Location header in the developer tools’ Network tab.
Fix the card and keep the account sign-in
Suppose a service card leads to /account/services/a/, while “Sign in” leads to /account/. Find the service description available to guests at /services/a/ and replace only the card’s address. Leave the sign-in link unchanged. Check both links before and after in a clean session. Then sign in to a test account using the usual method and confirm that the account area still uses its own route. These are two different tasks: making the public description accessible and preserving the private function. An employee checking one card does not confirm either the guest path or the security of the account area.
Update the source of the navigation links
Update the shared source of menu and card routes. If the incorrect URL is stored in the CMS, replace it in the menu or card settings; the label should still describe the service. For an old public link to a private path, the right solution depends on the architecture: don’t add a redirect that interferes with legitimate use of the account area. It is often better to fix the source of the link rather than change the protected route. For the public page, check a regular GET request without cookies. Don’t change the account area’s permissions to make the menu link work. Its personal pages should still require sign-in.
Check the menu and card while signed out
On desktop and mobile, a guest gets the service description at the public URL. The separate “Sign in” link remains, and the account area still requires authentication. There’s no need to change the account area’s permissions to fix the menu.
Read also: Website architecture: URL silo structure and click depth and Broken Link Building: a strategy for getting backlinks. Site checks are available on the reChecker technical audit page.