.d53b12e5.png&w=3840&q=75 "Trivas.ai")
by Trivas.aiNobody sets out to get https://app.trivas.ai/login?step=signin indexed. It just happens.
App routes like this get crawled through internal links buried in a navbar, through an old sitemap that never got trimmed, or through query-string variants Google decided to index on its own. One parameter gets discovered, Googlebot treats it as a distinct URL, and now it's sitting in your index next to pages that actually earn traffic.
?step=signinWe pulled the numbers on this exact URL. Under 10 impressions over three months. Zero clicks. Nobody is searching for your login screen, and if they land on it from search, they're not converting, they're just confused.
Here's the part people miss: a page with no search demand and no conversion value isn't neutral. It's not just "doing nothing." It's actively diluting the signals Google uses to judge the rest of your site, including crawl budget allocation and the broader quality assessment that falls under E-E-A-T.
Think about the ratio. If you've got 500 indexed URLs and 480 of them are genuinely useful content, that's a strong ratio. If 50 of those 500 are login screens, auth steps, cart states, and other thin gated pages, you've just weakened the signal.
Search engines don't evaluate pages in a vacuum. They sample your indexed inventory to decide how much crawl effort you're worth. A site where a meaningful chunk of indexed URLs return thin or gated content (think: a login form with no body copy, no unique value, nothing for a crawler to actually read) signals lower overall quality. That can mean slower discovery of your real pages, or less frequent recrawling of the content that's actually trying to rank.
This isn't about one URL tanking your rankings overnight. Nobody's domain authority is collapsing because of a single /login?step=signin page sitting in the index. The damage is cumulative. Every thin page you leave indexed is a small tax on the pages you actually care about. Enough of them stack up and you're paying that tax sitewide.
When you find a low-value URL like this, you've got two real options, not three.
301 merge. Redirect the URL's authority into a relevant pillar page. This makes sense when the page has backlinks pointing at it, or when it used to pull meaningful organic traffic before it degraded into noise. You're consolidating whatever equity exists rather than letting it evaporate.
Noindex. Leave the page fully functional for actual users (they still need to log in, obviously) but tell search engines to skip it. This is the right call when there's no backlink equity worth preserving and no search intent to capture in the first place.
For https://app.trivas.ai/login?step=signin specifically, noindex wins. Zero clicks and under 10 impressions over three months means there's no meaningful equity to consolidate. A 301 merge would be solving a problem that doesn't exist here. You're not redirecting value, because there isn't any to redirect. You're just removing a page that never should have been crawlable in the first place.
Login and auth pages almost never carry real informational content worth merging anywhere. There's no blog-post-worthy insight hiding behind a "sign in" button.
But sometimes teams bolt supporting text onto these screens anyway: a line about password resets, a note on account lockouts, a quick FAQ blurb. If any of that exists on https://app.trivas.ai/login?step=signin, it doesn't belong there. It belongs on a page built to actually rank for people asking those questions.
Move account-access guidance to the FAQ page or into the help center. Both are built to carry that kind of content and both can actually show up in search when someone types "forgot trivas password" or similar. Leaving that content stranded on a gated auth screen means it's invisible to search and invisible to anyone who isn't already mid-login.
This split keeps things clean: the functional login flow stays exactly as it is for users, and the informational content moves to a page that's eligible to compete in search. Nothing about the user experience changes. What changes is whether Google wastes time crawling a screen that was never meant to be a landing page.
If you've got one login URL quietly indexed with no traffic, you've probably got more. Here's the checklist we used.
/app, /login, /signup, or /dashboard route from Search Console over a 90-day window. Don't eyeball it, export the actual data.Run this quarterly if your app ships new routes often. Auth flows especially tend to spawn new query-string variants every time someone tweaks the login UX, and each variant is a fresh chance for Google to index something it shouldn't.
The call here is simple: noindex https://app.trivas.ai/login?step=signin, and route any account-access documentation that was living on it over to the FAQ or help center instead.
Pruning a URL like this isn't about making your site smaller for its own sake. It's about pointing crawl budget and quality signals at pages that are actually trying to answer a real search query. A login screen was never going to do that job, so stop asking it to.
If you landed on this post because you were actually trying to find your way into the Trivas app, you're in the wrong place, head over to our getting-started resources instead.
explore more insights
3 min read
3 min read
3 min read